Setting up a MuleSoft Direct integration is the no-code alternative to a full MuleSoft project. The walkthrough below covers the standard sequence for a typical Salesforce-to-SAP customer sync scenario; the steps are similar for other supported integrations with system-specific differences in credentials and field mappings.
- Confirm MuleSoft Direct licensing and scenario availability
Work with the Salesforce account team to confirm MuleSoft Direct is licensed for the integration scenario you need (Salesforce-to-SAP, Salesforce-to-Workday, etc.). Confirm the scenarios available in your region and the contracted record-volume tier. Document the contracted scope so future admins know what is in and out of license.
- Launch the MuleSoft Direct wizard from Setup
From Setup, search for MuleSoft Direct and open the page. Click New Integration and select the scenario (Salesforce-to-SAP Customer Master Sync). The wizard prompts for credentials and configuration. Provide SAP connection details (host, credentials, target system identifier). Test the connection through the wizard to confirm authentication works.
- Configure mappings and filters
On the next wizard screen, review the default field mappings between Salesforce Account and SAP Customer Master. Adjust mappings if the customer's Salesforce schema differs from the default. Add filters that restrict which records sync (only Accounts with a specific Customer Type, only records created after a certain date). Set the schedule (real-time, hourly, daily). Save the configuration.
- Activate and monitor
Click Activate to enable the integration. The first sync runs immediately (or on the configured schedule). Monitor the Setup page for run history, success and error counts, and any data quality issues that surface. For the first week, check the integration daily and investigate any unexpected behavior. After the initial validation period, settle into the weekly review cadence aligned with other operational monitoring.
- MuleSoft Direct supports only the curated set of integration scenarios. Custom integrations require the full Anypoint Platform.
- Customizations beyond what the wizard supports may be overwritten on the next MuleSoft update. Keep customizations in the wizard.
- Volume tiers apply. Exceeding the contracted volume produces overage charges or throttling, depending on the contract.
- Some target system configurations require specific versions or modules. Confirm compatibility with the target system before configuring.
- Sandbox versus production environments need separate MuleSoft Direct integrations. Cross-environment integration through Direct is not typically supported.