sales-workato

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Workato Platform Help

Workato平台帮助

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) Recipe building — connectors, triggers, actions, data mapping
- B) API Management — build, publish, manage, MCP Gateway
- C) Agent Studio — Genies, skills, knowledge bases, MCP servers
- D) Data Tables — structured storage, queries, record management
- E) Event Streams — real-time pub/sub messaging
- F) Embedded iPaaS — embedding integrations in your SaaS product
- G) B2B/EDI — trading partner data exchange
- H) Deployment — environments, RLCM, CI/CD, testing
- I) Monitoring / troubleshooting — job errors, debug tracing, performance
- J) Pricing / licensing — task consumption, editions, cost optimization
- K) Something else — describe it
What edition are you on?
- A) Standard
- B) Business
- C) Enterprise
- D) Workato One
- E) Not sure / evaluating
What's your role?
- A) Integration builder (creates recipes)
- B) Architect (designs integration strategy)
- C) Admin (manages workspace, users, governance)
- D) Business user (simple automations)
- E) Evaluating Workato

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) Recipe构建——连接器、触发器、操作、数据映射
- B) API管理——构建、发布、管理、MCP网关
- C) Agent Studio——Genies、技能、知识库、MCP服务器
- D) 数据表——结构化存储、查询、记录管理
- E) 事件流——实时发布/订阅消息
- F) 嵌入式iPaaS——在SaaS产品中嵌入集成功能
- G) B2B/EDI——贸易伙伴数据交换
- H) 部署——环境、RLCM、CI/CD、测试
- I) 监控/故障排除——任务错误、调试追踪、性能
- J) 定价/许可——任务消耗、版本、成本优化
- K) 其他——请描述具体需求
您使用的是哪个版本？
- A) Standard（标准版）
- B) Business（商业版）
- C) Enterprise（企业版）
- D) Workato One
- E) 不确定/正在评估
您的角色是什么？
- A) 集成构建者（创建Recipe）
- B) 架构师（设计集成策略）
- C) 管理员（管理工作区、用户、治理）
- D) 业务用户（简单自动化）
- E) 正在评估Workato

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

Step 2 — Route or answer directly

步骤2 — 路由或直接解答

Problem domain	Route to
Connecting Workato 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}`
MuleSoft-specific questions	`/sales-mulesoft {question}`
Boomi-specific questions	`/sales-boomi {question}`
SnapLogic-specific questions	`/sales-snaplogic {question}`
CRM data quality / deduplication	`/sales-data-hygiene {question}`
Recipe design and optimization	Answer directly — read platform guide
API management and MCP Gateway	Answer directly — read platform guide
Agent Studio / Genies	Answer directly — read platform guide
Pricing and cost optimization	Answer directly — read platform guide

When routing, provide the exact command.

问题领域	路由至
Workato与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}`
MuleSoft专属问题	`/sales-mulesoft {question}`
Boomi专属问题	`/sales-boomi {question}`
SnapLogic专属问题	`/sales-snaplogic {question}`
CRM数据质量/去重	`/sales-data-hygiene {question}`
Recipe设计与优化	直接解答——阅读平台指南
API管理与MCP网关	直接解答——阅读平台指南
Agent Studio / Genies	直接解答——阅读平台指南
定价与成本优化	直接解答——阅读平台指南

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

Step 3 — Workato platform reference

步骤3 — Workato平台参考

Read
references/platform-guide.md
for the full platform reference — modules, pricing, connectors, recipes, API management, Agent Studio, Event Streams.

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

If the question involves the Workato Developer API, also read
references/workato-api-reference.md
for endpoints, authentication, and resource details.

**阅读

references/platform-guide.md

**获取完整平台参考——模块、定价、连接器、Recipe、API管理、Agent Studio、事件流。

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

如果问题涉及Workato Developer API，还需**阅读

references/workato-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 Workato's integration library first for pre-built connectors (1,200+ available). If no connector exists, use the HTTP connector for any REST API, or build a custom connector with the Connector SDK (Ruby-based).

