sales-tray

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Tray.ai Platform Help

Tray.ai平台帮助

Step 1 — Gather context

步骤1 — 收集上下文

references/learnings.md

exists, read it first for accumulated platform knowledge.

Ask the user:

What do you need help with?
- A) Workflow building — connectors, triggers, steps, data mapping
- B) Merlin Agent Builder — AI agents, knowledge, tools, MCP
- C) Tray Embedded — embedding integrations in your SaaS product (Solutions, Solution Instances, Configuration Wizard)
- D) API Management — rate limiting, throttling, governance
- E) Connector Development Kit (CDK) — building custom connectors
- F) GraphQL API — Embedded API, Master/User tokens, mutations
- G) Deployment / environments / governance — Enterprise Core, SSO, audit logging
- H) Monitoring / troubleshooting — workflow errors, debugging, rate limits
- I) Pricing / licensing — task consumption, editions, cost optimization
- J) Evaluating Tray vs other iPaaS platforms
- K) Something else — describe it
What edition are you on?
- A) Pro
- B) Team
- C) Enterprise
- D) Tray Embedded (separate SKU)
- E) Not sure / evaluating
What's your role?
- A) Integration engineer (builds workflows)
- B) SaaS product team (embedding Tray in your app)
- C) Admin / architect (governance, security, deployment)
- D) AI/automation builder (Merlin agents)
- E) Evaluating Tray

Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask 1-2 critical clarifying questions.

若

references/learnings.md

文件存在，请先阅读以获取积累的平台知识。

询问用户：

您需要哪方面的帮助？
- A) 工作流构建——连接器、触发器、步骤、数据映射
- B) Merlin Agent Builder——AI Agent、知识库、工具、MCP
- C) Tray Embedded——将集成嵌入您的SaaS产品（解决方案、解决方案实例、配置向导）
- D) API管理——速率限制、流量控制、治理
- E) 连接器开发工具包（CDK）——构建自定义连接器
- F) GraphQL API——嵌入式API、主/用户令牌、变更操作（mutations）
- G) 部署/环境/治理——Enterprise Core、SSO、审计日志
- H) 监控/故障排查——工作流错误、调试、速率限制
- I) 定价/许可——任务消耗、版本、成本优化
- J) 评估Tray与其他iPaaS平台
- K) 其他——请描述
您使用的是哪个版本？
- A) Pro
- B) Team
- C) Enterprise
- D) Tray Embedded（独立SKU）
- E) 不确定/正在评估
您的角色是什么？
- A) 集成工程师（构建工作流）
- B) SaaS产品团队（在应用中嵌入Tray）
- C) 管理员/架构师（治理、安全、部署）
- D) AI/自动化构建者（Merlin Agent）
- E) 正在评估Tray

跳过规则：如果用户的提示已提供足够上下文，直接跳至步骤2。先基于合理假设（需明确说明）给出最佳答案，再提出1-2个关键澄清问题。

Step 2 — Route or answer directly

步骤2 — 路由或直接解答

Problem domain	Route to
Connecting Tray to Salesforce/HubSpot/CRM	`/sales-integration {question}`
CRM comparison — Salesforce vs HubSpot vs others	`/sales-crm-selection {question}`
Salesforce-specific config (Flows, Apex, SOQL)	`/sales-salesforce {question}`
Simple no-code Zapier/Make automations	`/sales-integration {question}`
Workato-specific questions	`/sales-workato {question}`
MuleSoft-specific questions	`/sales-mulesoft {question}`
Boomi-specific questions	`/sales-boomi {question}`
SnapLogic-specific questions	`/sales-snaplogic {question}`
Celigo-specific questions	`/sales-celigo {question}`
Jitterbit-specific questions	`/sales-jitterbit {question}`
CRM data quality / deduplication	`/sales-data-hygiene {question}`
Workflow design and task optimization	Answer directly — read platform guide
Tray Embedded integration	Answer directly — read platform guide
Merlin Agent Builder	Answer directly — read platform guide
GraphQL API / solution instances	Answer directly — read API reference
Pricing and cost optimization	Answer directly — read platform guide

When routing, provide the exact command.

