Salesforce

API configuration: salesforce, salesforce-sandbox

Features

Features	Status
Auth (OAuth)	✅
Sync data	✅
Perform workflows	✅
Proxy requests	✅
Receive webhooks	✅

We can implement missing features in <48h, just ask for it in the community.

Getting started

• Get a free Salesforce Developer Edition here (it’s a free Sandbox to test your integration)
• Salesforce OAuth documentation (Step 7 contains the details of what Salesforce returns along with the token)
• Overview of OAuth scopes
• Web API docs (their REST API)

Need help getting started? Get help in the community.

Connection Configuration in Nango

Salesforce uses a different API base URL, called the instance_url, for each customer.

Nango automatically retrieves the instance_url (e.g. https://yourInstance.salesforce.com/) from Salesforce and stores it in the Connection config for you.

If you use the Nango Proxy, it is automatically using the correct API base URL. But, if needed, you can retrieve the instance_url with the backend SDK or Connections API.

API gotchas

• If you or your end-user are authorizing a Salesforce sandbox account, you must use the salesforce-sandbox integration in Nango.
• Salesforce calls the client_id and client_secret as Consumer Key and Consumer Secret.
• To enable offline data access with a refresh token, add the refresh_token (or its synonym, offline_access) scope. By default, access tokens expire in ~2h (but customers can configure this value). Also, check the “Introspect All Tokens” checkbox in your OAuth app settings on the Salesforce developer portal (Salesforce doesn’t share the expiration date of access tokens. Instead, Nango needs to call the Salesforce API to check if access tokens are valid.)
• If you encounter an error in your flow that says invalid_client_id, make sure your (developer) User’s password does not contain any special characters (yes, really.)

Add Getting Started links and Gotchas by editing this page