Stacksona for n8n
Use the native Stacksona node immediately before the action you want to govern.
Directly before Gmail, HTTP, CRM, payment, database, or another side-effect node.
The workflow can keep normal AI Agent and routing logic. Stacksona checks the final action just before execution.
Minimal workflow
- 1Install.
Settings → Community Nodes →
n8n-nodes-stacksona. - 2Add credentials.
Use the Gate URL and
sg_agent API key. - 3Choose Request Decision and Wait.
Pass the exact final tool name and payload.
- 4Route only allow / approved forward.
Reject, rejected, and changes requested go to stop or revision branches.
Example
| Field | Value |
|---|---|
| Task ID | refund-{{$json.order_id}} |
| Tool Name | issue_refund |
| Subject | Refund order {{$json.order_id}} |
| Risk Level | high |
| Payload JSON | ={{ JSON.stringify({ order_id: $json.order_id, amount: $json.amount, currency: $json.currency }) }} |
No HTTP Request node, no Authorization header wiring, no manual polling loop, and no custom parsing of the normal Gate lifecycle.
Choose the operation by workflow shape
| Operation | Use it when |
|---|---|
| Request Decision and Wait | The review should finish inside the current execution window. |
| Request Decision | You want to persist thread_id and resume later. |
| Get Decision | You already know the thread or reusable task. |
| List Decisions | A scheduled resume flow needs recent pending/completed references. |
| Submit Revision | A reviewer requested changes and you have a revised proposal. |
| Validate Approval Token | The action requires signed one-time proof. |
| Log Event | You want execution or audit evidence in the task timeline. |
| Resolve Tools | Your agent needs registered Gate tool contracts before selection. |
Requested changes
The wait operation returns on changes_requested. Revise the proposal, then use Submit Revision with the same Task ID and Thread ID. The revision remains on the same human review.
Long reviews
Request Decision
↓
persist thread_id
↓
resume later
↓
Get Decision by thread_idUse this instead of keeping one n8n execution open indefinitely.
Signed approvals
Run Validate Approval Token before the real side effect when proof is required and branch on valid, not HTTP success alone.