问题领域	路由至
将Tray与Salesforce/HubSpot/CRM连接	`/sales-integration {question}`
CRM对比——Salesforce vs HubSpot及其他	`/sales-crm-selection {question}`
Salesforce专属配置（Flows、Apex、SOQL）	`/sales-salesforce {question}`
简单无代码Zapier/Make自动化	`/sales-integration {question}`
Workato专属问题	`/sales-workato {question}`
MuleSoft专属问题	`/sales-mulesoft {question}`
Boomi专属问题	`/sales-boomi {question}`
SnapLogic专属问题	`/sales-snaplogic {question}`
Celigo专属问题	`/sales-celigo {question}`
Jitterbit专属问题	`/sales-jitterbit {question}`
CRM数据质量/去重	`/sales-data-hygiene {question}`
工作流设计与任务优化	直接解答——阅读平台指南
Tray Embedded集成	直接解答——阅读平台指南
Merlin Agent Builder	直接解答——阅读平台指南
GraphQL API/解决方案实例	直接解答——阅读API参考文档
定价与成本优化	直接解答——阅读平台指南

路由时，请提供准确命令。

Step 3 — Tray platform reference

步骤3 — Tray平台参考

Read
references/platform-guide.md
for the full platform reference — modules, pricing, connectors, Merlin agents, Tray Embedded, rate limits, governance.

Answer the user's question using only the relevant section. Don't dump the full reference.

If the question involves the GraphQL Embedded API (solution instances, user tokens, authentications), also read
references/tray-api-reference.md
for endpoints, authentication, and mutation details.

**阅读

references/platform-guide.md

**获取完整平台参考——模块、定价、连接器、Merlin Agent、Tray Embedded、速率限制、治理等内容。

仅使用相关部分解答用户问题，不要输出完整参考内容。

如果问题涉及GraphQL Embedded API（解决方案实例、用户令牌、身份验证），还需**阅读

references/tray-api-reference.md

**获取端点、身份验证和变更操作的详细信息。

Step 4 — Actionable guidance

步骤4 — 可操作指导

You no longer need the platform guide — focus on the user's specific situation.

Connector selection shortcut: Check Tray's connector library first (700+ pre-built). If no connector exists, use the HTTP Client connector for any REST API, or build a custom connector with the Connector Development Kit (

falafel

Node.js framework).

Cost optimization shortcut: Task-based billing — each workflow step counts. Audit high-volume workflows, remove redundant steps, use branching to skip unnecessary actions. Enterprise contracts typically start at $36K/year; model task consumption before signing and negotiate usage caps.

Debugging shortcut: Use the workflow Debug panel to step through execution and inspect input/output at each step. For the Embedded API, inspect GraphQL responses for

errors

array — Tray returns HTTP 200 with an

errors

field even on failure. Check connection auth status; expired auths silently fail.

Tray Embedded shortcut: Solution instances are per-end-user copies of a Solution. Use Master Token for org-wide operations (Get Users, create Solution Instance). Use User Token (created via

createUserToken

mutation) for per-end-user operations (Get Solution Instances, update config). All API calls must be server-side — CORS blocks browser calls.

If you discover a gotcha, workaround, or tip not covered in

references/learnings.md

, append it there.

您无需再依赖平台指南——聚焦用户的具体场景。

连接器选择捷径：先查看Tray的连接器库（700+预构建）。如果没有对应连接器，使用HTTP Client连接器对接任何REST API，或通过连接器开发工具包（CDK，基于

falafel

Node.js框架）构建自定义连接器。

成本优化捷径：基于任务计费——每个工作流步骤都算入任务量。审核高流量工作流，移除冗余步骤，使用分支逻辑跳过不必要操作。企业版合同通常起价为每年36000美元；签约前需预估任务消耗并协商使用上限。

调试捷径：使用工作流调试面板逐步执行，检查每个步骤的输入/输出。对于嵌入式API，检查GraphQL响应中的

errors

数组——即使失败，Tray仍会返回HTTP 200并包含

errors

字段。检查连接的身份验证状态；过期的身份验证会静默失败。

Tray Embedded捷径：解决方案实例是解决方案的每个终端用户副本。使用主令牌（Master Token）执行组织级操作（获取用户、创建解决方案实例）。使用用户令牌（通过

createUserToken

变更操作创建）执行终端用户级操作（获取解决方案实例、更新配置）。所有API调用必须在服务端执行——CORS会阻止浏览器端调用。

如果发现

references/learnings.md

未涵盖的陷阱、变通方法或技巧，请添加至该文件中。

Gotchas

常见陷阱

Best-effort from research — review these, especially pricing details and feature availability which change frequently.

