Platform guide

Stacksona for Copilot Studio

Q: What statuses should my workflow allow?

Execute the gated action only on allow or approved. Stop, retry, notify, or route to fallback for every other state.

Use an HTTP action or connector-style action to call Stacksona before Copilot workflows trigger external systems or Power Platform operations.

RecipeNo native package yetSurface: HTTP action

Use HTTP actions or connector-style actions to route agent approvals through Stacksona before external operations continue. This page shows the recommended integration pattern using HTTP, a wrapper, or a small bridge service.

Start with this decision step

Every recipe should create a Stacksona decision before the platform executes the risky action.

pseudo

1. Agent prepares a risky action.
2. Platform calls Stacksona with action details.
3. If decision is allow or approved, execute the action.
4. If decision is pending_review, wait, poll, or resume through callback.
5. If decision is reject or rejected, do not execute.

Recommended pattern

Step	Description
Action proposal	The copilot prepares the action details and sends them to Stacksona.
Approval	Stacksona handles review, policy, and signed decision.
Continuation	The Copilot flow continues only after allow or approved. Rejected actions route to a safe response.

Example

bash

curl -X POST "$STACKSONA_GATE_URL/api/agent/tasks/task-refund-8821/requests"   -H "Authorization: Bearer $STACKSONA_API_KEY"   -H "Content-Type: application/json"   -d '{
    "workflow_name": "Customer Support",
    "task_label": "Refund request for order #8821",
    "tool_name": "issue_refund",
    "subject": "Issue a $500 refund to customer cus_99",
    "risk_level": "high",
    "payload": { "amount": 500, "currency": "usd", "customer_id": "cus_99" }
  }'

Decision handling

Status	Workflow behavior
`allow`	Continue immediately.
`reject`	Stop the action before execution.
`pending_review`	Pause, poll, or wait for callback. Continue only after approved.
`approved`	Execute the action. Validate token first when signed approval is required.
`rejected`	Do not execute. Route to fallback, manual task, or safe response.

Integration FAQ

Can I use Stacksona with Copilot Studio today?

Yes. Use the documented native package when one exists. Otherwise, use the REST API, HTTP module, webhook action, or a small Node sidecar with @stacksona/sdk.

Where should Stacksona sit in a Copilot Studio workflow?

Place Stacksona immediately before the action that sends, updates, deletes, refunds, posts, deploys, or calls a production API.

What statuses should my workflow allow?

Execute the gated action only on allow or approved. Stop, retry, notify, or route to fallback for every other state.