Introducing MuleSoft Composer for Salesforce: The Fastest, Easiest Way to Connect Your Apps and Data to Salesforce

Your users’ day-to-day work probably spans many different systems. They’re using Salesforce (of course!) but they also use email and perhaps spreadsheets. Maybe your company also uses NetSuite for inventory management, Workday for human resources, Slack for team communication, Box or Dropbox for file storage… the list goes on!

These systems and applications neatly store all the data needed to function on their own, but our business processes are anything but siloed. If the inventory in NetSuite isn’t also in Salesforce, your salespeople need to switch back and forth between applications. Not only is that slow, it also increases the chance that data will be inconsistent across those applications.

MuleSoft solves this exact problem: unlocking data across applications to deliver connected experiences. But MuleSoft has traditionally been a developer tool, out of reach for most admins — and that has meant waiting for development resources to complete your high-priority projects.

We know that YOU, #AwesomeAdmin, are an innovator. With Salesforce’s declarative tools, you find creative ways every day to make your users more effective and help your company grow. So we built MuleSoft Composer for you to break down data silos and automate integrations yourselves — with clicks, not code. And you’ll do all of this directly within Salesforce, where you already live.

How does MuleSoft Composer work?

MuleSoft Composer shows up as an app in Lightning App Launcher. In the Composer Flows tab, you’ll see a list of any Composer flows that you’ve already created, and whether they’re active or not. These flows will run in MuleSoft, but you’ll create them from Salesforce. You don’t have to be a MuleSoft customer — the price for MuleSoft Composer includes a managed version of the MuleSoft runtime where your Composer flows will run.

Composer’s secret sauce is the library of connectors to systems like Salesforce, Workday, and NetSuite. We’ll be releasing new connectors every month after GA, so you’ll be able to connect the applications you need. (Later in 2021 — safe harbor, of course — we also plan to release a version of MuleSoft Composer for existing MuleSoft customers, where IT can provide additional connectors and APIs for admins to use!)

When you create a new Composer flow, you first connect to the system where you want the flow to start, and then choose the event that triggers the flow. (You can also choose to run the Composer flow at a scheduled interval instead of having it respond to a trigger on a connection.) If you already know how to use Process Builder or triggered flows in Flow Builder, this is very similar! The main difference is that your Composer flow can start in any system that has a connector.

Now you can add additional steps to take actions in the system where the trigger happened, or any other system that you connect to. Each time you add an action, you’ll first choose the system where that action takes place. There are also some basic flow logic actions, like if/else and loops.

When an action returns a record (or more than one), you can use data from that record in other actions — regardless of which system the data came from. So, you can build a condition that compares data from multiple sources, or map the fields from a record you retrieved from any system in any previous step to create or update a record in another system.

At any time while you’re building, use the Test button to see how your Composer flow is working so far. And when you’re ready to go, activate it!

How can I learn more?

We’ll be launching some new Trailhead modules for MuleSoft Composer in a few weeks, as well as Salesforce Help content. For now, join the MuleSoft Composer group in the Trailblazer Community for more information on the release, and to ask questions or provide feedback.

Also, I chatted about MuleSoft Composer with Gillian Bruce and Mike Gerholdt on the Salesforce Admins podcast — check it out!