No public pricing page. Tray is sales-led — no self-service signup, no published tier pricing. Public third-party sources conflict by an order of magnitude (Pro quoted at both $99/mo and $595/mo). Enterprise contracts typically start at $36K/year. Always get a written quote before committing.
Task-based billing escalates unpredictably in production. The most common user complaint across G2/Capterra reviews: task consumption in production exceeds estimates. Model expected task volume carefully and ask Tray sales for consumption alerts and soft caps before signing.
GraphQL backend-only — CORS blocks client-side calls. "The Tray GraphQL API is a backend API only and calls must be invoked server-side." You cannot call the Embedded API from a browser. All integration UI in your SaaS product must route through your backend.
Two token types with different scopes. Master Token = entire org workspace (used for
```
Get Users
```
, admin mutations). User Token = single end user (used for
```
Get Solution Instances
```
,
```
updateSolutionInstance
```
). Some endpoints (e.g.,
```
Get Authentications
```
) accept both. Use the wrong token and you'll get empty results or auth errors.
Rate limits: 30 req/sec, 1800 req/min, burst 50/sec. Call connector endpoint has separate concurrency limit of 1000 active requests. Docs don't specify which HTTP response code is returned when exceeded — monitor for rate-limit errors and implement exponential backoff.
Documentation gaps are a consistent complaint. G2 and Capterra reviewers repeatedly note thin docs, missing real-world examples, and steep learning curve for advanced features. Budget training time and pair new builders with experienced ones.
Regional base URLs differ. US:
```
tray.io/graphql
```
. EU:
```
eu1.tray.io/graphql
```
. APAC:
```
ap1.tray.io/graphql
```
. Whitelabel OAuth redirects use
```
{org}.integration-authentication.com/oauth2/token
```
. Using the wrong region returns empty results without an obvious error.
Tray.io → Tray.ai rebrand. The product rebranded to Tray.ai in 2024 with heavy AI/Merlin pivot.
```
tray.io
```
now 301-redirects to
```
tray.ai
```
, but API surface and developer docs still use
```
tray.io
```
domains. Both work in documentation links.

基于研究的最佳总结——请重点关注这些内容，尤其是频繁变动的定价细节和功能可用性。

无公开定价页面。Tray由销售主导——无自助注册，无公开分层定价。第三方公开来源的报价差异极大（Pro版报价既有每月99美元，也有每月595美元）。企业版合同通常起价为每年36000美元。签约前务必获取书面报价。
基于任务的计费在生产环境中会不可预测地上涨。G2/Capterra评论中最常见的用户投诉：生产环境中的任务消耗超出预估。需仔细预估预期任务量，并在签约前要求Tray销售提供消耗警报和软上限。
GraphQL仅支持服务端调用——CORS会阻止客户端调用。“Tray GraphQL API仅为服务端API，调用必须在服务端发起。”您无法从浏览器调用嵌入式API。SaaS产品中的所有集成UI必须通过您的服务端路由。
两种令牌类型具有不同的作用域。主令牌（Master Token）= 整个组织工作区（用于
```
Get Users
```
、管理员变更操作）。用户令牌（User Token）= 单个终端用户（用于
```
Get Solution Instances
```
、
```
updateSolutionInstance
```
）。部分端点（如
```
Get Authentications
```
）接受两种令牌。使用错误令牌会导致返回空结果或身份验证错误。
速率限制：30请求/秒，1800请求/分钟，突发上限50请求/秒。调用连接器端点有单独的并发限制：1000个活跃请求。文档未说明超出限制时返回的HTTP响应代码——需监控速率限制错误并实现指数退避机制。
文档缺失是普遍投诉。G2和Capterra评论者反复提到文档内容单薄、缺乏真实场景示例、高级功能学习曲线陡峭。需预留培训时间，并让新构建者与经验丰富的人员结对工作。
区域基础URL不同。美国：
```
tray.io/graphql
```
。欧盟：
```
eu1.tray.io/graphql
```
。亚太：
```
ap1.tray.io/graphql
```
。白标OAuth重定向使用
```
{org}.integration-authentication.com/oauth2/token
```
。使用错误区域URL会返回空结果且无明显错误提示。
Tray.io → Tray.ai品牌重塑。产品于2024年重塑为Tray.ai，并大力转向AI/Merlin方向。
```
tray.io
```
现在会301重定向至
```
tray.ai
```
，但API接口和开发者文档仍使用
```
tray.io
```
域名。文档链接中两者均可使用。

