Get to Know MuleSoft for Flow Connectors
Learning Objectives
After completing this unit, you’ll be able to:
- Explain how MuleSoft for Flow connectors work within Agentforce IT Service.
- Articulate the difference between MuleSoft for Flow and MuleSoft Direct.
- List key connector categories and example use cases relevant to IT automation.
How Connectors Work in Agentforce IT Service
In the previous unit, you discovered the channels employees use to reach out for help. Now, let’s examine how your AI agents take action in external systems.
Connectors are essentially prebuilt Flow actions. When an agent needs to reset an Okta password or create an epic in Aha, it uses these connectors to get the job done without requiring you to write any custom code. That means there’s no need to drag in a team of developers to build and maintain these connections for you.
The invocation model operates as a complete, step-by-step round-trip. In the image, the invocation flows from left to right, and the response flows back from right to left. Note that the AI agent never connects directly to the external system.
-
Invocation: When an AI agent needs to take action, it calls a MuleSoft Flow. That flow invokes the relevant connector, which then communicates with the external system.
-
Response: Once the action is complete, the external system passes the result back to the connector, then MuleSoft Flow, and finally to the agent, which sends a response to the employee.
These connectors are the engine behind zero-touch fulfillment, which is the mechanism that lets your Unified Catalog automatically provision, route, and close requests end to end.
License, Security, and Authentication
-
License: Keep in mind that MuleSoft for Flow is licensed separately.
-
Security and authentication: Admins may wonder how these connectors securely authenticate with external systems. It depends on what the third-party products support. Overall integration security follows the standards outlined at security.salesforce.com. Because this is an introductory badge, it doesn’t cover specific security and authentication configurations.
MuleSoft for Flow Versus MuleSoft Direct
Let’s clear up a potential point of confusion out in the field: the difference between MuleSoft for Flow and MuleSoft Direct.
MuleSoft |
What It Does |
Primary Use Case |
|---|---|---|
MuleSoft for Flow |
Gives you access to prebuilt Flow connectors |
IT automation and zero-touch fulfillment |
MuleSoft Direct |
Provides specific employee data integrations |
HR service (such as Workday and SAP SuccessFactors) |
With those differences in mind, how do you decide what your IT team needs?
Best Practice
Stick with MuleSoft for Flow for your standard IT automations. MuleSoft Direct is only required when you need to integrate HR employee data from platforms like Workday or SAP SuccessFactors.
Key Connector Categories and Use Cases
What can these connectors do for your IT team? Here is a breakdown of key categories and how you can use them for IT automation.
Category |
Example Connectors |
Example IT Automation Use Case |
|---|---|---|
Identity and Access Management (IAM) |
Microsoft Entra ID, Okta, Jamf, Intune |
Provision or deprovision users when a service request is fulfilled |
Monitoring and observability |
Datadog, SolarWinds |
Auto-create incidents from alerts triggered by threshold breaches |
Development and project tools |
Aha, Asana, ClickUp |
Create or update work items when a change request is approved |
AI/LLM |
Anthropic, Google Gemini |
Augment agent reasoning with external model calls |
Competing IT service management (ITSM) |
Legacy ITSM platforms |
Route escalations to legacy ITSM platforms |
And that table is only a fraction of what’s available! Check out the link in the Resources section for a complete list of hundreds of MuleSoft for Flow connectors and discover what else you can automate.
What’s Next?
Now you understand how the two integration layers work independently. Next, you explore them in action together in a real-world scenario: a complex, multi-industry enterprise that already has a legacy ITSM platform in place. The final unit awaits!