Skip to main content
You don’t need an agent to use a connector. Any backend, script, or workflow can call an action directly — over the Actions API or with the SDK used standalone.

Calling actions

Make an RPC call to any enabled action with the same two values every protocol and SDK uses: your StackOne API key and the end-user’s x-account-id. The RPC endpoint routes the request to that account’s provider, handles authentication, transforms the request to match the provider API, and returns normalized data. If you don’t already know which action you need, discover what’s available with GET /actions first, then call it with POST /actions/rpc:
Authenticate with your API key as Basic auth, and pass the linked account’s ID in the x-account-id header.

Discover available actions

Call the action

POST actions/rpc request parameters

Query parameters — Workday: list employees
Request body — Greenhouse: create candidate
Path parameters — Salesforce: get contact

GET /actions

API reference for actions metadata.

POST /actions/rpc

API reference for the RPC endpoint.

When to use this

  • Syncing or enriching data in a backend job
  • Triggering an action from your own app logic
  • Scripting one-off tasks against a provider
For agent-driven use:

MCP

Open standard for AI tools. Works with Claude, Cursor, Vercel AI, n8n

Agent SDK

Native TypeScript/Python with framework integrations (LangChain, CrewAI, OpenAI)

A2A

Call a pre-built agent per integration — for multi-agent orchestration.