Autopilot

An Autopilot routine is a standing plan: which accounts, how often, what to post about, and how far a run may go (drafts for your approval, scheduled posts, or publishing). You save it once on the Autopilot page.

Your AI does the writing, in each account's own voice, the same way it does when you ask it in a chat. Antwork never writes the posts. It keeps the plan, holds every run to it, starts the run where your AI allows it, and tells you when a run doesn't happen.

• ›1. Open Autopilot in the sidebar and choose New routine.
• ›2. Pick the accounts the routine posts to.
• ›3. Set the days and the time, in your timezone.
• ›4. Write the brief: what the posts are about, and anything your AI should keep in mind.
• ›5. Choose what a run may do: Drafts for my approval, Schedule the posts, or Schedule or publish without asking.
• ›6. Set the most posts one run may make.
• ›7. Choose who starts each run (the sections below), then save. A routine's switch turns it off and on at any time.

You can also ask your AI to set up a routine, in plain words: "every Monday at 9, write 2 posts about our weekly special for Instagram and Facebook and schedule them". It uses the manage_routine tool, with the same limits as the Autopilot page, and reads the routine back to you as one sentence.

It can list, edit, pause, resume, delete or run a routine now the same way. In ChatGPT or Grok it can then create its own scheduled task with the routine's prompt in the same chat. A Claude routine's API trigger and token are the exception: you create them in Claude (see below) and give them to your AI or paste them on the Autopilot page.

With a Claude routine's API trigger, Antwork starts your Claude routine at each run time, so a task switched off in Claude can't fail without you knowing. It needs Claude Code on the web, on a Pro plan or higher.

• ›1. In Claude, open claude.ai/code/routines and create a routine with the Antwork connector. Paste this as its prompt: "Antwork starts this routine and its message says which Antwork routine is due. Follow the instructions in that message, using the Antwork connector." Claude treats what Antwork sends as information, and acts on it only because the routine's prompt says to.
• ›2. Under Select a trigger, choose Add another trigger, then API, then Generate token.
• ›3. In Antwork, open the routine, set Runs from to Claude routine, and paste the URL and the token.
• ›4. Save, then use Run it now to try it once.

Create a scheduled task in ChatGPT at the routine's time, with the Antwork app on, and paste the routine's prompt from its setup panel. Antwork checks each run and tells you when one doesn't happen.

Antwork starting runs in ChatGPT itself, through ChatGPT's event-triggered tasks in a Work chat, is being tested and switches on later.

Grok runs the routine on its own schedule. Antwork records each run and notices the ones that didn't happen.

• ›1. In Grok, open Automations (grok.com/automations).
• ›2. Add Antwork under Connectors if it isn't there: New Connector, then Custom, with https://api.antwork.io/mcp.
• ›3. Create an automation at the routine's time and paste the routine's prompt from its setup panel.

In the Codex app, create an automation with the Antwork MCP server added; in Claude Code, use /schedule. Set the routine's time and paste its prompt from the setup panel. A Codex automation runs while the Codex app is open. Antwork records each run and notices the ones that didn't happen.

Set Runs from to webhook, and add a webhook endpoint subscribed to routine.due under Developer, Webhooks. At each run time Antwork sends it, signed, with the routine and its brief. Start your agent from it (n8n, Make, Zapier or your own code) and have it call Antwork with routine_id.

Webhooks are part of every paid plan.

Webhooks reference

It calls get_post_context with routine_id. The answer carries the routine's brief, accounts, mode, how many posts this run may make, and what is already queued.

It passes the same routine_id to create_post, schedule_post and publish_post, so every post is linked to the run.

Antwork holds the run to the plan: a drafts-only routine can't schedule or publish, a run can't go past its post limit or post to other accounts, and a paused routine refuses. Each refusal says why.

MCP reference

The Autopilot page marks the run as missed and says why, with Run it now and Check setup. Antwork also emails you, once per routine per day.

Why a routine didn't run

The Free plan keeps active routine; every paid plan keeps as many as you like. Starting runs by webhook is part of every paid plan.

If you move to Free with more routines than it keeps, the newer ones are paused. Resume them after upgrading, or pause another one first.

Pricing

Contact

Questions, integration help, or bugs? Reach out.