Skip to main content
An action step lets a workflow do more than read: update an operational system, send a corrective notice, open a ticket or publish a report.

​
Add an action step

Declare a terminal action step with:
  • A static directive, or the Slack directive source.
  • An approval setting:
    • approval: false for deliberate auto-execution.
    • approval: true for the built-in approval.
    • An approval-policy ID, to use a configured policy.

​
The action lifecycle

1

Plan

AgentFlow builds a concrete execution plan from the directive and earlier outputs.
2

Freeze

The exact plan and its input context are frozen.
3

Approve, when required

The frozen plan goes through the configured email or Slack policy.
4

Execute

The frozen plan runs after approval, or immediately when approval is off.
5

Audit

The plan, decisions, changes, result and audit events are kept.

​
Approval policies

Set approval policies in the project’s Settings under Action policies. Policies support:
  • Email or Slack approvers
  • Reminders and escalation levels
  • An exhaust behavior, such as rejection or expiration
An approver can approve, reject, or request bounded changes. A change request makes AgentFlow replan in a controlled way. Approval is an explicit policy, not something every action gets automatically. Match the control to the consequence of the action.
Last modified on October 1, 2026