Browse docs

Automations

Give the assistant a recurring task, run it on a schedule, and get the result by email.


An automation is a task for the assistant that runs on its own: a weekly Search Console report, a monthly content health check, a daily look at new competitor pages. You write the instructions once, pick a schedule, and choose where the result goes.

Find automations under Automations in the sidebar.

Creating an automation

  1. Open Automations and click New automation, or pick a template and click Use template
  2. Give it a name and, if you like, a description
  3. Set the Trigger
  4. Write the Agent instructions
  5. Choose the Action
  6. Click Create

Automations can be switched between Active and Inactive at any time.

Templates

When you open Automations, templates are shown below your list. A template fills in the instructions and settings for a common task, so you only need to adjust them for your site. Click Use template to start from one.

Triggers

Every automation can be run manually with Run now. Add a schedule to run it automatically:

ScheduleRuns
Manual runOnly when you trigger it
HourlyEvery hour, at the minute you choose
DailyEvery day at the time you choose
WeeklyOn the day and time you choose
MonthlyOn a day of the month (1st to 28th) at the time you choose
Custom (cron)Any schedule you can write as a cron expression

Schedules use a timezone, which defaults to yours. You can change it in the trigger settings.

How often automations can run, and how many can be scheduled, depends on your plan. Starter includes three scheduled automations that run weekly or monthly, Pro includes unlimited automations that run up to daily, and Business runs them up to hourly. Automations you run by hand with Run now don't count toward the limit. See pricing.

Agent instructions

Describe the task as you would to a colleague, for example: "Summarize last week's organic search performance and email me the top movers."

Use the + button next to the instructions to add:

  • Data sources, such as Google Search Console, Google Analytics 4, Google Ads, Ahrefs or SerpApi. See Integrations.
  • Skills, so every run follows the same playbook. See Skills.

You can also choose the model the automation uses. Each run reads your pages, context and connected data fresh, and can look back at its own previous result when it needs continuity, for example to report what changed since last week.

Actions

The action decides what happens with the result:

  • Just output: the result is saved in the run history. Nothing is sent.
  • Send email: the result is emailed to one or more Recipients

Under Email options you can add CC and BCC, set a Subject, and include a disclaimer at the top of the email. Charts in the result are sent as images, so they display in every email client.

Failure recipients

To send failed runs to other people, turn on Send failure emails to different recipients and enter addresses under Fail recipients, for example the person who maintains the automation. Successful runs still go to Recipients.

Run history

Open an automation and choose Run history to see every run, newest first. Each run has a status:

  • Queued
  • Running
  • Success
  • Failed
  • Cancelled

Open a run to see its Output and its Run log: what the assistant did step by step. Each run also shows its trigger, duration and model. You can stop a run in progress with Stop run, or start a new one with New run. Download a run's output as Markdown or PDF to share it.

All recent runs across your automations are also listed on the Automations page.

Credits

Each run uses AI credits based on the work it does, like a chat turn. See Credits and usage.

Ideas

  • A weekly email with the pages that gained and lost the most clicks
  • A monthly list of your top pages whose helpful-content score dropped
  • A weekly check of what ranks for your top ten keywords
  • A monthly summary of Google Ads spend by landing page