Stacksona Docs / Platform docs
Platform docs

Integration Hub

Choose the Stacksona integration path for the platform your agents already use.

Choose the simplest path

Use a native Stacksona surface when one exists. Use a recipe only when the platform does not have a dedicated package yet.

n8n

Native

Install the community node and place Stacksona before risky workflow actions.

n8n-nodes-stacksona

Node and TypeScript

Native SDK

Use the SDK in custom agents, backend services, and approval sidecars.

@stacksona/sdk

MCP Clients

Native MCP

Expose Stacksona approval tools to MCP-compatible agent clients.

@stacksona/mcp-server

Custom REST

REST

Call Stacksona directly from any platform that supports HTTP.

Gate API

The call every recipe uses

Every platform recipe eventually does this: send the proposed action to Stacksona, then branch on the returned decision.

bash
curl -X POST "$STACKSONA_GATE_URL/api/agent/tasks/task_123/requests" \
  -H "Authorization: Bearer $STACKSONA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_name": "Customer Support",
    "task_label": "Approve customer email",
    "tool_name": "send_email",
    "subject": "Send reply to customer@example.com",
    "preview": "Agent drafted a customer-facing reply.",
    "risk_level": "medium"
  }'

Platform recipes

Recipes are implementation guides using HTTP, webhooks, the SDK, or a small bridge service. They are not native Stacksona packages unless marked as native.

OpenAI Agents SDK

Recipe

Wrap risky function tools so approval happens before the tool executes.

SDK wrapper or API sidecar
Tool callsGuardrailsSidecar

LangGraph

Recipe

Use Stacksona as the approval inbox and audit layer around graph pause, review, and resume patterns.

HTTP or Node approval bridge
GraphsInterruptResume

CrewAI

Recipe

Require Stacksona approval before CrewAI tools perform external, customer-facing, financial, or destructive actions.

Tool wrapper
Multi-agentToolsGovernance

LlamaIndex

Recipe

Route human input and approval points through Stacksona before LlamaIndex workflows continue.

Workflow event adapter
WorkflowsEventsReview

Dify

Recipe

Use Dify workflow nodes to request Stacksona approval, collect review decisions, and continue or stop the workflow.

HTTP request and human input nodes
No-codeHuman inputHTTP

Make

Recipe

Call Stacksona before Make scenarios write records, send messages, issue refunds, or call production APIs.

HTTP module
AutomationHTTPScenarios

Zapier Agents

Recipe

Insert Stacksona as a pre-action approval step before Zapier agents trigger app actions.

Webhook action
ActionsWebhooksRouting

Copilot Studio

Recipe

Route Copilot agent actions into Stacksona for review before Power Platform or external operations continue.

HTTP action
EnterpriseHTTPApprovals

Salesforce Agentforce

Recipe

Gate record mutations, customer actions, and workflow changes with Stacksona decisions.

Apex or Flow HTTP callout
CRMApexFlow

Google ADK

Recipe

Add approval checks before Google ADK tools take production, customer, or external actions.

Tool callback or sidecar
ADKToolsPolicy

GitHub Actions

Recipe

Require Stacksona approval before deploy, release, destructive repository operations, or production scripts.

curl or Node step
CI/CDDeployAudit

Decision routing

StatusWorkflow behavior
allowExecute the action immediately.
pending_reviewWait, poll briefly, or store the decision ID and resume through a callback.
approvedExecute the action and log the result.
reject or rejectedDo not execute. Route to fallback or manual handling.