How to connect
The Salesforce integration connects iPaaS.com to your Salesforce organization over the Salesforce REST API. Authentication uses OAuth through a Salesforce Connected App: you authorize iPaaS.com once from the subscription settings, and the integration exchanges the resulting authorization code for the access and refresh tokens it uses on every subsequent call.
Prerequisites
Before setting up the Salesforce integration, ensure you have the following:
Salesforce account: Access to a Salesforce account with administrator privileges, so you can create and manage a Connected App.
A Salesforce Connected App: A Connected App must be enabled in your Salesforce organization with OAuth settings turned on. The Connected App supplies the Consumer Key and Consumer Secret that iPaaS.com uses to authenticate. To create one, in Salesforce go to Setup, enter App Manager in the Quick Find box, select App Manager, then create a new Connected App and enable OAuth settings. After saving, open the app and select Manage Consumer Details to view the Consumer Key and Consumer Secret. (Salesforce Help, "Create a Connected App in Salesforce for OAuth", accessed June 2026.)
Your Salesforce instance URL: Confirm the base URL of your Salesforce instance, for example https://your-instance.salesforce.com. This is the API Url value you will enter in iPaaS.com.
Configure subscription settings
Navigate to the Salesforce subscription settings in iPaaS.com and provide the following details.
Field | Description | Required |
API Url | The base URL of your Salesforce instance, for example | Yes |
Consumer Key | The OAuth client identifier from your Salesforce Connected App. | Yes |
Consumer Secret | The OAuth client secret from your Salesforce Connected App. | Yes |
Account Poll Days | The number of days of history the integration looks back the first time it polls Salesforce for account changes. Defaults to 7. | No |
Contact Poll Days | The number of days of history the integration looks back the first time it polls Salesforce for contact changes. Defaults to 7. | No |
The Consumer Key and Consumer Secret must match the values from the Connected App you created in the prerequisites. If either value is missing or incorrect, authentication will fail and no data will transfer.
Authenticate with OAuth
The integration authenticates against Salesforce using OAuth. After you provide the settings above, complete the one-time authorization so iPaaS.com can obtain its access and refresh tokens.
Add the subscription: Enter a name for the subscription and save it.
Authenticate the subscription:
Open the subscription settings in iPaaS.com.
Select the Authenticate button in the top toolbar.
Sign in to Salesforce:
Sign in with your Salesforce credentials.
Grant the requested permissions to iPaaS.com.
Refresh and verify:
After granting permissions, refresh the subscription to confirm the connection.
Confirm that the Access Token and Refresh Token fields are populated. These tokens are managed by the integration; you do not need to enter them manually.
Troubleshooting OAuth authentication
If authentication does not complete, or if the integration reports that the refresh token is missing, reset the OAuth authorization and try again:
Remove the existing tokens in iPaaS.com: In the subscription settings, delete the stored OAuth tokens using the delete icon.
Reset OAuth in Salesforce:
In Salesforce, go to Setup, then Apps, then Connected Apps, and review the Connected Apps OAuth usage.
Locate the iPaaS.com app and reinstall it if prompted.
Uninstall and reinstall if needed: On the Connected App page, uninstall the app, confirm, then reinstall it and retry the OAuth authorization from iPaaS.com.
After resetting, repeat the authentication steps above and confirm that the Access Token and Refresh Token fields are populated.
Initialization and change capture
The integration keeps Salesforce and iPaaS.com in step by polling Salesforce for changes on a schedule; there is no inbound push from Salesforce. The first time the integration polls each record type, it looks back over a configurable window of history so existing records can be picked up:
Account Poll Days: Sets how many days back the integration looks the first time it polls for account changes. Defaults to 7 days.
Contact Poll Days: Sets how many days back the integration looks the first time it polls for contact changes. Defaults to 7 days.
Increase these values if you need the integration to pick up records that changed further in the past on its first run. Because change capture is poll-based rather than real-time, updates appear in the destination system on the integration's polling cycle rather than the instant they are saved in the source.
Throttling
The integration paces its calls to the Salesforce API so that bulk transfers do not overwhelm Salesforce or trip its API limits. The throttling fields shown on the subscription are populated by the integration and are not values subscribers configure. For background on these fields, see Subscription Configuration – Edit.
If a transfer fails or stalls, review the run details under Dashboard / Integration Monitoring / Error Logs for the specific message.
Related Documents