MCP
A2A
Get Started
5-Minute Quickstart
Get your first integration running with step-by-step instructions
Browse Integrations
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:The Request Flow
When your agent calls an action, here’s what happens behind the scenes:
- Your agent calls an action with
account_id, scoping all operations to that end-user’s connection - StackOne authenticates with the provider using stored credentials
- StackOne transforms the request to the provider’s API format
- Provider returns raw, provider-specific data
- StackOne normalizes the response for the protocol/SDK being used
- Your agent receives well-scoped data optimized for the use-case at hand
Connect Your Agent
MCP Server
A2A Protocol
AI Toolset (SDK)
Compare Agent Protocols
Not sure which to choose? See detailed comparison with code examples.
Build with APIs
Actions API
POST /actions/rpc. The same layer that powers MCP and AI Toolset.Platform API
Unified APIs for cross-provider operations
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, BoxIAM
GET /iam/users returns consistent user data from Okta, Azure AD, Google WorkspaceLegacy 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.
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
- 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)
| 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 |
Dashboard & Setup
Connectors
Creating Connector Auth Configs
Connecting Accounts
AI Playground
