Salesforce Connector 10.17 - Mule 4

You can receive a new security token by email if you run Reset Security Token through My Personal Information from the Salesforce Setup pages.

If you plan to create the XML for your Mule app, include the correct namespace and schema location in your XML file. Studio adds this information to the XML file automatically when you add Salesforce Connector to a flow in a Mule app.

Read this document and create your Mule app in Anypoint Studio.

The Additional Configuration Information topic helps you extend your understanding of the connector.

Read XML and Maven Support, the Additional Configuration Information topic, and Examples.

Give your sales team access to all relevant customer data from one system via real-time synchronization of data between Salesforce and your ERP & finance applications. For example, use Anypoint Connector for SAP (SAP Connector) to sync data between Salesforce and SAP and Anypoint Connector for NetSuite (NetSuite Connector) to sync data between Salesforce and NetSuite.

Collect data from multiple Salesforce orgs, other CRMs, ERP systems, and databases into one Salesforce instance or use that information to generate reports.

Easily manage data post-acquisition, move off of a legacy CRM system, or migrate ERP data into Salesforce by automatically moving your data into Salesforce.

Deliver a consistent, connected customer experience across channels, increase customer satisfaction, and drive revenue growth by integrating Salesforce to applications such as ServiceNow, Marketo, and others.

Uses a username and password for authentication

Delegates user authentication to the service hosting the user account

Uses OAuth 2.0 with a JSON Web token (JWT) request for user authentication

Uses OAuth 2.0 with a signed SAML 2.0 assertion to request an access token

Uses OAuth 2.0 with a user and password for authentication

An external system accesses, changes, deletes, or adds data in Salesforce in batches, and vice versa (Salesforce to external system).

An external system accesses, changes, deletes, or adds data in Salesforce, and vice versa (Salesforce to external system).

Salesforce initiates a process in a third-party system and receives an acknowledgment that the process has started. The third-party system continues processing independent of Salesforce.

Salesforce initiates a process in a remote system, waits for the remote system to finish processing, and accepts control returned from the remote system.

The Salesforce UI updates in response to a change in a third-party system.

Salesforce Apex SOAP API exposes Apex class methods as custom SOAP web service calls. This allows an external app to invoke an Apex web service to perform an action in Salesforce.

Salesforce Apex REST API creates your own REST-based web services using Apex. This API has all of the advantages of the REST architecture, while adding the ability to define custom logic and including automatic argument or object mapping.

Salesforce Bulk API quickly and securely loads batches of your organization’s data into Salesforce. See also Load Data in Batches.

Salesforce Metadata API manages customizations and build tools that work with the metadata model, not the data itself.

Salesforce SOAP API provides secure access to your organization’s information on Salesforce. Most of the operations that Salesforce Connector performs map to this API.

All the Salesforce operations performed through the SOAP API have an optional parameter called Headers that can take any of the Salesforce SOAP headers.

Salesforce Streaming API securely receives notifications about changes to your organization’s information in Salesforce. See Create a Streaming Channel to Receive Data from Salesforce for more information about the use of the Streaming API.