---
schema_version: "1"
id: cf4e097a5c275e9e9a95a23e12335534afcb42e9720e3e299e3a7a76bc98148a
title: Building Process Automation with MuleSoft Composer for Salesforce
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/composer-salesforce/ms_composer_overview.md
canonical_url: https://docs.mulesoft.com/composer-salesforce/ms_composer_overview
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 2c8482814ebcf3e4842b98caf1681e5213e5ab86c06d2c6af97f0c294ba22031
description: MuleSoft Documentation Site
latest: true
---
---
product: Composer for Salesforce
---

# Building Process Automation with MuleSoft Composer for Salesforce

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

MuleSoft Composer for Salesforce (Composer) automates data integration between systems using a
no-code interface within your Salesforce org. You connect different applications and synchronize
data in real-time, creating a unified view of customers and business operations without writing
code.

To automate processes with Composer, you build a flow that contains every step in the process:

- Selecting the data that you specify from a system such as Google Sheets, Tableau, Workday, or a
  Salesforce org

- Performing actions on the data, such as copying it to another system

You choose when to trigger the flow: when something happens, like a change to a record or row, or at
intervals of time that you specify. Flows can be as simple or complex as your business needs.

## Example

Imagine that a regional Slack user-group tracks its local members in a spreadsheet. Slack users
register with the national organization first. Since the national office uses Salesforce to track
membership, automatically pushing new members to the regional sheet would save everyone a lot of
time. Using Composer, the Salesforce admin can create a single flow that automatically performs this
task in near real-time.

![A workflow that describes keeping user information up to date between data silos](/mulesoft/current/en-us/composer-salesforce/_images/images/overview1.png)

This simple flow can be expanded to perform more complex actions, such as writing to different
sheets based on the zip code of the new user or propagating changes for existing users.

## Use Cases

Some common use cases for Composer include:

- **Quote to Cash (ERP Integration)**

  Drive efficiency and improve sales productivity by automating and streamlining quote-to-cash
  processes. For example, automatically create sales orders in NetSuite once a Salesforce
  opportunity closes and automatically notify billing teams in Slack. For more information, refer to
  the
  [NetSuite Automation with MuleSoft Composer](https://trailhead.salesforce.com/content/learn/modules/netsuite-data-sync-with-mulesoft-composer)
  Trailhead module.

- **Case Escalation (Ticketing System Integration)**

  Escalate and resolve cases faster by automating support case management and notification. For
  example, automatically create a JIRA ticket and automatically send a Slack notification to
  organize and prioritize urgent support cases from Service Cloud or Zendesk to streamline
  communication between agents, engineering, and DevOps. For more information, refer to the
  [Jira Automation with MuleSoft Composer](https://trailhead.salesforce.com/content/learn/modules/jira-data-sync-with-mulesoft-composer)
  Trailhead module.

- **Salesforce to Salesforce**

  Connect and synchronize data between multiple Salesforce orgs. For example, create or update an
  object in one Salesforce org and sync the changes to another Salesforce org. For more information,
  refer to the
  [Automation Between Orgs with MuleSoft Composer](https://trailhead.salesforce.com/content/learn/modules/data-sync-between-orgs-with-mulesoft-composer)
  Trailhead module.

## Steps To Create a Flow

To create a functioning, real-time integration in Composer, you don’t need coding experience. Simply
open Composer, and then create a flow that contains all the steps you need to get data from Point A
to Point B:

Step 1: Choose or create a connection

A connection is the username and password you’ll use to access the data you want to work with, plus
the URL where you typically enter those credentials. Some systems require a few additional pieces of
information, such as a security token.

After you define the connection, you can use it multiple times in the same flow or in different
flows that you create. Composer never exposes your credentials, and the connections are available
only to you, even if other people are also building flows.

Instead of a connection, you can choose to schedule a time when the flow runs, such as every 10
minutes.

Step 2: Choose a trigger

Every flow that uses a connection starts with a trigger: an event such as creating a new record.
This event always triggers the flow to run. The events available to trigger a flow depend on the
connection you choose.

If a scheduled time is chosen instead of a connection, no trigger is needed, because the flow runs
at the chosen interval.

Step 3: Define the actions you want to take

Define what happens to the data fetched by the trigger, and when those actions should be taken; for
example, to fetch all records for a specific time period but only copy over the records that have
changed or that are new. You might also want to copy over only some information from each record,
rather than the entire record.

Using the triggers and actions of Composer, you can make the flow as elaborate or as simple as
necessary.

If you start the flow at a specified time interval instead of choosing a connection, then you’ll
fetch data as part of the first action.

Step 4: Test your flow on one record

As you define triggers and actions, you see sample data that helps you verify you are building the
right steps. You can test every change before making the next one, making it easier to find and
correct issues with your flow. Your changes will not appear until you activate the flow.

Step 5: Activate the flow

After testing, activate the flow in your production org. After the flow is activated, it
automatically runs when the conditions in the trigger are met.

Step 6: Monitor the behavior of your flow

You can see what your flow is doing by looking at the data provided on the flow detail page in
Composer.

Mapping data between systems and doing exactly the right thing at the right time sometimes feels
complicated; however, using Composer helps you break down the logic into the steps required. You can
experiment with a flow until you’ve got it working just right, and you can add complexity to it as
you discover new use cases.

## Access Composer

Access the home page to start using Composer for your business needs:

![Mulesoft Composer for Salesforce Home page](/mulesoft/current/en-us/composer-salesforce/_images/images/overview-page-sf.png)

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td><strong>Home</strong>: View the Composer home page.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td><strong>Templates</strong>: Leverage <a href="https://docs.mulesoft.com/composer-salesforce/ms_composer_build_a_flow_using_templates">pre-built Composer templates</a> to build your flow.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td><strong>Composer Flows</strong>: Create, test, activate, and monitor your <a href="https://docs.mulesoft.com/composer-salesforce/ms_composer_flows">flows</a>.</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td><strong>Usage Summary</strong>: View your <a href="https://docs.mulesoft.com/general/automation-credits-usage-and-rates">monthly tasks and credit usage per flow</a> for your organization.</td></tr><tr><td><i data-value="5"></i><b>5</b></td><td><strong>Create New Flow</strong>: Create your new flow <a href="https://docs.mulesoft.com/composer-salesforce/ms_composer_using_a_flow_and_creating_trigger#create-a-flow">from scratch or from a template</a>.</td></tr></tbody></table>

## Next Steps

1.  Review [How Composer Works](https://docs.mulesoft.com/composer-salesforce/ms_composer_about_flows) to understand how the different parts of a
    flow work together to automate processes. If you want more help, you can use Salesforce
    Trailhead or visit the MuleSoft blog post about Composer.

2.  Create a plan for your first flow using the [checklist](https://docs.mulesoft.com/composer-salesforce/ms_composer_checklist).

3.  Open Composer in your Salesforce org and build your first flow.

## Additional Learning Resources

- [Trailhead: MuleSoft Composer Installation and Configuration](https://trailhead.salesforce.com/content/learn/modules/mulesoft-composer-install-and-config/)

- [Trailhead: MuleSoft Composer Basics](https://trailhead.salesforce.com/content/learn/modules/mulesoft-composer-basics/)

- [MuleSoft blog post](https://blogs.mulesoft.com/news/introducing-mulesoft-composer/)

## Related Resources

- [Getting Started](https://docs.mulesoft.com/composer-salesforce/ms_composer_prerequisites)

- [Composer Connector Reference](https://docs.mulesoft.com/composer-salesforce/ms_composer_reference)

- [Knowledge Articles](https://help.salesforce.com/s/)
