Workflow platform

Stacksona for Zapier

Use Evaluate Action immediately before the app action, then resume the exact review thread when human review is required.

Where Gate goes

Between the agent or Zap decision and the real app action.

Keep the platform's normal reasoning and orchestration. Gate only the exact action at the last safe point before execution.

Agent/Zap chooses action→Evaluate Action checks Gate→App action executes or Zap waits

Start here

1
Build the final action.
Let Zapier choose the action and produce the arguments it intends to execute.
2
Check the exact action with Gate.
Send tool_name and the final payload immediately before the side effect.
3
Follow one of four outcomes.
Continue, wait, revise, or stop. You do not need the advanced features to get this basic path working.

Minimal setup

Stacksona Zapier surface	Use
Evaluate Action	Check the exact proposed action.
Decision Completed	Discover completed review work.
Find Decision	Fetch the current decision by exact `thread_id`.
Log Task Event	Add execution and task evidence.

Handle the decision

Outcome	Gate status	What Zapier should do
Continue	`allow` or `approved`	Execute the exact proposed action. If signed proof is required, validate it first.
Wait	`pending_review`	Store `thread_id` and resume that exact review later.
Revise	`changes_requested`	Return reviewer feedback to the part of the runtime that can revise the proposal.
Stop	`reject` or `rejected`	Do not execute. Replan, fall back, or end the action.

Unknown or failed decision = stop.

Fail closed if Gate cannot be reached, returns an unknown state, or required approval proof is missing or invalid.

Platform notes

Use thread_id for the exact review; task_id may group multiple checks.
Do not continue the app action while the decision is still pending.
Requested changes should return to the step that can revise the proposed action.

Advanced: review threads, revisions, proof, and audit

task_id is your grouping ID. thread_id identifies the exact Gate review and should be persisted whenever work can pause.

For changes_requested, revise on the same review thread using the revision event contract. For high-impact actions that require signed proof, validate the returned approval token before execution. Log execution success or failure when you need complete audit evidence.

For long reviews, use the platform's durable continuation mechanism instead of keeping a process, workflow, or runner open.

Advanced runtime patterns Full Gate API Exact decision states