Automations
Set it up once in plain words, on a schedule or when something happens in your apps. PandaOS runs it and keeps the result waiting for you.
Describe the job once. PandaOS turns it into an automation with a trigger, its steps and a record of what every run did.
Every hour, every weekday, every Monday at 09:00 or the 1st of the month. Pick it in the schedule picker, or write a cron expression if you prefer.
Start a run when an email arrives, an issue is opened or a deploy finishes. Webhooks and events from apps you built in PandaOS start it at once.
Any app you have connected can be a step, next to AI steps, full agent sessions and conditions that branch the flow.
Rules mode is the default: a call that matches no rule pauses the run and asks you first. Scheduled runs always use the Limited sandbox.
How it started, how long it took, what it cost and every tool call, for the last 10 runs of each automation. You are notified when one finishes.
No workflow editor to learn first. Say what you want, check what PandaOS built, and let it run.
Tell PandaOS in a chat what should happen, and when.
See the trigger and every step, and change any of them in the builder.
It runs on its schedule or its event, and the result waits for you.
Recurring work rarely takes long. It just keeps coming back, and it always lands at a bad time.
You remember the routine and do it by hand.
The routine runs and you review the result.
Automations use the same apps, the same AI and the same project knowledge as your chats.
Describe the work that keeps coming back, and let PandaOS take it from there.
They run while PandaOS is running, and that includes the tray. Closing the window keeps PandaOS in the tray, and it starts there when you log in, so a schedule fires with no window open. If your computer was asleep or PandaOS was quit, a missed run happens once when it is back, or is skipped if you prefer.
No. Describe the automation in a chat, or pick a trigger and steps in the builder. A custom cron expression is there if you want one.
Gmail, Google Calendar, Google Tasks, Google Chat, Google Drive, GitHub, Vercel, Supabase, Trello and database queries, plus any webhook. Apps you build in PandaOS can start automations with their own events.
Webhooks and events from apps you built in PandaOS start a run at once. Built-in apps are checked every few minutes, an interval you can set on each trigger.
Rules mode is the default: calls that match your rules run, read-only tools are always allowed, and anything else pauses the run and asks you. Automations started by a webhook always run in Rules mode. For automations you trust, you can choose Full access.
The same connections as your chats. An automation follows your default engine unless you pin it to another, and every run shows its tokens and cost.