Overview
Pre-built tooling
✅ Authorization
✅ Authorization
✅ Read & write data
✅ Read & write data
| Tools | Status |
|---|---|
| Pre-built integrations | ✅ |
| API unification | ✅ |
| 2-way sync | ✅ |
| Webhooks from Nango on data modifications | ✅ |
| Real-time webhooks from 3rd-party API | 🚫 (time to contribute: <48h) |
| Proxy requests | ✅ |
✅ Observability & data quality
✅ Observability & data quality
| Tools | Status |
|---|---|
| HTTP request logging | ✅ |
| End-to-type type safety | ✅ |
| Data runtime validation | ✅ |
| OpenTelemetry export | ✅ |
| Slack alerts on errors | ✅ |
| Integration status API | ✅ |
✅ Customization
✅ Customization
| Tools | Status |
|---|---|
| Create or customize use-cases | ✅ |
| Pre-configured pagination | 🚫 (time to contribute: <48h) |
| Pre-configured rate-limit handling | 🚫 (time to contribute: <48h) |
| Per-customer configurations | ✅ |
Accounts
Contacts
Leads
Opportunities
| Function name | Description | Type | Source code |
|---|---|---|---|
create-opportunity | Create a single opportunity in salesforce | Action | 🔗 Github |
update-opportunity | Update a single opportunity in salesforce | Action | 🔗 Github |
delete-opportunity | Delete a single opportunity in salesforce | Action | 🔗 Github |
opportunities | Fetches a list of opportunities from salesforce | Sync | 🔗 Github |
Users
Others
| Function name | Description | Type | Source code |
|---|---|---|---|
fetch-fields | Fetch available task fields, child relationships and validation rules. If the input is not specified then it defaults back to “Task” Data Validation: Parses all incoming data with Zod. Does not fail on parsing error will instead log parse error and return result. | Action | 🔗 Github |
articles | Fetches a list of articles from salesforce | Sync | 🔗 Github |
tickets | Fetches a list of tickets from salesforce | Sync | 🔗 Github |
Access requirements
| Pre-Requisites | Status | Comment |
|---|---|---|
| Paid dev account | ❓ | |
| Paid test account | ❓ | |
| Partnership | ❓ | |
| App review | ❓ | |
| Security audit | ❓ |
Setup guide
No setup guide yet.Contribute improvements to the setup guide by editing this page
Useful links
- Get a free Salesforce Developer Edition here (it’s a free Salesforce account 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)
Contribute useful links by editing this page
Connection Configuration in Nango
Salesforce uses a different API base URL, called theinstance_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-sandboxintegration in Nango. Your Salesforce Developer Edition account is not a Salesforce sandbox! Use it with the regularsalesforceconnector. - Salesforce calls the
client_idandclient_secretasConsumer KeyandConsumer 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.)
Contribute API gotchas by editing this page