Overview
MuleSoft Composer lets Salesforce admins and business technologists build integrations by clicks. A Composer flow starts with a trigger, such as a record created or updated in Salesforce, a schedule, or an invocation from another tool, and then runs actions through prebuilt connectors for apps such as Salesforce, NetSuite, Workday, Slack, Google Sheets, ServiceNow and generic HTTP endpoints.
The section covers four skills. You connect systems by creating connections and choosing the right trigger and actions. You control flow logic with If/Else blocks and For Each loops. You reshape data with the formula editor's number, string and date functions as you map fields from one system to another. Finally, you test the flow against connected systems and activate it only when it behaves as expected. Composer is often the fastest way to deliver the integration part of a hyperautomation project, and it can also start MuleSoft RPA processes through its RPA connector.
How it's tested
Composer questions describe a simple integration need in business terms and ask which trigger, action, flow control or formula achieves it, or why a test run behaved unexpectedly. The best answer stays within Composer's no-code features and uses the most direct connector, control or function for the job.
-
Pick the trigger and action
A business event in one app should cause an update in another, and you choose the Composer trigger, connector and action.
-
Branch or loop
Only some records should be processed, or a list must be handled item by item, and you choose If/Else or For Each.
-
Fix the data shape
A value arrives in the wrong format, and you pick the formula function that converts numbers, text or dates.
When a Salesforce opportunity is closed won, a sales team wants a row added to a shared Google Sheet, but only for deals above 50,000. The trigger is an updated opportunity record in Salesforce. An If/Else block checks that the stage is Closed Won and the amount exceeds the threshold, and only that branch runs the Google Sheets add-row action. A For Each loop is unnecessary because the trigger delivers one record per run.
Objectives 4
Official objectives from the Salesforce outline, in outline order.
2.1 Given a scenario, connect systems using a Composer flow and connectors.Connections, triggers and actions between Salesforce and other apps.
- What it means
- A Composer flow has one trigger and a sequence of actions. Each step uses a connector and a saved connection that holds the credentials for an app. Triggers include events in a source system, such as a Salesforce record being created or updated, and scheduled runs; actions create, update, search or retrieve records in target systems.
- What to understand
- Choose the trigger that matches the business event, and use search or get actions to look up related data before writing. Connections are created once and reused across flows, and they run with the permissions of the account used to authorize them. Composer also offers an HTTP connector for REST endpoints without a dedicated connector, and an RPA connector for starting bot processes.
- How it shows up
- A scenario describes an event in one app and an update in another, and you choose the trigger and action pair.
- Common confusion
- The connection's user account determines what Composer can read and write, so missing access often comes from that account rather than the flow logic.
2.2 Given a scenario, implement the appropriate flow controls including If/Else blocks and For Each loops.Branching on conditions and iterating over lists.
- What it means
- If/Else blocks run different actions depending on conditions built from field values, with optional Else If branches. For Each loops repeat the enclosed actions for every item in a list, such as the records returned by a search action or the line items of an order.
- What to understand
- Use If/Else to filter which events lead to actions, for example processing only records with a given status. Use For Each when an earlier step returns multiple items; actions inside the loop reference the current item. Order matters: retrieve the list first, then loop. Nested logic is possible but becomes hard to maintain, which is a hint that Anypoint may suit the requirement better.
- How it shows up
- A search returns many contacts that each need an update, and you place the update action inside a For Each loop.
- Common confusion
- If/Else decides whether actions run; it does not loop, so it cannot process each record in a returned list.
2.3 Given a scenario, transform data using number, string, and date functions and formulas.Reshaping values with the formula editor during field mapping.
- What it means
- When mapping a value into a target field, Composer lets you insert formulas built from functions for text (such as concatenation, substring, upper and lower case), numbers (such as rounding and arithmetic) and dates (such as formatting and adding days), combined with data pills from earlier steps.
- What to understand
- Targets often need data in a specific shape: a full name built from first and last name, an amount rounded to two decimals, a phone number trimmed, or a date converted to the format the target app expects. Pick the function family that matches the data type, and watch for nulls and type mismatches that cause a step to fail during testing.
- How it shows up
- A target system rejects a value or needs it combined or reformatted, and you choose the right function type.
- Common confusion
- Formatting a date as text for display is different from passing a date value; the target field type decides which is needed.
2.4 Test Composer flows to ensure they work as expected.Running a flow in test mode before activation.
- What it means
- Composer lets you test a flow before activating it. A test run waits for or uses a real trigger event in the connected systems and then executes the actions, showing the result and data for each step so you can see where a step failed or produced unexpected values.
- What to understand
- Because tests execute real actions, connect flows to sandbox or test accounts while building, and create trigger records that cover each branch. After activation, review run history to confirm successful executions and investigate failures. Change and retest the flow when a connected app's fields or permissions change.
- How it shows up
- A developer must validate a new flow without writing to production records, and you choose testing against sandbox connections.
- Common confusion
- A test run is not a simulation; actions really create or update data in the connected systems.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Composer flow
A no-code integration made of one trigger followed by actions, flow controls and mappings.
- Remember
- One trigger per flow; everything else follows it in sequence.
- Tested as
- The basic unit in every Composer question.
- Trap
- Expecting several independent triggers in a single flow.
-
Connection
Saved authentication for an app that connectors use, created once and reused by flows.
- Remember
- Access is limited by the authorizing user's permissions in that app.
- Tested as
- Explains missing-data and permission errors.
- Trap
- Changing flow logic when the connection user lacks access.
-
Trigger
The event or schedule that starts a flow, such as a Salesforce record created or updated.
- Remember
- Choose the trigger that matches the business event, then filter with If/Else.
- Tested as
- First choice in scenario questions.
- Trap
- Using a schedule when an event trigger exists.
-
If/Else block
Conditional branching with optional Else If branches.
- Remember
- Filters which records lead to which actions.
- Tested as
- Status- or threshold-based processing.
- Trap
- Using it where a list must be iterated.
-
For Each loop
Repeats enclosed actions for each item in a list from an earlier step.
- Remember
- Get the list first, then loop over it and reference the current item.
- Tested as
- Multi-record updates and line items.
- Trap
- Placing the write action outside the loop.
-
Formula functions
Text, number and date functions used while mapping values.
- Remember
- Match the function family to the data type the target needs.
- Tested as
- Data-format scenarios.
- Trap
- Passing a formatted text date into a date field.
-
Data pills
References to output fields from the trigger or earlier steps, used in mappings and formulas.
- Remember
- A pill is only available from steps that run before the current one.
- Tested as
- Mapping questions.
- Trap
- Referencing data from a later step.
-
Test run
Executes the flow once against connected systems before activation, showing step-by-step results.
- Remember
- Actions are real, so use sandbox or test connections.
- Tested as
- Testing objective.
- Trap
- Testing against production connections.
-
Run history
Record of flow executions with success or failure details after activation.
- Remember
- First place to look when an active flow stops producing results.
- Tested as
- Troubleshooting scenarios.
- Trap
- Rebuilding the flow before reading the failed run.
-
HTTP and RPA connectors
Composer connectors for calling REST endpoints without a dedicated connector and for starting MuleSoft RPA processes.
- Remember
- They extend Composer to APIs and to interface-only systems.
- Tested as
- Hyperautomation patterns linking Composer to other tools.
- Trap
- Assuming Composer cannot reach apps beyond its named connectors.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
If/Else vs. For Each
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| If/Else | Runs actions when conditions match | Chooses a path once per run | Using it to process every item in a list |
| For Each | Repeats actions per list item | Iterates over a collection from an earlier step | Looping over a single trigger record |
Composer vs. Anypoint for an integration
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Composer | Clicks-based flows with prebuilt connectors | Fast, admin-owned, simple logic | Forcing complex orchestration or high volume into it |
| Anypoint Platform | Developer-built Mule applications and APIs | Complex transformation, policies, reuse at scale | Using it for a quick two-app field sync |
Test run vs. run history
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Test run | Executes a flow before activation | Validates a draft with live connected data | Assuming it does not write data |
| Run history | Log of executions of an active flow | Diagnoses production failures | Skipping it when troubleshooting |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Schedule instead of event
- What candidates pick
- Run the flow every hour to look for changed records.
- Why it looks right
- Schedules feel predictable and catch everything.
- Why it's wrong
- An event trigger reacts to each change directly, avoiding delay and duplicate processing when the source supports it.
Clue to watch for The requirement says when a record is created or updated.
-
If/Else for a list
- What candidates pick
- Add an If/Else block to process all returned records.
- Why it looks right
- Conditions seem to apply to the records.
- Why it's wrong
- If/Else evaluates once and does not iterate; each list item needs a For Each loop.
Clue to watch for A search action returns multiple records.
-
Code it in Anypoint
- What candidates pick
- Hand a simple Salesforce-to-Slack notification to integration developers.
- Why it looks right
- Developers can build anything.
- Why it's wrong
- Composer has the connectors and delivers this without code or a development cycle.
Clue to watch for Admin team, supported apps, simple mapping.
-
Production test
- What candidates pick
- Test the flow with the live production connection to see real data.
- Why it looks right
- Production data is realistic.
- Why it's wrong
- Test runs perform real actions, so they can create or change production records.
Clue to watch for The question stresses not affecting live records.
-
Text date into a date field
- What candidates pick
- Format the date as a readable string and map it to the target date field.
- Why it looks right
- It looks correct to a person reading it.
- Why it's wrong
- Date fields need a date value in the expected format; a display string can fail or be misread.
Clue to watch for The target field type is date or datetime.
Answer framework
Build a Composer answer in the same order you would build the flow itself.
- Confirm the requirement fits Composer: supported apps, simple logic, admin ownership and modest volume with no custom code or API governance needs.
- Choose the trigger that matches the business event, using an event trigger where the source supports one and a scheduled trigger only when it does not.
- Add search or get actions to gather related data, then If/Else to filter and For Each to iterate any list.
- Map fields with formula functions that match the target data types for text, numbers and dates, and handle empty values explicitly.
- Test against sandbox or test connections across every branch, then activate the flow and watch run history for failed or skipped runs.
Practice question
Want more like this? The Mule-Dev-202 practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Composer is learned fastest by building. Use the Trailhead Composer modules and, if you can access a Composer-enabled org, build three small flows: a record-triggered sync from Salesforce to a spreadsheet, a flow that searches records in a second system and updates each one in a For Each loop, and a flow with If/Else branches that formats names, amounts and dates with formulas.
High-priority topics are trigger choice, For Each placement and the difference between a test run and run history. Underestimated areas are connection permissions and data types, because many failures in practice questions come from a value in the wrong shape rather than wrong logic.
When reviewing questions, describe the flow out loud as trigger, lookup, condition, loop and mapping, and check which of those the answer changes. Then compare the requirement against Composer's limits, since a few questions are really asking whether Composer is the right tool at all. Finish by linking this section to the RPA section, as Composer is one of the ways to start a bot process.
FAQ
How much of the Mule-Dev-202 exam covers Use Composer to automate data integrations in a hyperautomation project?
The Composer section is 12% of the exam, or about seven of 60 questions as an editorial estimate. Composer also appears as an option in tool-selection questions in the best-practices section.
Do I need coding experience for the Composer questions?
No. Composer is a clicks-based tool, and the questions focus on triggers, connectors, flow controls, formulas and testing. Knowing when a need exceeds Composer helps more than any code.
What is the difference between If/Else and For Each in Composer?
If/Else chooses which actions run based on conditions, once per run. For Each repeats its actions for each item in a list, such as the results of a search action.
Does testing a Composer flow change real data?
Yes. A test run executes the actions against the connected systems, so build and test with sandbox or test connections before switching to production.
Can Composer start a MuleSoft RPA process?
Yes. Composer provides an RPA connector that can start a deployed RPA process, which is one of the hand-off patterns tested in the best-practices section.
How long should I study this section?
Plan about 7 to 9 hours as an editorial estimate, most of it hands-on building and testing small flows.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 2 knowledge
You have covered Composer connections, triggers, If/Else and For Each controls, formula transformations and testing. Check whether you can choose the right control or function in timed integration scenarios.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Mule-Dev-202 AI tutor Get any concept explained your way