Workflow platform

Stacksona for Copilot Studio

Wrap governed Copilot actions in a connector, Power Automate flow, HTTP action, or service that checks Gate before execution.

Where Gate goes

Inside the action, connector, flow, or service that owns the real side effect.

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

Copilot selects action→Governed connector/flow checks Gate→Action executes or conversation continues

Start here

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

When a built-in action cannot be intercepted safely, replace the raw action with a governed connector or service wrapper that owns both the Gate check and the real execution.

Handle the decision

Outcome	Gate status	What Copilot Studio 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 conversation reasoning and action selection in the Microsoft stack.
Store exact review state in flow, conversation, or external durable state.
Return reviewer-requested changes to the Copilot or planning path.

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