Salesforce Data 360 (formerly Data Cloud) is a data platform that unifies all of your customer data.
Set up a connection
After you start the connection, configure it in the Create connection panel and complete all of the required * authentication settings:
| Setting | Instructions |
|---|---|
| Name your connection * |
Enter a clear and distinguishable name. Throughout integrator.io imports and exports, you will have the option to choose this new connection. A unique identifier will prove helpful later when selecting it from a list of the connections in your account. |
| API type * |
Choose your Salesforce Data 360 API type:
Each API type uses a different OAuth 2.0 client. |
| Data 360 Connect API | |
| Data cloud instance URL * | Enter your Salesforce instance URL without the protocol. For example, orgfarm-86481ld167-dev-ed.develop.my.salesforce.com. |
| OAuth 2.0 client * |
Select the OAuth 2.0 client that stores the client ID and client secret of your Salesforce connected app. To create an OAuth 2.0 client, select Create iClient (+) and enter the following:
For detailed information on retrieving the consumer key and consumer secret, see View and rotate the consumer key and consumer secret of a connected app. Multiple layers of protection, including AES-256 encryption, are in place to keep your client secret safe. When editing this OAuth 2.0 client, you must re-enter this value each time; it is stored only when the client is saved and never displayed as text. |
| Data API | |
| Data cloud instance URL * | Enter your Salesforce instance URL. For example, https://orgfarm-86481ld167-dev-ed.develop.my.salesforce.com. |
| OAuth 2.0 client * |
Select the OAuth 2.0 client that stores the JWT bearer details of your Salesforce connected app. To create an OAuth 2.0 client, select Create iClient (+) and enter the following:
For detailed information on setting up the connected app for JWT bearer authentication, see OAuth 2.0 JWT bearer flow for server-to-server integration. Multiple layers of protection, including AES-256 encryption, are in place to keep your private key safe. When editing this OAuth 2.0 client, you must re-enter this value each time; it is stored only when the client is saved and never displayed as text. |
Tip
This connector documentation describes only the settings shown for the Simple view. For the corresponding HTTP settings, see the OAuth 2.0 auth universal connector documentation.