Back to Details

sales-mulesoft

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MuleSoft Platform Help

MuleSoft平台支持

Step 1 — Gather context

步骤1 — 收集上下文

If 
references/learnings.md
exists, read it first for accumulated platform knowledge.
Ask the user:
  1. What do you need help with?
    • A) API design — RAML/OAS specs, Design Center, API-first approach
    • B) Integration development — Anypoint Studio, Code Builder, connectors, DataWeave
    • C) Deployment — CloudHub, CloudHub 2.0, Runtime Fabric, on-prem, hybrid
    • D) API management — API Manager, policies, SLA tiers, Flex Gateway, rate limiting
    • E) Composer — no-code integrations, Salesforce-native automation
    • F) RPA / IDP — robotic process automation, document processing
    • G) AI — Einstein for MuleSoft, Dev Agent, Agent Fabric, MCP support
    • H) Exchange — publishing assets, discovering connectors, templates
    • I) Monitoring / troubleshooting — logs, alerts, performance, errors
    • J) Pricing / licensing — vCores, editions, Gold/Platinum/Titanium, cost optimization
    • K) Something else — describe it
  2. What's your deployment model?
    • A) CloudHub (Salesforce-hosted)
    • B) CloudHub 2.0 (shared responsibility)
    • C) Runtime Fabric (self-managed Kubernetes)
    • D) On-premises (standalone Mule runtime)
    • E) Hybrid (mix of above)
    • F) Not sure / evaluating
  3. What's your role?
    • A) MuleSoft developer (builds integrations)
    • B) Architect (designs API strategy)
    • C) Admin (manages platform, users, environments)
    • D) Business user (Composer / no-code)
    • E) Evaluating MuleSoft
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
文件存在，请先阅读该文件获取已积累的平台知识。
向用户询问以下问题：
  1. 您需要哪方面的帮助？
    • A) API设计——RAML/OAS规范、Design Center、API优先方法
    • B) 集成开发——Anypoint Studio、Code Builder、连接器、DataWeave
    • C) 部署——CloudHub、CloudHub 2.0、Runtime Fabric、本地部署、混合部署
    • D) API管理——API Manager、策略、SLA层级、Flex Gateway、速率限制
    • E) Composer——无代码集成、Salesforce原生自动化
    • F) RPA/IDP——机器人流程自动化、文档处理
    • G) AI——MuleSoft Einstein、Dev Agent、Agent Fabric、MCP支持
    • H) Exchange——资产发布、连接器发现、模板
    • I) 监控/故障排查——日志、告警、性能、错误
    • J) 定价/授权——vCore、版本、Gold/Platinum/Titanium、成本优化
    • K) 其他——请描述具体内容
  2. 您的部署模式是什么？
    • A) CloudHub（Salesforce托管）
    • B) CloudHub 2.0（共享责任模式）
    • C) Runtime Fabric（自管理Kubernetes）
    • D) 本地部署（独立Mule运行时）
    • E) 混合部署（以上模式组合）
    • F) 不确定/评估中
  3. 您的角色是什么？
    • A) MuleSoft开发者（构建集成）
    • B) 架构师（设计API策略）
    • C) 管理员（管理平台、用户、环境）
    • D) 业务用户（Composer/无代码工具使用者）
    • E) 正在评估MuleSoft
跳过规则：如果用户的提问已提供足够上下文，直接跳至步骤2。先基于合理假设（需明确说明）给出最优解答，再提出1-2个关键澄清问题。

Step 2 — Route or answer directly

步骤2 — 路由或直接解答