Related skills

Examples

示例

Example 1: Tray bill climbing and we can't see where the tasks are going

示例1：Tray账单攀升，无法追踪任务消耗去向

User says: "Our Tray bill went from $40K to $65K in 9 months — how do we figure out what's consuming tasks?" Skill does: Reads platform guide for pricing section. Explains task-based billing — every workflow step counts, so high-volume workflows with many branches/steps are usually the culprits. Recommends: (1) review the workflow task consumption view in the Tray dashboard, (2) audit the top 10 highest-volume workflows for redundant or always-on steps, (3) add branching to skip unnecessary actions, (4) batch-process where the source API supports it, (5) renegotiate at contract renewal with usage data in hand. Notes that Tray doesn't hard-stop workflows at plan limits, so overages compound. Result: User has a concrete optimization plan and a starting audit list.

用户提问：“我们的Tray账单在9个月内从4万美元涨到了6.5万美元——如何找出任务消耗的来源？” 技能处理：阅读平台指南中的定价部分。解释基于任务的计费方式——每个工作流步骤都算入任务量，因此高流量、包含多个分支/步骤的工作流通常是罪魁祸首。建议：(1) 在Tray仪表板中查看工作流任务消耗视图；(2) 审核前10个高流量工作流，查找冗余或持续运行的步骤；(3) 添加分支逻辑跳过不必要操作；(4) 在源API支持的情况下使用批处理；(5) 续约时手持使用数据重新协商。注意Tray不会在达到计划限制时强制停止工作流，因此超额费用会不断累积。结果：用户获得了具体的优化计划和初始审核清单。

Example 2: Embedding Tray Solutions in a B2B SaaS product

示例2：在B2B SaaS产品中嵌入Tray解决方案

User says: "We're a SaaS company and want to embed Tray so our customers can connect their own tools. How does that work?" Skill does: Reads platform guide for Tray Embedded section and API reference for mutation details. Explains: (1) build a Solution in Tray (reusable workflow template), (2) use the Configuration Wizard to let end users authenticate and configure, (3) on your backend, call

createSolutionInstance

mutation with a Master Token to create per-customer copies, (4) pass

configValues

and

authValues

to customize each instance, (5) use

createUserToken

to generate per-user tokens for subsequent operations. Flags CORS constraint (API is backend-only), and points to the official sample app (

github.com/trayio/embedded-edition-sample-app

) for reference architecture. Result: User understands the embedded integration model, token types, and reference implementation.

用户提问：“我们是一家SaaS公司，希望嵌入Tray以便客户连接他们自己的工具。这该如何实现？” 技能处理：阅读平台指南中的Tray Embedded部分和API参考中的变更操作细节。解释：(1) 在Tray中构建解决方案（可复用的工作流模板）；(2) 使用配置向导让终端用户进行身份验证和配置；(3) 在您的服务端调用

createSolutionInstance

变更操作（使用主令牌）创建每个客户的副本；(4) 传递

configValues

和

authValues

自定义每个实例；(5) 使用

createUserToken

生成每个用户的令牌用于后续操作。标记CORS限制（API仅支持服务端），并指向官方示例应用（

github.com/trayio/embedded-edition-sample-app

）获取参考架构。结果：用户理解了嵌入式集成模型、令牌类型和参考实现。

Example 3: Evaluating Tray vs Workato for a technical team

示例3：技术团队评估Tray vs Workato

User says: "We're a 6-person platform engineering team integrating 30 SaaS apps. Tray or Workato?" Skill does: Reads platform guide for competitor comparison. For a technical team integrating many apps: Tray fits better for teams comfortable with API-first, JavaScript-adjacent workflows and custom connector development via the CDK. Workato fits better for teams that want faster time-to-value with business-user-friendly recipes and broader connector coverage (1,200+ vs 700+). Pricing is similar enterprise range. Notes: Tray docs are thinner — budget more ramp time. If you plan to embed in a product, Tray Embedded is mature (launched 2020); Workato also has Embedded iPaaS with the Embed Partner Program. Result: User understands trade-offs and can pick based on team preference and roadmap.

