Automations

An automation is work that runs without you. You describe it once in chat; from then on it happens by itself whenever something starts it.

A scheduled task runs on a clock. An automation runs on an event — an email arriving, a form being submitted, a row landing in a spreadsheet, a web page changing. That difference is the whole feature: a clock cannot tell you an email arrived.

Open Automations from the left sidebar (/user/automations).

Creating one

You do not fill in a form. You say it in chat, in your own words:

"Whenever a new row lands in my leads sheet, research the company and email me a summary."

"Keep an eye on my inbox — when a customer emails about pricing, reply with our rates."

"Give me a webhook URL that files whatever it receives into my revenue spreadsheet."

The assistant works out which trigger fits, sets it up, and hands back anything you need to wire up — a webhook URL, an email address, a form link.

Phrases like "whenever", "keep checking", "every time" and "from now on" are what tell it you want an automation rather than a one-off task.

The twelve triggers

Anything that can send a webhook — Zendesk, Linear, Stripe, Slack, Shopify — works through the Webhook trigger. You paste the URL into that app; no separate integration is needed.

About the polled triggers

Gmail, Sheets, Airtable, Notion, Drive, Calendar, Jira and Web page are checked on an interval, as often as every minute. Each one remembers what it has already seen, so an item fires exactly once — and a missed check catches up rather than skipping.

The apps in that list need to be connected first, from the connectors (grid) icon in the chat input. The web-page watcher needs nothing.

What a run does

Every run goes through the normal chat pipeline, so an automation can reach every tool you can: your connected apps, web search, your Brain documents, your saved Skills.

Whatever started it comes along as data — the webhook body, the form fields, the new rows, the email. It arrives clearly fenced and labelled, never mixed into your instructions. That matters: a webhook is open to the internet, and text arriving from outside must never be able to rewrite what your automation was told to do.

The result lands as a new chat you can open, and is filed in Artifacts.

Watching them

The Automations page lists everything you have running, with its trigger, how often it checks, how many times it has run and when it last did.

The history icon on a row opens every run: what it did, how long it took, how many tools it used, and — when something broke — why. A run that failed before producing anything is still recorded, so a silent failure is impossible.

Activity shows recent runs across every automation at once, which is the fastest way to answer "is anything broken?"

Pausing, editing, deleting

Pause an automation to stop it firing without losing it. Resuming re-arms it from now, so a paused-for-a-week automation does not fire seven times when it comes back.

Rotating a webhook or form token invalidates the old URL immediately. Do it if a URL leaks.

Credits

A run that only looks and finds nothing is free. A run that actually sends something — an email reply, a Slack message — costs credits.

That split is deliberate: a watcher checking every minute mostly finds nothing, and billing those checks would drain an account for doing no work.

If your balance cannot cover a send, the automation pauses itself and tells you, rather than continuing to work for free.

Notifications

You get an in-app notification for every run.

Event-triggered automations do not email you on success. An inbox watcher that emailed you every time it checked would be filling the inbox it was hired to watch. Scheduled reports still email, because there the email is the deliverable.

Failures always notify, whatever the trigger. An automation that quietly stopped working is worse than one that is noisy.

Templates

The Templates tab has ready-made automations across sales, support, marketing, operations and data. Picking one prefills the wording in chat, where you can adjust it before setting it up.

From your own code

Every automation is reachable over the REST API with a personal API key, and through MCP from Claude Desktop or Cursor. See API access.