Problem domainRoute to
Connecting MuleSoft 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}
SnapLogic-specific questions
/sales-snaplogic {question}
Workato-specific questions
/sales-workato {question}
Boomi-specific questions
/sales-boomi {question}
API design best practices (REST, versioning)Answer directly — this is core MuleSoft
DataWeave transformation helpAnswer directly — read platform guide
CloudHub deployment or performanceAnswer directly — read platform guide
vCore optimization or pricingAnswer directly — read platform guide
When routing, provide the exact command.
问题领域路由至
MuleSoft与Salesforce/HubSpot/CRM的连接
/sales-integration {question}
CRM对比——Salesforce vs HubSpot vs 其他
/sales-crm-selection {question}
Salesforce专属配置（Flows、Apex、SOQL）
/sales-salesforce {question}
简单无代码Zapier/Make自动化
/sales-integration {question}
SnapLogic相关问题
/sales-snaplogic {question}
Workato相关问题
/sales-workato {question}
Boomi相关问题
/sales-boomi {question}
API设计最佳实践（REST、版本控制）直接解答——这是MuleSoft核心内容
DataWeave转换帮助直接解答——查阅平台指南
CloudHub部署或性能问题直接解答——查阅平台指南
vCore优化或定价问题直接解答——查阅平台指南
路由时，请提供准确命令。

Step 3 — MuleSoft platform reference

步骤3 — MuleSoft平台参考

Read 
references/platform-guide.md
 for the full platform reference — modules, pricing, integrations, data model, deployment options, DataWeave.
Answer the user's question using only the relevant section. Don't dump the full reference.
If the question involves the Anypoint Platform APIs, also read 
references/mulesoft-api-reference.md
 for endpoints, authentication, and rate limits.
**阅读
references/platform-guide.md
**获取完整平台参考——模块、定价、集成、数据模型、部署选项、DataWeave等内容。
仅使用相关章节解答用户问题，不要输出完整参考内容。
若问题涉及Anypoint Platform API，还需**阅读
references/mulesoft-api-reference.md
**获取端点、认证和速率限制信息。

Step 4 — Actionable guidance

步骤4 — 可落地指导

You no longer need the platform guide — focus on the user's specific situation.
API-led connectivity shortcut: System APIs (connect to backend systems) → Process APIs (orchestrate business logic) → Experience APIs (serve channels/apps). Layer this architecture to maximize reuse.
Deployment decision shortcut: CloudHub for fastest start, lowest ops burden. Runtime Fabric for Kubernetes shops needing control. On-prem only if regulatory/compliance requires it. CloudHub 2.0 is the new default — evaluate before choosing legacy CloudHub.
Cost optimization shortcut: Right-size vCores (start with 0.1 for dev, 0.2 for staging, 1.0+ for prod). Use shared workers for low-traffic APIs. Consolidate apps where possible to reduce vCore count. Monitor CPU/memory to avoid over-provisioning.
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
无需再依赖平台指南——聚焦用户具体场景。
API驱动连接捷径：系统API（连接后端系统）→ 流程API（编排业务逻辑）→ 体验API（服务渠道/应用）。通过分层架构最大化复用性。
部署决策捷径：CloudHub上手最快、运维负担最低；Runtime Fabric适合需要控制权的Kubernetes团队；仅在合规要求下选择本地部署；CloudHub 2.0是新默认选项——选择旧版CloudHub前请先评估。
成本优化捷径：合理调整vCore规格（开发环境从0.1开始，预发布环境用0.2，生产环境用1.0+）；低流量API使用共享工作器；尽可能合并应用以减少vCore数量；监控CPU/内存避免过度配置。
若发现
references/learnings.md
未覆盖的陷阱、解决方案或技巧，请补充至该文件中。

Gotchas

注意事项

Best-effort from research — review these, especially pricing details and feature availability which change with Salesforce releases.
  • vCore pricing spirals with scale. Each integration flow needs vCores. Enterprise contracts commonly exceed $50K/year before headcount. Model your vCore needs before signing — add 30% buffer for non-production environments.
  • DataWeave has a steep learning curve. It's a proprietary functional language with no equivalent outside MuleSoft. Certified MuleSoft developers command $120-180K salaries. Budget for training or hire experienced developers.
  • Implementation takes 6-18 months. Typical enterprise MuleSoft deployment is a multi-quarter project. CI/CD pipeline integration requires custom DevOps scripting not included in the platform.
  • Anypoint Studio IDE is buggy. Crashes, memory leaks, port binding issues, and misleading error messages are common complaints. Save frequently, use version control, and consider Code Builder as an alternative.
  • CloudHub has CPU credit limits. Applications that run fine locally may struggle after CloudHub deployment. Monitor CPU usage closely — exceeding credits causes throttling.
  • Premium connectors cost extra. SAP, Oracle, Workday, Siebel connectors carry separate annual fees ($5K-50K+ each). Verify connector licensing before planning integrations.
  • MuleSoft Community migrated to Trailblazer. As of May 2025, help.mulesoft.com forums moved to Salesforce Trailblazer Community. Old bookmarks may not work.
