Automations
It keeps working after launch day.
An Automation is an agent with a job, a schedule or a trigger, and a report to file. Write one yourself, or let an Initiative set up the recurring work its outcome needs.
How it works
- 1
Give it a job
Name it and write its instructions in plain text, or let an Initiative create it paused.
- 2
Choose when it runs
Every day, weekdays, custom days or a cron schedule, or when an event arrives.
- 3
It runs and reports
Each run reads the workspace and files a report with a title, summary and the full write-up.
- 4
Follow up
Open any run to follow up or steer, and pause, resume or run it now.
Triggers
On a schedule or when something happens
Run on a calendar, react to your support source, or accept signed events from any system you run.
- Every day, weekdays, custom days or a five-field cron
- When a support report is created or a customer replies
- Custom signed events, up to 32 types per agent
Reports
A report on every run
Every run files a report into the workspace and notifies you when it finishes or fails. Scheduled checks report even on quiet days, so silence never hides a broken job.
- Title, summary and the full markdown report
- Notifications on finish or failure
- Linked to the Initiative it serves
Reliability
Built to run unattended
Automations run without anyone watching, so they never escalate for permission and retry only what is safe to retry.
- One automatic retry: after a crash or a provider failure
- Marked skipped when the CLI is not ready
- Signed webhooks with per-agent keys and rate limits
Where it stops for you
Runs on its own
- Runs on its schedule or trigger
- Reads the workspace and your connected sources
- Files a report and notifies you
- Retries once after a crash or provider failure
Waits for you
- Turning on an Automation an Initiative created
- Changing its own instructions, which needs your reply to cite
- Anything that reaches a customer or spends money
What it works with
Reads
- Library
- Business metrics
- Support sources
- Sales records
- Signed events from your systems
Produces
- Automation reports
- Notifications
- Run conversations
Where founders use it
A morning report
Read every signup, demo and support case overnight and have the summary waiting at 7:00.
Prospect monitoring
Research the next groups to call every weekday before the team starts.
Reacting to your product
Send a signed event from your app and let an agent investigate when something happens.
How it compares with a workflow builder
In the Tablebird launch
It keeps working after launch day.
The Initiative sets up its own agents. One finds the next groups to call at 6:00. Another reads every signup, demo and support case and has a report on Ava’s desk by 7:00.
Follow the whole launchWhat people ask
- What can trigger an Automation?
- A schedule, a support report or customer reply from your connected source, or a signed event from any system you run.
- Who creates them?
- You, or an Initiative that needs recurring work. Automations an Initiative creates start paused.
- What happens if a run fails?
- It retries once after a crash or a provider failure, and notifies you either way.
- Are there built-in Automations?
- Yes. The Library Maintainer keeps your Library current daily, and the Support Responder handles support events.
- What do they run on?
- Your own Claude Code or Codex plan, like everything else in the workspace.
How it connects to the rest of the company
Every capability reads the same Library and reports into the same Initiatives.
Early access · macOS
Run your next launch from one conversation.
We’re onboarding a few founders and small teams each week, one at a time, starting with the launch you’re planning next.
We email you once, when your seat is ready.