Autonomy — what runs on its own, and what asks first
Set per automation whether it runs, notifies, or asks a human first — graded by whether the action can be undone.
Most tools grade an agent’s autonomy by how much you trust the model. Fleet grades it by the consequence of the action — because a wrong reversible action is a retry, and a wrong irreversible one is an incident.
Auto-run
Reversible
Runs immediately, logged. Drafting a reply, updating a record, enriching a lead.
Notify
Worth knowing
Runs, then posts to the owner’s channel. Nobody has to click.
Ask first
Irreversible / costly
Pauses and asks a human before acting. Refunds, publishing, granting access.
Off
Disabled
Paused entirely — nothing runs.
Default policy:auto-run reversible actions · ask first before irreversible ones · never run an action Fleet can’t classify. This rides n8n’s existing approval delivery (Send & Wait across 9 channels) — Fleet only decides when a human is asked, who, and records the answer.
Per-automation policy
23 automations · ordered by consequencenames Live + seeded consequence Derived level FleetIrreversible
Lena Brandt · unconfirmed
Irreversible
Dana Okafor · unconfirmed
Irreversible
Raj Menon · unconfirmed
Irreversible
Mark Reuben · deactivated
approval step not found
Irreversible
unassigned — nobody has claimed this
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Costly to undo
no interruptions
Reversible
no interruptions
Reversible
no interruptions
Reversible
no interruptions
Every level shown is the default Fleet computed from the row’s consequence class — nobody has set one. Levels live in Fleet’s autonomy_policy table because n8n has no field for them; changing a control here stays in the browser and is not written back.
One automation takes an action classified as irreversible and no approval step was found in its graph. n8n records no gate flag, so this is unverified rather than proven absent — a gate may exist in a form Fleet cannot read.
Routing comes from ownership, and 1 of these is unassigned — nobody has claimed it. An ask-first policy with no owner has nobody to ask, which is itself the finding. The delivery surface (Slack, Teams, email) is not configured on this instance; n8n’s Send & Wait is what would carry the message once it is.