基于研究的最佳实践——请重点关注这些内容，尤其是随Salesforce版本更新的定价细节和功能可用性。
  • vCore成本随规模激增。每个集成流都需要vCore。企业合同通常在计入人力成本前就超过每年5万美元。签署合同前先预估vCore需求——为非生产环境预留30%的缓冲。
  • DataWeave学习曲线陡峭。它是MuleSoft专属的函数式语言，无同类替代工具。认证MuleSoft开发者年薪可达12-18万美元。需为培训预算或聘请资深开发者做好规划。
  • 实施周期为6-18个月。典型企业级MuleSoft部署是跨季度项目。CI/CD流水线集成需要平台未提供的自定义DevOps脚本。
  • Anypoint Studio IDE存在bug。崩溃、内存泄漏、端口绑定问题和误导性错误是常见投诉。请频繁保存、使用版本控制，并考虑改用Code Builder作为替代方案。
  • CloudHub有CPU积分限制。本地运行正常的应用部署到CloudHub后可能出现性能问题。请密切监控CPU使用率——超出积分会导致限流。
  • 高级连接器需额外付费。SAP、Oracle、Workday、Siebel连接器需单独支付年费（每个5000-50000美元以上）。规划集成前请确认连接器授权情况。
  • MuleSoft社区已迁移至Trailblazer。截至2025年5月，help.mulesoft.com论坛已迁移至Salesforce Trailblazer社区。旧书签可能失效。

Related skills

相关技能

  • /sales-salesforce
    — Salesforce platform help — MuleSoft's parent company, CRM integration target
  • /sales-workato
    — Workato platform help — enterprise iPaaS, 1200+ connectors, recipe automation, MCP Gateway (direct competitor)
  • /sales-boomi
    — Boomi platform help — enterprise iPaaS, 1000+ connectors, API Management, Data Hub MDM (direct competitor)
  • /sales-celigo
    — Celigo platform help — mid-market iPaaS, 1000+ connectors, AI error management, NetSuite depth (direct competitor)
  • /sales-snaplogic
    — SnapLogic platform help — enterprise iPaaS, 1000+ Snaps, AgentCreator AI agents, API Management 3.0 (direct competitor)
  • /sales-jitterbit
    — Jitterbit platform help — Harmony iPaaS, 400+ connectors, API Manager, App Builder (direct competitor)
  • /sales-tray
    — Tray.ai platform help — enterprise iPaaS, 700+ connectors, Merlin Agent Builder, Tray Embedded (direct competitor)
  • /sales-informatica
    — Informatica IDMC platform help — enterprise iPaaS + data management, CDI/CAI, MDM, Data Catalog (direct competitor, data-management-first)
  • /sales-integration
    — Connecting sales tools — webhooks, Zapier/Make, native integrations, CRM sync
  • /sales-hubspot
    — HubSpot platform help — common MuleSoft integration target
  • /sales-crm-selection
    — CRM comparison and selection — choosing the right CRM to integrate with
  • /sales-data-hygiene
    — CRM data quality — deduplication, record matching, enrichment automation
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install: 
    npx skills add sales-skills/sales --skill sales-do
  • /sales-salesforce
    ——Salesforce平台支持——MuleSoft母公司，CRM集成目标平台
  • /sales-workato
    ——Workato平台支持——企业级iPaaS，1200+连接器，配方自动化，MCP Gateway（直接竞品）
  • /sales-boomi
    ——Boomi平台支持——企业级iPaaS，1000+连接器，API管理，Data Hub MDM（直接竞品）
  • /sales-celigo
    ——Celigo平台支持——中端市场iPaaS，1000+连接器，AI错误管理，NetSuite深度集成（直接竞品）
  • /sales-snaplogic
    ——SnapLogic平台支持——企业级iPaaS，1000+组件，AgentCreator AI代理，API Management 3.0（直接竞品）
  • /sales-jitterbit
    ——Jitterbit平台支持——Harmony iPaaS，400+连接器，API Manager，App Builder（直接竞品）
  • /sales-tray
    ——Tray.ai平台支持——企业级iPaaS，700+连接器，Merlin Agent Builder，Tray Embedded（直接竞品）
  • /sales-informatica
    ——Informatica IDMC平台支持——企业级iPaaS+数据管理，CDI/CAI，MDM，数据目录（直接竞品，以数据管理为核心）
  • /sales-integration
    ——销售工具连接——webhooks、Zapier/Make、原生集成、CRM同步
  • /sales-hubspot
    ——HubSpot平台支持——常见MuleSoft集成目标平台
  • /sales-crm-selection
    ——CRM对比与选型——选择适合集成的CRM
  • /sales-data-hygiene
    ——CRM数据质量——去重、记录匹配、 enrichment自动化
  • /sales-do
    ——不确定使用哪个技能？该路由可将任何销售目标匹配至合适技能。安装命令：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: DataWeave transformation not working