Cost optimization shortcut: Audit recipe task consumption — each action inside a recipe counts as a task. Consolidate multi-step recipes where possible. Use conditional logic to skip unnecessary actions. Monitor via the Consumption Dashboard. Negotiate multi-year for volume discounts.

Debugging shortcut: Enable Job Debug Tracing for detailed HTTP request/response logs per action. Use Network Tracing for connector-level debugging. Add error-handling steps (Monitor → On Error) with custom notifications. Test incrementally — use the step-skip feature to isolate failures.

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

references/learnings.md

, append it there.

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

连接器选择捷径：先查看Workato集成库中的预构建连接器（超过1200个）。如果没有对应连接器，使用HTTP连接器对接任意REST API，或通过Connector SDK（基于Ruby）构建自定义连接器。

成本优化捷径：审计Recipe任务消耗——Recipe内的每个操作都计为一个任务。尽可能合并多步骤Recipe。使用条件逻辑跳过不必要的操作。通过消耗仪表板监控。协商多年期协议获取批量折扣。

调试捷径：启用任务调试追踪，获取每个操作的详细HTTP请求/响应日志。使用网络追踪进行连接器级调试。添加错误处理步骤（监控→出错时）并设置自定义通知。逐步测试——使用跳步功能隔离故障。

如果发现

references/learnings.md

未涵盖的陷阱、变通方案或技巧，请补充至该文件。

Gotchas

注意事项

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

Task-based billing spirals fast. Each action inside a recipe = 1 task. A 10-step recipe processing 1,000 records/day = 10,000 tasks/day. Teams report costs doubling within 6-12 months of initial deployment. Model your task consumption before signing and set up consumption alerts.
Data size limits are real. CSV parsing caps at 50K records. Lookup Tables cap at 100K rows. For larger datasets, use Data Tables or external storage. These limits are not obvious until you hit them.
Not built for ETL. Workato excels at business process automation but struggles with complex joins, data masking, deduplication, or multi-step data transformations. Use a dedicated ETL tool (Fivetran, dbt, Airbyte) for data pipeline work.
Recipe errors can be vague. Default error messages often lack specificity. Enable Job Debug Tracing (per-job HTTP logs) and add Monitor → On Error steps with detailed error notifications. Test recipes incrementally using step-skip.
No Git-style versioning. Workato uses recipe versioning (snapshots) but lacks branching, merging, or pull requests. For teams used to Git workflows, this feels limiting. Use RLCM (Recipe Lifecycle Management) with export manifests for promotion between environments.
Connector API limits are inherited. Workato respects the target system's API rate limits but doesn't always surface these clearly. A recipe that works at low volume may hit 429 errors at scale. Check the target system's rate limit docs before scaling.
Consumption overages aren't blocked by default. Workato tracks consumption proactively but doesn't hard-stop recipes that exceed your plan. Set up consumption alerts and monitor the dashboard weekly during ramp-up.

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

基于任务的计费成本增长极快。Recipe内的每个操作=1个任务。一个10步骤的Recipe每日处理1000条记录=每日10000个任务。团队反馈初始部署后6-12个月内成本翻倍。签约前务必预估任务消耗并设置消耗警报。
数据大小限制真实存在。CSV解析上限为50000条记录。查找表上限为100000行。对于更大的数据集，使用数据表或外部存储。这些限制在触发前并不明显。
并非为ETL打造。Workato擅长业务流程自动化，但在复杂关联、数据掩码、去重或多步骤数据转换方面表现不佳。针对数据管道工作，请使用专用ETL工具（Fivetran、dbt、Airbyte）。
Recipe错误可能模糊不清。默认错误消息通常缺乏具体信息。启用任务调试追踪（单任务HTTP日志）并添加监控→出错时步骤，设置详细错误通知。使用跳步功能逐步测试Recipe。
无Git式版本控制。Workato支持Recipe版本控制（快照），但缺少分支、合并或拉取请求功能。对于习惯Git工作流的团队而言，这会受限。使用RLCM（Recipe生命周期管理）配合导出清单在环境间推广。
连接器API限制继承自目标系统。Workato遵循目标系统的API速率限制，但并不总是清晰展示。低流量下正常运行的Recipe在扩容时可能触发429错误。扩容前请查看目标系统的速率限制文档。
默认不阻止消耗超额。Workato会主动追踪消耗，但不会强制停止超出计划的Recipe。设置消耗警报，并在上线初期每周监控仪表板。

