Workflow platform

Stacksona for Dify

Put a Gate HTTP node or governed action service immediately before the Dify action that changes the outside world.

Where Gate goes

In the governed workflow branch before the side-effecting HTTP, tool, or action node.

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

Agent/router chooses branch→Gate HTTP/action service checks it→Action executes or branch returns

Start here

1
Build the final action.
Let Dify 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

If a Dify-managed tool cannot be intercepted before execution, expose that capability through a governed HTTP wrapper service and let Dify call the wrapper instead of the raw service.

Handle the decision

Outcome	Gate status	What Dify 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

Keep Dify LLM, Agent, router, and workflow logic unchanged.
Route changes_requested back to the LLM, template, or parameter revision path.
For long reviews, use callback or a separate continuation workflow.

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