You are here:
Salesforce Connector
Connect to an external Salesforce account. Perform tasks like syncing contacts or transferring opportunities. Use Salesforce as a data source (trigger) or a data target (action).
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
Connections
To connect to a system, whether it's a data source or a data target, create a connection with that system's required credentials. You can connect to multiple systems within a flow and reuse each connection.
You can create connections in the Integrations tab or in Flow Builder.
Standard Connection
This system uses OAuth2BrowserFlow authentication.
OAuth2BrowserFlow authentication includes features that extend OAuth 2.0 protocol functionality and security.
This system requires this credential information for its connections.
| FIELD | DESCRIPTION |
|---|---|
| Connection Name | Enter a unique connection name that helps you remember the details of this connection. After you create a connection, the system hides the credentials. You can reuse connections. Anyone with the Manage Integration Connections permission can see and use all connections in the org. |
| URL | Enter the base URL of your org, not the Lightning redirected URL. For example, the
To check your domain name, go to Setup > Settings > Company Settings > My Domain. Under My Domain Details, your domain name is in the Current My Domain URL field. |
| Environment | Select the environment type for the connection. |
Named Credential Connection
Select a pre-existing named credential from Setup to use for your external system connections.
Before connecting to your external system with a named credential, first create or use an existing authenticated named credential and external credential that is enabled for your users.
To ensure a successful connection for use in a flow, use only one principal for each named credential.
- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.
When you create a connection with an existing named credential, note these behaviors:
- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.
Triggers
A trigger initiates the flow when a specified event occurs. Triggers are important for automating business processes because they react to real-time data changes in various systems. For more information about triggers, refer to Create a Flow with a Connector as a Trigger.
These Salesforce triggers are available in Flow Builder.
- On New Or Updated Record Trigger
- On New Record Trigger
- On Updated Record Trigger
These Salesforce objects are available for On New Or Updated Record Trigger, On New Record Trigger, and On Updated Record Trigger.
- Address
- Approval
- Asset
- Audience
- Campaign
- CampaignInfluence
- CampaignMember
- Contract
- ContractLineItem
- Customer
- Entitlement
- Event
- Expense
- Incident
- IncidentRelatedItem
- ItemGroup
- ItemReceipt
- Job
- JournalEntry
- KitItem
- Location
- NonInventoryPurchaseItem
- NonInventoryResaleItem
- NonInventorySaleItem
- Note
- Opportunity
- OtherChargePurchaseItem
- OtherChargeResaleItem
- OtherChargeSaleItem
- Partner
- Payment
- PaymentItem
- PhoneCall
- Pricebook2
- PricebookEntry
- Problem
- ProblemRelatedItem
- PurchaseOrder
- Quote
- QuoteLineItem
- Refund
- ReturnAuthorization
- ReturnOrder
- ReturnOrderLineItem
- SalesOrder
- Seller
- ServicePurchaseItem
- ServiceResaleItem
- ServiceSaleItem
- Shift
- Shipment
- ShipmentItem
- Solution
- Task
- TransferOrder
- User
- UserRole
- Vendor
- VendorBill
- WorkOrder
- WorkOrderLineItem
Actions
An action performs a specific task or operation within a target system. Use actions to automate tasks across different systems without manual intervention, based on conditions set in the flow. For more information about actions, refer to Create a Flow with a Connector as an Action.
In Flow Builder, you can use both dynamic and static Salesforce actions. Dynamic Salesforce actions interact with all standard and custom objects and are compatible with custom fields but they don’t support picklist values. Customize static Salesforce actions by using labels or picklist values. These actions don't support custom fields.
These dynamic Salesforce actions are available in Flow Builder.
- Create Record
- Delete Record
- Get Record By Id
- Get Records
- Update Record
- Upsert Record
Get Records Action
Query searchable objects from each connector by using custom filter logic in the MuleSoft for Flow: Integration Get Records action, which functions like the Salesforce Flow's Get Records element.
The MuleSoft for Flow: Integration Get Records action:
- Defines queried object to ensure flexibility and adaptability across different data sources.
- Specifies available operators and enables the selection of fields, addition of conditions, and sorting of results.
- Defines the logical operator types.
- Includes other metadata to describe the operators available for each field when the available operators differ based on the object type.
- Runs the query request, processes the response, and formats the retrieved data accurately.
- Provides sorting options with custom logic and flexible record output.
- Limits the number of records returned to optimize performance and makes sure that you have access to the most relevant data.
These Salesforce objects are available for Create Record, Delete Record, Get Record By Id, Update Record, and Upsert Record.
- Address
- Approval
- Asset
- Audience
- Campaign
- CampaignInfluence
- CampaignMember
- Contract
- ContractLineItem
- Customer
- Entitlement
- Event
- Expense
- Incident
- IncidentRelatedItem
- ItemGroup
- ItemReceipt
- Job
- JournalEntry
- KitItem
- Location
- NonInventoryPurchaseItem
- NonInventoryResaleItem
- NonInventorySaleItem
- Note
- Opportunity
- OtherChargePurchaseItem
- OtherChargeResaleItem
- OtherChargeSaleItem
- Partner
- Payment
- PaymentItem
- PhoneCall
- Pricebook2
- PricebookEntry
- Problem
- ProblemRelatedItem
- PurchaseOrder
- Quote
- QuoteLineItem
- Refund
- ReturnAuthorization
- ReturnOrder
- ReturnOrderLineItem
- SalesOrder
- Seller
- ServicePurchaseItem
- ServiceResaleItem
- ServiceSaleItem
- Shift
- Shipment
- ShipmentItem
- Solution
- Task
- TransferOrder
- User
- UserRole
- Vendor
- VendorBill
- WorkOrder
- WorkOrderLineItem
These static Salesforce actions are available in Flow Builder.
- Create Account
- Create Case
- Create Case Comment
- Create Contact
- Create Lead
- Create Opportunity
- Create Opportunity Line Item
- Create Order
- Create Order Item
- Create Payment
- Create Price Book
- Create Price Book Entry
- Create Product
- Delete Account
- Delete Case
- Delete Case Comment
- Delete Contact
- Delete Lead
- Delete Opportunity
- Delete Opportunity Line Item
- Delete Order
- Delete Order Item
- Delete Payment
- Delete Price Book
- Delete Price Book Entry
- Delete Product
- Get Account By Id
- Get Case By Id
- Get Case Comment By Id
- Get Contact By Id
- Get Lead By Id
- Get Opportunity By Id
- Get Opportunity Line Item By Id
- Get Order By Id
- Get Order Item By Id
- Get Payment By Id
- Get Price Book By Id
- Get Price Book Entry By Id
- Get Product By Id
- Update Account
- Update Case
- Update Case Comment
- Update Contact
- Update Lead
- Update Opportunity
- Update Opportunity Line Item
- Update Order
- Update Order Item
- Update Payment
- Update Price Book
- Update Price Book Entry
- Update Product
- Upsert Account
- Upsert Case
- Upsert Case Comment
- Upsert Contact
- Upsert Lead
- Upsert Opportunity
- Upsert Opportunity Line Item
- Upsert Order
- Upsert Order Item
- Upsert Payment
- Upsert Price Book
- Upsert Price Book Entry
- Upsert Product
For information about specific limitations for connections and third-party connectors, see MuleSoft for Flow: Integration Limits & Considerations.
File Actions
MuleSoft for Flow: Integration file actions support binary file transfers up to 15 MB, enabling your flow to upload and return files, such as email attachments or documents, from an external system. The actions provide a file as a reusable object variable for subsequent flow actions, such as sending a file to an external system.
The Salesforce connector supports these file-based actions:
- Upload File to Salesforce
- Download File from Salesforce
Polling Frequency
For Salesforce Connector triggers, provide a value for the Polling Frequency field. Select how often the flow checks for record changes. Background jobs can impact polling frequency.
Select a different polling frequency for each flow in your org. With a shorter frequency, the flow runs more often; however, a shorter frequency consumes more API calls. For example, if you have an order management flow, you require instantaneous updates. You can meet this requirement with a 5-minute polling interval (which is 288 API calls per day). In contrast, if your flow updates a pricing catalog, you require only hourly polling of the flow (which is 24 API calls per day).
