Configuration
| Field | What it does |
|---|---|
| Title | Short title shown on the approval card |
| Form Fields | Fields the reviewer sees. Each has a name, type (string, number, boolean, select, media), label, and a pre-filled value that can reference upstream data, e.g. {{http-1.amount}} |
Reviewing requests
Pending requests live in the Feed tab in the top navigation (shortcutG then A). A badge shows how many are waiting.
Each card shows the form fields filled with their resolved values. The reviewer can edit the values, then click Approve or Reject. The run resumes down the matching output handle:
| Handle | When it runs |
|---|---|
| Approved | The request was approved |
| Rejected | The request was rejected |
{{approval-id.values.field_name}}.
Example: an agent drafts a tweet, an Approval node shows it in a tweet_text field, and the Approved branch posts {{approval-id.values.tweet_text}} to X. The reviewer can tweak the wording right in the card before approving.
While a request is pending, the execution shows a waiting status in Execution logs. The card also links back to the workflow and node that created it.