示例1：DataWeave转换失效

User says: "My DataWeave transformation keeps failing — I'm trying to map a nested JSON array from SAP to flat Salesforce records." Skill does: Reads platform guide for DataWeave section. Explains 
flatMap
and 
map
for nested-to-flat transformations. Provides a DataWeave snippet mapping nested SAP items to flat Salesforce Contact records. Notes common pitfalls: null handling with 
default
, type coercion with 
as String
, and the 
---
separator requirement. Result: User gets a working DataWeave transformation with error handling.
用户提问："我的DataWeave转换一直失败——我正尝试将SAP的嵌套JSON数组映射为扁平化的Salesforce记录。" 技能处理：查阅平台指南中DataWeave章节。解释用于嵌套转扁平化的
flatMap
和
map
函数。提供将SAP嵌套条目映射为扁平化Salesforce Contact记录的DataWeave代码片段。指出常见陷阱：使用
default
处理空值、使用
as String
进行类型转换、以及必须使用
---
分隔符。 结果：用户获得带错误处理的可用DataWeave转换方案。

Example 2: CloudHub deployment running out of resources

示例2：CloudHub部署资源耗尽

User says: "Our MuleSoft API deployed to CloudHub is timing out under load — we're on a 0.2 vCore worker." Skill does: Reads platform guide for deployment section. Explains vCore sizing: 0.2 is development-tier (500 MB heap). For production load, recommends minimum 1.0 vCore. Suggests monitoring via Runtime Manager dashboards. Flags that horizontal scaling (multiple workers) distributes load but requires stateless design. Notes CloudHub 2.0 offers better autoscaling. Result: User understands vCore sizing and scaling options.
用户提问："我们部署到CloudHub的MuleSoft API在负载下超时——我们使用的是0.2 vCore工作器。" 技能处理：查阅平台指南中部署章节。解释vCore规格：0.2属于开发层级（500MB堆内存）。生产负载下建议最低使用1.0 vCore。建议通过Runtime Manager仪表盘监控。指出水平扩展（多工作器）可分散负载，但需要无状态设计。说明CloudHub 2.0提供更优的自动扩缩容能力。 结果：用户理解vCore规格与扩缩容选项。

Example 3: Choosing between MuleSoft and simpler tools

示例3：选择MuleSoft还是更简单的工具

