StackOne 101

Connect your AI agents to 10,000+ actions across hundreds of SaaS integrations.

StackOne is the AI Integration Gateway. Connect your AI agents to any SaaS system, yours or your users’, with any AI framework or protocol. One gateway. Hundreds of systems. Thousands of actions.

---

Get Started

5-Minute Quickstart

Get your first integration running with step-by-step instructions

Browse Available Connectors

Explore 200+ supported providers: Salesforce, Workday, Slack, and more

Key Concepts

Before diving in, here are the core building blocks you’ll work with:

Actions

An Action is an operation your agent can perform. It’s the core unit of work in StackOne.

Type	Description	Example
Standard Actions	Provider-specific operations mapping directly to a provider’s API	salesforce_get_contact, gmail_list_messages
Unified Actions	Normalized operations with consistent schemas across providers	iam_list_users, documents_list_files

StackOne provides 10,000+ actions across all integrations, plus webhooks to receive events from connected systems.

Connectors

Browse and test all available connector actions in the dashboard

Linked Accounts

A Linked Account represents one end-user’s authenticated connection to one provider. When your customer connects their Salesforce, Slack, or any other system through the Integration Hub, StackOne creates a linked account.

Field	Description	Example
account_id	Unique identifier for API calls	acme-corp-bamboohr
origin_owner_id	End-user’s ID in your system	cust_12345
provider	The connected SaaS system	bamboohr

Connect Tools Overview

Learn about tools for connecting end-user accounts

Unified Authentication

One API key authenticates your app. One header routes to the right end-user:

Authorization: Basic {base64_encoded_api_key}
x-account-id: {customer_account_id}

No OAuth token refresh logic. No per-provider credential management. Consistent auth across 200+ providers.

---

The Request Flow

When your agent calls an action, here’s what happens behind the scenes:

1. Your agent calls an action with account_id, scoping all operations to that end-user’s connection
2. StackOne authenticates with the provider using stored credentials
3. StackOne transforms the request to the provider’s API format
4. Provider returns raw, provider-specific data
5. StackOne normalizes the response for the protocol/SDK being used
6. Your agent receives well-scoped data optimized for the use-case at hand

What StackOne handles: OAuth token refresh, rate limiting, retry logic, schema normalization, error handling, and audit logging.

---

Connect Your Agent

MCP Server

Native tool calling via Model Context Protocol for Claude, Cursor, n8n, and any MCP-compatible client.

A2A Protocol

Agent-to-Agent communication for orchestrating complex multi-agent workflows.

AI Toolset (SDK)

Python and TypeScript libraries with built-in tool definitions for LangChain, CrewAI, Vercel AI.

Compare Agent Protocols

Not sure which to choose? See detailed comparison with code examples.

Build with APIs

Actions API

Execute any of 10,000+ actions via POST /actions/rpc. The same layer that powers MCP and AI Toolset.

Platform API

Manage linked accounts, sessions, and connectors

Unified APIs for cross-provider operations

Unified APIs provide consistent REST endpoints when you need the same operation across multiple providers. Useful for building provider-agnostic backends.

Documents

GET /documents/files works the same for Google Drive, SharePoint, Dropbox, Box

IAM

GET /iam/users returns consistent user data from Okta, Azure AD, Google Workspace

Legacy Unified APIs: HRIS and ATS unified endpoints are still available for existing integrations. See the HRIS API Reference and ATS API Reference for documentation. For new implementations, we recommend using the Actions API for greater flexibility.

Actions API vs Unified API: Use Actions API when you need provider-specific features or want dynamic tool discovery. Use Unified APIs when building traditional REST integrations that must work identically across providers.

---

Organization & Projects

Organization is your company’s StackOne account. It contains:

• All team members and their roles
• Billing and subscription details
• All projects within your company

Project is an isolated workspace within your organization. Each project has:

• Its own API keys (credentials don’t cross projects)
• Its own integrations and configurations
• Its own linked accounts (end-user connections)
• Regional data residency settings (US, EU)

Common project strategies:

Strategy	Example	Use Case
Environment isolation	dev, staging, production	Separate test data from real end-users
Regional data isolation	us-prod, eu-prod	GDPR compliance, data residency
Team separation	team-a-sandbox	Temporary projects for experimentation

Start with a single project for evaluation. You can then create additional projects if needed for production with appropriate regional settings.

Dashboard & Setup

Connectors

Browse 10,000+ actions across all providers

Creating Connector Auth Configs

Enable Connectors by selecting and configuring authentication options

Connecting Accounts

Embed the connection flow for end-user onboarding

AI Playground

Test actions with natural language and see real responses

Build Custom Connectors

Connector Engine

Build and deploy custom connectors with the StackOne CLI

AI Builder

AI-assisted connector development