stackone-connectors

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

StackOne Connectors — Integration Discovery

StackOne连接器——集成发现

Important

重要说明

Connector availability changes frequently as StackOne adds new providers. Before answering:

Fetch

https://docs.stackone.com/connectors/introduction

for the current connector list

For specific provider capabilities, fetch the relevant category API reference

Never assume a connector exists or doesn't exist without checking live docs.

连接器的可用情况会随着StackOne新增供应商而频繁变化。回答前请先：

调用

https://docs.stackone.com/connectors/introduction

获取当前的连接器列表

若需了解特定供应商的功能，请调用对应类别的API参考文档

切勿在未查阅实时文档的情况下假设某连接器存在或不存在。

Instructions

操作指南

Step 1: Identify the user's integration need

步骤1：明确用户的集成需求

Common patterns:

"What providers do you support for X?" → Check the category (HRIS, ATS, CRM, etc.) in the connectors page
"Can I do Y with provider Z?" → Check the provider's supported actions in the API reference
"Recommend an integration for my use case" → Match the use case to a category, then list available providers

常见场景：

“你们支持哪些X类别的供应商？” → 在连接器页面中筛选对应类别（HRIS、ATS、CRM等）
“我可以通过供应商Z执行Y操作吗？” → 在API参考文档中查看该供应商支持的操作
“为我的用例推荐一款集成工具” → 将用例与对应类别匹配，然后列出可用的供应商

Step 2: Look up connector availability

步骤2：查询连接器的可用情况

Fetch

https://docs.stackone.com/connectors/introduction

for the full, current list.

Consult

references/category-overview.md

for a snapshot of categories and example providers. But always verify against live docs since new connectors are added regularly.

调用

https://docs.stackone.com/connectors/introduction

获取完整的当前连接器列表。

可参考

references/category-overview.md

获取类别及示例供应商的快照，但由于StackOne会定期新增连接器，务必以实时文档为准。

Step 3: Check available actions for a provider

步骤3：查询特定供应商的可用操作

Each connector exposes its own set of provider-specific actions. Action counts vary significantly — Salesforce has 370+ actions, HubSpot has 100+, while smaller providers may have a handful.

To find what's available for a specific provider:

Fetch

https://docs.stackone.com/connectors/introduction

Find the provider and check its listed actions

For action details, fetch

https://docs.stackone.com/platform/api-reference/actions/make-an-rpc-call-to-an-action

Actions are named

{provider}_{operation}_{entity}

(e.g.,

bamboohr_list_employees

salesforce_get_contact

每个连接器都有其专属的供应商操作集合，操作数量差异较大——Salesforce有370+操作，HubSpot有100+操作，而小型供应商可能仅有少量操作。

查询特定供应商的可用操作：

调用

https://docs.stackone.com/connectors/introduction

找到该供应商并查看其列出的操作

若需了解操作详情，调用

https://docs.stackone.com/platform/api-reference/actions/make-an-rpc-call-to-an-action

操作命名格式为

{供应商}_{操作}_{实体}

（例如：

bamboohr_list_employees

、

salesforce_get_contact

）。

Step 4: Execute actions via the Actions API

步骤4：通过Actions API执行操作

All actions are executed through StackOne's Actions API:

bash

curl -X POST https://api.stackone.com/actions/rpc \
  -H "Authorization: Basic $(echo -n 'YOUR_API_KEY:' | base64)" \
  -H "x-account-id: ACCOUNT_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "bamboohr_list_employees"
  }'

AI agents typically call actions via the SDK or MCP rather than raw API calls — see the

stackone-agents

skill for SDK/MCP integration.

Fetch

https://docs.stackone.com/platform/api-reference/actions/make-an-rpc-call-to-an-action

for the full RPC reference.

所有操作均通过StackOne的Actions API执行：

bash

curl -X POST https://api.stackone.com/actions/rpc \
  -H "Authorization: Basic $(echo -n 'YOUR_API_KEY:' | base64)" \
  -H "x-account-id: ACCOUNT_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "bamboohr_list_employees"
  }'

AI Agent通常通过SDK或MCP调用操作，而非直接调用原始API——如需SDK/MCP集成，请查看

stackone-agents

技能。

调用

https://docs.stackone.com/platform/api-reference/actions/make-an-rpc-call-to-an-action

获取完整的RPC参考文档。

Step 5: Test before building

步骤5：构建前测试

AI Playground: https://app.stackone.com/playground — test API calls interactively

MCP Inspector:

npx @modelcontextprotocol/inspector https://api.stackone.com/mcp

— test via MCP

Postman: importable collection available from the docs

AI Playground：https://app.stackone.com/playground —— 交互式测试API调用

MCP Inspector：

npx @modelcontextprotocol/inspector https://api.stackone.com/mcp

—— 通过MCP测试

Postman：可从文档中导入可用的集合

Release stages

发布阶段

