Your agent
Automations
Create jobs that run before publishing, after an event, or when you start them, with clear limits on what they can do.
Automations are named jobs your agent runs when a specific trigger happens. They live under Advanced in the sidebar. For recurring content work, like a weekly roundup or a release post, use Playbooks instead.
Create an automation
Ask in chat. Describe the job ("one day after I publish, email me three follow-up ideas") and your agent replies with a setup card that walks through what it does, when it runs, and what it can access. Create automation on the Automations page opens the same conversation. Everything is saved paused until you choose Turn it on, or Keep it paused to leave it off.
Build it yourself. Open the arrow beside Create automation and choose Create manually to fill in the same fields in one form.
Choose a trigger
- Before publish runs while you prepare to publish a post, for checks like "make sure every post links to our docs."
- After an event runs when a post is published, scheduled, unpublished, archived, or restored, or when a reader subscribes. It can start right away or after a delay of up to 30 days.
- Manual runs only when you start it with Run now.
New automations can't run on a schedule. Each matching event starts one run. A reader subscribing can start a private draft or notify you, but never a public action.
Configure the job
Give each automation one clear job. Its capabilities are grouped by what they do:
- Sources: your posts, publication details, analytics, audience stats, and the public web.
- Outputs: create and edit private drafts.
- Delivery: email the result to you.
- Public actions: publish to an audience, which needs your confirmation.
- Connected tools: services from Connections. Reading works on its own. Tools that change something elsewhere stay off until you turn them on for this automation.
The agent can't add a tool or public action during a run.
Turn on Skip runs with nothing to do for jobs that only sometimes have work. A quick check runs first and skips the run when your instructions don't apply. Skipped runs show in your Inbox with the reason.
What needs your approval
Private work, like reading content or creating a draft, doesn't need extra approval. Public actions do.
The first public action is Post on X: one original, text-only post per run on a connected X account. When you add it, the confirmation names the automation, its trigger and timing, and the X handle. Choose Allow and enable to authorize and start it, or Save paused to keep it without authorization.
Enabling an automation authorizes that one job, with the trigger and account you confirmed. Asking the agent to post something in chat applies to that one request only.
Needs review
Editing or disabling a public automation clears its authorization. It also moves to Needs review when its connected X account changes or disconnects, or when a tool it was allowed to use is disconnected. Review it and choose Allow and enable again. Until then, public actions are skipped and Run now is unavailable.
Automation runs use the monthly credits included with your plan. See Plans and credits.