Approvals

Any step in a workflow that acts on the outside world, or produces a result, can be set to ask for approval first. The run pauses at that step until a person decides, then continues with what they approved.

In one line

Turn on “Ask for approval” on a step, say who can decide, and the run waits. Approve from your Approvals inbox, from the run itself, or straight from the email — no sign-in required unless you turn that on too.

Turn it on for a step#

Open a workflow step that can carry a gate — Tool, API Call, Send Email, AI, Code, Image Generation, or Agent — and switch on Ask for approval in its config panel.

Where it holds#

A step that acts on something outside Adlyse (a Tool, API Call, or Send Email) is held before it runs, so the approver sees the exact inputs it’s about to send. A step that only produces a value (AI, Code, Image, Agent) is held after it runs, so the approver reviews the output before anything downstream uses it. This is fixed by the step type, not a choice you make.

Who can approve#

Pick Anyone who can provide input to workflows — the organization permission — or name specific people or roles. A step nobody is able to approve fails instead of waiting forever, so the config warns you if you name someone who doesn’t hold that permission.

The message#

Write what the approver should check. Type @ to pull in a value from an earlier step, so the message shows the real number or name it’s about, not a placeholder.

Extra controls#

Let the approver edit the values (before a “before” gate) or the result (after an “after” gate) as part of deciding, rather than only approve or reject as-is.
Require sign-in to approve if you don’t want the decision made straight from an emailed link.
If nobody decides — set how long the request waits (4 hours up to 30 days) before it expires and that branch of the run stops.

A gate can’t sit on a step inside a loop body — a loop can run hundreds of times, and nobody wants an inbox flooded with one approval per iteration.

Deciding one#

Whoever is named an approver hears about a pending request in three places, and any one of them is enough:

The Approvals inbox (sidebar, next to Workflows) lists every open request across your organization, badged with a count. It’s also where you find requests you’ve already decided.
The run itself shows an approval badge on the gated step; open the run to review and decide inline.
Email. The approver gets a message with what the step is about to do (or what it produced) and Approve / Reject / Review buttons. Opening the email decides nothing — only pressing a button does — so a link preview or a mail scanner can’t accidentally approve something.

Unless “Require sign-in” is on, the email link resolves straight to the request for that named approver, no login needed. With it on, the link asks them to sign in first.

Common flows#

Guard a send. Put a gate on the Send Email step of a client-facing workflow so a person reads the draft before it goes out.
Review before it acts. Gate the Tool or API Call step that would change a campaign, and let the approver edit the values (say, the new budget) before approving.
Spot-check AI output. Gate an AI or Agent step in a long pipeline so a person reads its output before the rest of the run builds on it.
Widen who can decide. Use “specific people or roles” to route a sensitive step to a manager instead of anyone with workflow permissions.

Workflows

Where approval gates live: one setting on the steps that can carry one.

Team

Grant “provide input to workflows” so someone can be named an approver.

Schedules

A scheduled run with a gated step still waits for a person — the clock only starts it.

Approvals

In one line

Turn it on for a step#

Open a workflow step that can carry a gate — Tool, API Call, Send Email, AI, Code, Image Generation, or Agent — and switch on Ask for approval in its config panel.

Where it holds#

Who can approve#

The message#

Write what the approver should check. Type @ to pull in a value from an earlier step, so the message shows the real number or name it’s about, not a placeholder.

Extra controls#

Let the approver edit the values (before a “before” gate) or the result (after an “after” gate) as part of deciding, rather than only approve or reject as-is.
Require sign-in to approve if you don’t want the decision made straight from an emailed link.
If nobody decides — set how long the request waits (4 hours up to 30 days) before it expires and that branch of the run stops.

A gate can’t sit on a step inside a loop body — a loop can run hundreds of times, and nobody wants an inbox flooded with one approval per iteration.

Deciding one#

Whoever is named an approver hears about a pending request in three places, and any one of them is enough:

The Approvals inbox (sidebar, next to Workflows) lists every open request across your organization, badged with a count. It’s also where you find requests you’ve already decided.

The run itself shows an approval badge on the gated step; open the run to review and decide inline.

Email. The approver gets a message with what the step is about to do (or what it produced) and Approve / Reject / Review buttons. Opening the email decides nothing — only pressing a button does — so a link preview or a mail scanner can’t accidentally approve something.

Unless “Require sign-in” is on, the email link resolves straight to the request for that named approver, no login needed. With it on, the link asks them to sign in first.

Common flows#

Guard a send. Put a gate on the Send Email step of a client-facing workflow so a person reads the draft before it goes out.

Review before it acts. Gate the Tool or API Call step that would change a campaign, and let the approver edit the values (say, the new budget) before approving.

Spot-check AI output. Gate an AI or Agent step in a long pipeline so a person reads its output before the rest of the run builds on it.

Widen who can decide. Use “specific people or roles” to route a sensitive step to a manager instead of anyone with workflow permissions.