Stage	Meaning	Recommendation
GA	Production-ready, fully supported	Safe for production
Beta	Stable for testing, minor changes possible	OK for non-critical flows
Preview	Early-stage, expect breaking changes	Development/testing only

阶段	含义	建议
GA	可用于生产环境，完全受支持	可安全用于生产环境
Beta	测试稳定，可能存在微小变更	可用于非核心流程
Preview	早期阶段，可能出现破坏性变更	仅用于开发/测试

Examples

示例

Example 1: User wants to know what HR integrations are available

示例1：用户想了解有哪些HR集成工具可用

User says: "Which HRIS tools does StackOne support?"

Actions:

Fetch

https://docs.stackone.com/connectors/introduction

Filter for the HRIS category
List available providers with their release stages and action counts
For specific providers the user is interested in, list their available actions

Result: Current list of HRIS connectors with per-provider action counts.

用户提问：“StackOne支持哪些HRIS工具？”

操作步骤：

调用

https://docs.stackone.com/connectors/introduction

筛选HRIS类别
列出可用供应商及其发布阶段和操作数量
若用户对特定供应商感兴趣，列出其可用操作

结果：当前HRIS连接器列表及各供应商的操作数量。

Example 2: User wants to know what they can do with a specific provider

示例2：用户想了解通过特定供应商可执行哪些操作

User says: "What can I do with BambooHR through StackOne?"

Actions:

Fetch

https://docs.stackone.com/connectors/introduction

and find BambooHR

List the available actions (e.g.,

bamboohr_list_employees

bamboohr_get_employee

, etc.)

Explain the Actions API for executing them, or recommend using the SDK/MCP for agent integration
Fetch the Actions RPC reference for payload details if they need the raw API

Result: Full list of BambooHR actions with how to call them.

用户提问：“我可以通过StackOne对BambooHR执行哪些操作？”

操作步骤：

调用

https://docs.stackone.com/connectors/introduction

并找到BambooHR

列出可用操作（例如：

bamboohr_list_employees

、

bamboohr_get_employee

等）

说明如何通过Actions API执行这些操作，或推荐使用SDK/MCP进行Agent集成
若用户需要原始API的详细信息，调用Actions RPC参考文档获取负载详情

结果：BambooHR的完整操作列表及调用方法。

Example 3: User needs a connector that doesn't exist

示例3：用户需要的连接器不存在

User says: "Does StackOne support our custom HR tool?"

Actions:

Check the connectors page — it may exist under a different name
If not found, explain two options: a. Request it:
```
https://docs.stackone.com/connectors/add-new
```
b. Build it: use the Connector Engine (see
```
stackone-cli
```
skill)
If they have budget/urgency, recommend the AI Builder for faster custom connector development

Result: Clear path forward — either request or build.

用户提问：“StackOne是否支持我们的自定义HR工具？”

操作步骤：

检查连接器页面——该工具可能以其他名称列出
若未找到，说明两种方案： a. 申请添加：
```
https://docs.stackone.com/connectors/add-new
```
b. 自行构建：使用Connector Engine（请查看
```
stackone-cli
```
技能）
若用户有预算或需求紧急，推荐使用AI Builder快速开发自定义连接器

结果：清晰的后续方案——申请添加或自行构建。

Troubleshooting

故障排除

Can't find a specific provider

找不到特定供应商

Cause: Provider may be listed under a different name, or may not be supported yet.

Search the connectors page by the provider's official name
Check if it's under a parent company name (e.g., "Microsoft Entra ID" not "Azure AD")
If not found, suggest requesting it or building a custom connector

原因：供应商可能以其他名称列出，或暂未被支持。

使用供应商的官方名称在连接器页面搜索
检查是否归属于母公司名称下（例如：“Microsoft Entra ID”而非“Azure AD”）
若未找到，建议用户申请添加或自行构建自定义连接器

Action returns "not supported" for a provider

针对某供应商执行操作时返回“不支持”

Cause: The requested action doesn't exist for this provider.

Each provider has its own set of actions — check the connectors page for what's available
Action names include the provider prefix (e.g.,
```
bamboohr_list_employees
```
not
```
list_employees
```
)
Some actions require specific OAuth scopes on the provider side

原因：该操作在该供应商中不存在。

每个供应商都有其专属的操作集合——请查看连接器页面了解可用操作
操作名称包含供应商前缀（例如：
```
bamboohr_list_employees
```
而非
```
list_employees
```
）
部分操作需要供应商端的特定OAuth权限

Connector logos not loading

连接器图标无法加载

Cause: Incorrect slug format.

Logo URL format:

https://stackone-logos.com/api/{connector-slug}/filled/png

Slugs are lowercase, hyphenated (e.g.,
```
bamboo-hr
```
,
```
google-drive
```
)
Fetch the connectors page to verify the exact slug

原因：Slug格式错误。

图标URL格式：

https://stackone-logos.com/api/{connector-slug}/filled/png

Slug为小写、连字符分隔格式（例如：
```
bamboo-hr
```
、
```
google-drive
```
）
调用连接器页面验证准确的Slug