Related skills

Examples

示例

Example 1: Recipe costs spiraling out of control

示例1：Recipe成本失控增长

User says: "Our Workato bill went from $15K to $30K in 6 months and we can't figure out why." Skill does: Reads platform guide for pricing section. Explains task-based billing — each action = 1 task, so a 10-step recipe processing 1,000 triggers/day = 10,000 tasks/day = 300K tasks/month. Recommends: (1) open Consumption Dashboard → sort by task usage to find top consumers, (2) audit high-volume recipes for unnecessary steps, (3) add conditions to skip actions that don't need to run every time, (4) consider batch processing to reduce trigger frequency. Notes that consumption alerts should be set at 80% of plan. Result: User identifies the cost drivers and has a concrete optimization plan.

用户提问："我们的Workato账单在6个月内从1.5万美元涨到3万美元，找不到原因。" 技能处理：阅读平台指南中的定价章节。解释基于任务的计费规则——每个操作=1个任务，因此一个10步骤的Recipe每日触发1000次=每日10000个任务=每月30万个任务。建议：(1) 打开消耗仪表板→按任务用量排序找出高消耗项，(2) 审计高流量Recipe中的不必要步骤，(3) 添加条件逻辑跳过无需每次运行的操作，(4) 考虑批量处理以降低触发频率。注意应将消耗警报设置为计划用量的80%。结果：用户识别出成本驱动因素并获得具体优化方案。

Example 2: Evaluating Workato vs MuleSoft vs Boomi

示例2：评估Workato vs MuleSoft vs Boomi

User says: "We need an iPaaS for 25 SaaS apps, small IT team of 4, mostly cloud — Workato, MuleSoft, or Boomi?" Skill does: Reads platform guide for comparison section. For a small team with 25 cloud apps: Workato is the best fit — lowest learning curve (visual recipe builder), fastest time-to-value, 1,200+ pre-built connectors, and business users can build simple automations. MuleSoft is overkill (needs certified developers, $50K+/yr). Boomi is mid-ground but per-connection pricing adds up fast with 25 apps. Recommends Workato Standard/Business tier. Notes: model task consumption carefully to avoid bill shock. Result: User understands the trade-offs and has a recommendation for their scale.

用户提问："我们需要一款iPaaS对接25个SaaS应用，IT团队仅4人，以云环境为主——选Workato、MuleSoft还是Boomi？" 技能处理：阅读平台指南中的对比章节。对于对接25个云应用的小型团队：Workato是最佳选择——学习曲线最低（可视化Recipe构建器）、价值交付最快、1200+预构建连接器，且业务用户可构建简单自动化。MuleSoft过于冗余（需要认证开发人员，年费5万美元以上）。Boomi处于中间价位，但按连接计费的模式在25个应用场景下成本增长迅速。推荐Workato Standard/Business版本。注意：务必仔细预估任务消耗，避免账单意外增长。结果：用户了解各产品权衡点，并获得适配自身规模的推荐。

Example 3: Recipe failing with unclear error on high volume

示例3：高流量下Recipe失败且错误模糊

User says: "My recipe that syncs Salesforce opportunities to NetSuite keeps failing with 'Action failed' but the error details are empty." Skill does: Explains debugging approach: (1) Enable Job Debug Tracing for the recipe — this captures full HTTP request/response for each action, (2) check if the error is a rate limit from NetSuite (429 or SuiteTalk concurrency limit), (3) add a Monitor → On Error step that captures

