Create an automation
Creates an empty automation. It is a draft until you publish a version with POST /v1/automations/{automation_id}/versions. It is often easier to ask the agent to build one with an agent task.
Requires the automations:write permission.
Authorizations
An API key from Settings → API keys, sent as Authorization: Bearer jb_live_…
Body
The name.
1 - 80A short name, unique among your automations.
^[a-z0-9][a-z0-9-]{0,63}$Put the automation in a project you can edit.
64Pause after this many failures in a row.
1 <= x <= 100Response
The automation.
An automation.
The automation id.
The name.
Whether it starts on its triggers. A paused automation is not enabled.
draft (nothing published), attention (needs the person), paused or active.
draft, attention, paused, active The account that owns it.
A short name used in addresses.
The live version. Null for a draft.
Why it paused: manual, failures or budget.
manual, failures, budget, null When it paused.
It pauses after this many failures in a row.
What it does.
Whether the description was written by a person rather than taken from the package.
The monthly spending limit in US dollars.
The monthly spending limit in credits.
Whether it may take actions without asking.
Spending limits by service in US dollars.
Spending limits by service (ai, agent) in credits.
When it was created.
The project it belongs to.
The account's role on it.
owner, editor, viewer Why it needs the person.
missing_secrets, missing_accounts, account_expired, question, approval, consent, build_failed, paused_after_failures, paused_for_budget, failing Secret names the live version needs and does not have.
Connected-account slots that are not usable.
Whether a run is in progress.
How the automation has been doing.