User says: "My boss wants us to use MuleSoft for everything but we're a 20-person startup with basic CRM integrations." Skill does: Explains that MuleSoft is enterprise-grade ($50K+/year, 6-18 month implementation). For a 20-person startup with basic integrations, recommends Zapier/Make first ($20-100/mo, same-day setup). Routes to 
/sales-integration
for no-code options. Notes MuleSoft makes sense when you have 50+ integrations, need API governance, or compliance requirements. Result: User understands when MuleSoft is (and isn't) the right tool.
用户提问："我的老板要求我们所有场景都用MuleSoft，但我们是20人的初创公司，只需要基础的CRM集成。" 技能处理：说明MuleSoft是企业级产品（每年5万美元以上，实施周期6-18个月）。对于20人的初创公司和基础集成需求，建议优先使用Zapier/Make（每月20-100美元，当日即可完成配置）。路由至
/sales-integration
获取无代码选项。指出当集成数量超过50个、需要API治理或合规要求时，MuleSoft才是合适选择。 结果：用户理解MuleSoft的适用（与不适用）场景。

Troubleshooting

故障排查

"Anypoint Studio keeps crashing or freezing"

"Anypoint Studio频繁崩溃或冻结"

Symptom: IDE becomes unresponsive, throws memory errors, or crashes during development. Cause: Anypoint Studio is Eclipse-based and resource-hungry. Common triggers: large projects, multiple open flows, insufficient heap memory, conflicting plugins. Solution: Increase heap size in 
AnypointStudio.ini
(set 
-Xmx
to 4096m or higher). Close unused projects in the workspace. Disable unused plugins. Consider switching to Anypoint Code Builder (VS Code-based, lighter weight). Save and commit frequently.
症状：IDE无响应、抛出内存错误或开发过程中崩溃。 原因：Anypoint Studio基于Eclipse开发，资源消耗大。常见触发因素：大型项目、多个打开的流、堆内存不足、插件冲突。 解决方案：修改
AnypointStudio.ini
中的堆内存大小（将
-Xmx
设置为4096m或更高）。关闭工作区中未使用的项目。禁用未使用的插件。考虑改用Anypoint Code Builder（基于VS Code，更轻量化）。频繁保存并提交代码。

"DataWeave type coercion errors"

"DataWeave类型转换错误"

Symptom: Transformation fails with "Cannot coerce" or unexpected null values in output. Cause: Input data has unexpected types or null values that DataWeave can't auto-coerce. Common with SAP/ERP sources that send numbers as strings or use empty strings for nulls. Solution: Use explicit type coercion (
as String
, 
as Number
). Add null guards with 
default
operator. Use 
skipNullOn="everywhere"
output directive. Test with sample payloads using DataWeave Playground before deploying.
症状：转换失败并提示"Cannot coerce"或输出中出现意外空值。 原因：输入数据存在DataWeave无法自动转换的意外类型或空值。常见于SAP/ERP数据源将数字作为字符串发送，或用空字符串表示空值的情况。 解决方案：使用显式类型转换（
as String
、
as Number
）。用
default
运算符添加空值防护。使用
skipNullOn="everywhere"
输出指令。部署前先用DataWeave Playground测试示例负载。

"vCore costs keep growing and I can't justify the budget"

"vCore成本持续增长，无法证明预算合理性"

Symptom: MuleSoft licensing bill increases every renewal cycle as integration count grows. Cause: Each deployed application consumes vCores. Non-production environments (dev, staging, QA) each need their own allocation. Premium connectors add per-connector fees on top. Solution: Right-size vCores per environment (0.1 for dev, 0.2 for staging). Consolidate related flows into single applications where possible. Use Composer for simple Salesforce-native integrations (included in some Salesforce licenses). Negotiate multi-year contracts for volume discounts. Document ROI per integration to justify costs.
症状：随着集成数量增加，MuleSoft授权费用在每次续约时都会上涨。 原因：每个部署的应用都会消耗vCore。非生产环境（开发、预发布、QA）各自需要独立分配资源。高级连接器还需额外支付每个连接器的费用。 解决方案：为每个环境合理调整vCore规格（开发用0.1，预发布用0.2）。尽可能将相关流合并到单个应用中。对于简单的Salesforce原生集成，使用Composer（部分Salesforce授权已包含该功能）。协商多年合同以获取批量折扣。记录每个集成的ROI以证明成本合理性。