用户提问：“我们是一个6人的平台工程团队，需要集成30个SaaS应用。选Tray还是Workato？” 技能处理：阅读平台指南中的竞品对比部分。对于需要集成多个应用的技术团队：Tray更适合熟悉API优先、类JavaScript工作流以及通过CDK构建自定义连接器的团队。Workato更适合希望快速实现价值、偏好面向业务用户的配方以及需要更广泛连接器覆盖（1200+ vs 700+）的团队。企业级定价范围相似。注意：Tray文档较单薄——需预留更多上手时间。如果计划嵌入产品，Tray Embedded已成熟（2020年推出）；Workato也有嵌入式iPaaS及Embed合作伙伴计划。结果：用户了解了权衡点，可根据团队偏好和路线图做出选择。

Troubleshooting

故障排查

Workflow silently fails — no error shown, no output

工作流静默失败——无错误提示，无输出

Symptom: A workflow step completes without an error but downstream steps receive empty data. Cause: Tray's GraphQL API returns HTTP 200 with an

errors

field when the server encounters a problem. Connection authentication may have expired without flagging, or the step's input mapping references a null/missing field. Solution: Open the workflow Debug panel and inspect input/output at each step. Check Connections → verify the connection for the step shows "Authenticated" (not expired). Re-authenticate if needed. For API-level debugging, inspect the full GraphQL response — look for

errors

array even on HTTP 200 responses.

症状：工作流步骤完成但无错误，但下游步骤收到空数据。原因：当服务器遇到问题时，Tray的GraphQL API会返回HTTP 200并包含

errors

字段。连接身份验证可能已过期但未标记，或步骤的输入映射引用了空/缺失字段。 解决方案：打开工作流调试面板，检查每个步骤的输入/输出。进入“连接”页面——验证该步骤的连接显示“已验证”（未过期）。如有需要重新验证。对于API级调试，检查完整的GraphQL响应——即使HTTP状态为200，也要查找

errors

数组。

Getting 429 or rate-limit errors at scale

大规模运行时遇到429或速率限制错误

Symptom: Workflow actions fail intermittently when processing high volumes. Cause: Tray enforces 30 req/sec and 1800 req/min across Embedded/Connectivity APIs (except Call Connector). Bursts up to 50/sec are tolerated briefly. Hitting these limits returns rate-limit responses (specific HTTP code not published). Solution: Implement exponential backoff on rate-limit errors. For high-volume Call Connector usage, remember concurrency cap is 1000 active requests — request a CSM increase if needed. Reduce trigger frequency or batch source events. For Event delivery (Trigger API), Tray auto-implements exponential backoff when downstream endpoints rate-limit.

症状：处理高流量时，工作流操作间歇性失败。原因：Tray对嵌入式/连接API（调用连接器除外）强制执行30请求/秒和1800请求/分钟的限制。短暂允许最高50请求/秒的突发流量。达到这些限制会返回速率限制响应（具体HTTP代码未公布）。 解决方案：针对速率限制错误实现指数退避机制。对于高流量的调用连接器使用，记住并发上限为1000个活跃请求——如有需要可请求客户成功经理（CSM）提高上限。降低触发器频率或批量处理源事件。对于事件交付（触发器API），当下游端点限制速率时，Tray会自动实现指数退避。

Solution Instance not appearing for a specific end user

特定终端用户看不到解决方案实例

Symptom: You created a Solution Instance via the Embedded API but the end user doesn't see it in their Configuration Wizard. Cause: Using the wrong token scope, or querying from the wrong regional endpoint.

Get Solution Instances

requires a User Token scoped to that specific end user. Master Token won't return a user's instances. Solution: Generate a User Token via

createUserToken

mutation for that specific user_id, then query

Get Solution Instances

with that token. Confirm the regional base URL matches your org's region (US:

tray.io

, EU:

eu1.tray.io

, APAC:

ap1.tray.io

). Whitelabel deployments use

{org}.integration-authentication.com

for OAuth redirects — verify the end user's auth flow hits the correct redirect URL.

症状：您通过嵌入式API创建了解决方案实例，但终端用户在配置向导中看不到它。原因：使用了错误的令牌作用域，或从错误的区域端点查询。

Get Solution Instances

需要作用域为该特定终端用户的用户令牌。主令牌不会返回用户的实例。 解决方案：通过

createUserToken

变更操作为该特定用户ID生成用户令牌，然后使用该令牌查询

Get Solution Instances

。确认区域基础URL与您组织的区域匹配（美国：

tray.io

，欧盟：

eu1.tray.io

，亚太：

ap1.tray.io

）。白标部署使用

{org}.integration-authentication.com

作为OAuth重定向地址——验证终端用户的身份验证流程是否访问了正确的重定向URL。