error_message

and

error_type

and sends to Slack, (4) if rate-limited, add a Repeat step with delay between batches. Notes that NetSuite has a 25-concurrent-request limit on SuiteTalk API. Result: User has debugging steps and a likely root cause.

用户提问："我那台将Salesforce商机同步到NetSuite的Recipe一直显示'操作失败'，但无错误详情。" 技能处理：解释调试方法：(1) 为Recipe启用任务调试追踪——捕获每个操作的完整HTTP请求/响应，(2) 检查是否是NetSuite的速率限制错误（429或SuiteTalk并发限制），(3) 添加监控→出错时步骤，捕获

error_message

和

error_type

并发送至Slack，(4) 如果是速率限制问题，添加带延迟的重复步骤分批处理。注意NetSuite的SuiteTalk API有25并发请求限制。结果：用户获得调试步骤及可能的根本原因。

Troubleshooting

故障排除

Recipe suddenly stops triggering

Recipe突然停止触发

Symptom: Recipe was working fine but stops processing new events — no errors, no jobs. Cause: Trigger polling may have hit an API limit on the source system, or the trigger's "since" cursor is stuck. Connection tokens may have expired. Solution: Check the connection status (Connections → verify it shows "Connected"). Re-test the trigger manually. Check if the source app's API changed authentication requirements. If the trigger cursor is stuck, reset it via Recipe → Reset Trigger (warning: may reprocess old events). Check Workato's status page for platform-wide issues.

症状：Recipe之前运行正常，但突然停止处理新事件——无错误、无任务记录。原因：触发器轮询可能触发了源系统的API限制，或触发器的"since"游标卡住。连接令牌可能已过期。 解决方案：检查连接状态（连接→确认显示"已连接"）。手动重新测试触发器。检查源应用的API是否更改了认证要求。如果触发器游标卡住，通过Recipe→重置触发器重置（警告：可能会重新处理旧事件）。查看Workato状态页面确认是否存在平台级问题。

Job debug tracing shows 429 errors

任务调试追踪显示429错误

Symptom: Actions fail intermittently, debug tracing shows HTTP 429 (Too Many Requests) responses. Cause: Target system's API rate limit exceeded. Workato sends requests as fast as the recipe runs — it doesn't auto-throttle to match the target system's limits. Solution: Add a Repeat step with configurable delay between actions. Reduce batch size. Check the target system's rate limit docs and set your recipe frequency accordingly. For Salesforce, check the 24-hour API request limit (varies by edition). For NetSuite, check SuiteTalk concurrency limits.

症状：操作间歇性失败，调试追踪显示HTTP 429（请求过多）响应。原因：超出目标系统的API速率限制。Workato会按Recipe运行速度发送请求——不会自动节流以匹配目标系统的限制。 解决方案：添加带可配置延迟的重复步骤。减小批量大小。查看目标系统的速率限制文档并相应设置Recipe频率。对于Salesforce，查看24小时API请求限制（因版本而异）。对于NetSuite，查看SuiteTalk并发限制。

Recipe works in test but fails in production

Recipe在测试环境正常但生产环境失败

Symptom: Recipe runs fine with test data but fails on real production data. Cause: Production data has edge cases not present in test — nulls, special characters, unexpected formats, larger payloads exceeding field limits. Solution: Add data validation steps before key actions. Use error handling (Monitor → On Error) to catch and log specific failures. Check for null values with conditional logic before mapping. Verify field length limits on the destination system match your production data.

症状：Recipe在测试数据下运行正常，但在真实生产数据下失败。原因：生产数据存在测试数据中没有的边缘情况——空值、特殊字符、意外格式、有效载荷超过字段限制。 解决方案：在关键操作前添加数据验证步骤。使用错误处理（监控→出错时）捕获并记录特定故障。在映射前使用条件逻辑检查空值。验证目标系统的字段长度限制是否匹配生产数据。