Oil painting in blue: an integration architect draws boxes and arrows on a whiteboard
  1. Home
  2. Integrations
  3. MuleSoft consulting

Anypoint Platform done right.

MuleSoft consulting focused on API-led connectivity and integrations with Salesforce, SAP, and legacy systems: governance, high-performance DataWeave, and reusable architecture for operations that cannot fail.

Serious integration needs explicit standards. We design every API as a product, with an owner, a contract, a version, and a security policy, so it becomes a reusable asset, not a one-off patch.

Scenarios we've already delivered in production

Salesforce, SAP, Brazilian ERPs, and B2B partners connected through Anypoint Platform, with APIs reused from one project to the next.

Salesforce and SAPBidirectional integration between Sales or Service Cloud and SAP S/4HANA or ECC: accounts, contacts, orders, invoicing, and inventory.
Salesforce and Brazilian ERPsSalesforce connected to Protheus, Oracle EBS, Sankhya, or Sage, with dedicated connectors and DataWeave for tax mapping.
B2B EDIEDI integrations with retail chains and other partners in ANSI X12, EDIFACT, and IDoc, through the native EDI Module.
Advanced DataWeaveComplex transformations of JSON, XML, EDI, CSV, Avro, and Parquet, with reusable functions and shared libraries.
CloudHubAPIs and integrations on the MuleSoft managed cloud, with auto-scaling, high availability, and built-in monitoring.
Runtime FabricRuns on Kubernetes in your cloud (AWS, Azure, or GCP) or in your data center, for data sovereignty and local latency requirements.

Why CCX for this work

API-led as a discipline, not a diagram: contract, security, and cost handled from the design stage.

API as a product

Contract in OpenAPI 3 or RAML, design review before implementation, contract tests in CI/CD, and publication to Anypoint Exchange for reuse.

The right pattern for each case

Synchronous only when low latency is mandatory; asynchronous, with idempotency and retries, for everything that tolerates some delay.

Right-sized licensing

We size vCores, reduce payloads, use streaming and batching, and reuse APIs across projects to avoid over-provisioning.

An autonomous client team

Documentation, full handoff, and DataWeave training so the in-house team can keep evolving the integrations.

Three layers that maximize reuse

API-led connectivity separates responsibilities: each API is reused across multiple projects and channels, without duplicating logic.

  1. SAPS/4HANA or ECC
  2. SalesforceSales and Service Cloud
  3. Protheus and OracleERPs and legacy systems
  4. System APIsOne clean API per system
  5. Complete customerComposite Process API
  6. Unified shippingComposite Process API
  7. Experience APIsTailored payload
  8. API ManagerPolicies and versioning
  9. Mobile appMobile experience
  10. Web portalCustomers and teams
  11. B2B partnerThird-party integration

The three layers of API-led connectivity, with API Manager applying security and throttling policies. A single System API serves multiple processes and channels.

MuleSoft, SAP CPI, or another iPaaS: when to use each

The choice depends on the technical context, the licenses you already have, and complexity. We help you decide before you license.

OptionMakes sense whenWatch out
MuleSoft (Anypoint Platform)Advanced API management, the Salesforce ecosystem, and complex DataWeave transformations are central.vCore-based licensing and a steep learning curve. Sizing it right avoids over-provisioning.
SAP CPI (Integration Suite)SAP is at the core and the company already has SAP BTP licenses.Less suited to the Salesforce ecosystem; the license is also costly. See SAP and e-commerce integration.
Lighter iPaaSMid-market scenario, with simpler integrations and priority on license cost and a short learning curve.API management and complex transformations tend to be less robust.

Three patterns that define every integration

We choose the pattern by the case, not by habit. The result withstands partial failures, scales with volume, and is auditable at every step.

Request-reply, only when needed

Synchronous calls only where low latency is mandatory, with an explicit contract between the parties.

Pub-sub and events

Anypoint MQ, Kafka, AMQP, or webhook queues, with idempotency and retries for everything that tolerates some delay.

Orchestration or choreography

Orchestration, choreography, and scatter-gather chosen case by case, with MuleSoft's built-in primitives.

Layered security, governance in the pipeline

A mandatory minimum policy for every API, applied per environment, from the first deploy to operations.

  • Authentication with OAuth 2.0, mTLS, or JWT.
  • Authorization by claims, scopes, and roles.
  • Encryption in transit and at rest, masking of personal data, and an audit trail.
  • Ready-made policies per environment: rate limiting, IP allowlist, CORS, and client ID.
  • Governance gates in CI/CD that block non-compliant deploys.
  • Anypoint Monitoring with Datadog or Splunk alerting on violations after go-live.

Frequently asked questions

What is MuleSoft Anypoint Platform?

Anypoint Platform is the integration platform from MuleSoft, a company in the Salesforce ecosystem. It brings together tools to build, manage, publish, and monitor APIs and integrations in a unified hub, with prebuilt connectors for hundreds of systems.

What is API-led connectivity?

It is the MuleSoft methodology that organizes integrations into three layers: System APIs, which connect source systems; Process APIs, which orchestrate business rules; and Experience APIs, which deliver data tailored to each channel or consumer. It reduces coupling and increases reuse.

Is MuleSoft only for Salesforce?

No. Although it belongs to Salesforce, MuleSoft integrates any system: SAP, Oracle, Workday, Protheus, databases, queues, SaaS APIs, and legacy systems. Salesforce integration is one of the most common cases, but it isn't required.

MuleSoft, SAP CPI, or another iPaaS: which one to choose?

MuleSoft stands out in advanced API management, DataWeave, and the Salesforce ecosystem. CPI is ideal when SAP is at the core. Lighter iPaaS platforms may be enough for simpler mid-market scenarios. CCX helps you choose based on the technical context, current licenses, and complexity.

How much does a MuleSoft license cost?

MuleSoft uses a licensing model based on vCores, the contracted runtime capacity, and the price grows with the size of the operation. CCX helps size the capacity and negotiate the contract with Salesforce.

Do I need DataWeave to work with MuleSoft?

Yes. DataWeave is MuleSoft's native data transformation language: every transformation between formats, such as JSON, XML, CSV, and EDI, goes through it. CCX has DataWeave specialists and includes training for the client's teams.

Does MuleSoft run in the cloud or on-premises?

Both. CloudHub is the managed SaaS option. Runtime Fabric runs on Kubernetes in your cloud or data center, and the runtime can also run standalone on VMs. The choice depends on security, latency, and control requirements.

Take MuleSoft to the next level.

Thirty minutes with a CCX engineer, at no cost, to analyze your current setup and design the next steps toward an API-led architecture.