Integrate iPaaS.com with SugarCRM to enable data synchronization for Accounts, their primary contact, and their billing and shipping addresses. This reference describes the credentials and settings needed to connect a SugarCRM subscription, how authentication works, and how to keep the connection running.
How to Connect
Prerequisites
Before configuring the SugarCRM subscription in iPaaS.com, set up the following in SugarCRM:
API URL: the address of your SugarCRM REST API, including the API version. Enter it without a
https://prefix; the integration always connects over HTTPS. Example:demo.sugarcrm.com/rest/v11_25.API user: a SugarCRM user with read and write permission for Accounts and Contacts. The integration authenticates as this user.
Scheduled job (cron.php): required only if you plan to use automatic transfers. SugarCRM delivers its Web Logic Hook events through the scheduled
cron.phpjob, so it must be enabled and running on the SugarCRM server. See the SugarCRM Installation Instructions for the webhook setup.
Configuration Details
Enter the following on the SugarCRM subscription settings page in iPaaS.com:
API URL: your SugarCRM REST API host and version, without the
https://prefix (for example,demo.sugarcrm.com/rest/v11_25).Username: the SugarCRM API user's username.
Password: the password for that API user.
Configure Subscription Settings
Field | Description | Required | Example |
Name | A name to identify this SugarCRM subscription in iPaaS.com. | Yes |
|
Version | The integration version to install. | Yes |
|
API URL | Your SugarCRM REST API host and version, entered without the | Yes |
|
Username | The SugarCRM API user with read/write access to Accounts and Contacts. | Yes |
|
Password | The password for the API user. | Yes | Your SugarCRM API password |
Authentication Methods
The SugarCRM integration authenticates with OAuth 2.0, using the API user's username and password.
On the SugarCRM subscription settings page, enter the API URL, Username, and Password.
Save the settings.
Establish the connection from the subscription settings so iPaaS.com can validate the credentials.
Once connected, iPaaS.com uses the API URL, username, and password to obtain an OAuth 2.0 access token from SugarCRM, and refreshes that token automatically as it expires — no further action is required. If the credentials are rejected, the connection is not established and the reason is reported on the subscription; confirm the API URL and credentials and try again.
Initialization Support
Currently, initialization is not supported for SugarCRM in iPaaS.com. All data synchronization and mappings must be configured during the integration setup. To bring across a large set of existing records, see bulk sync using Postman.
Throttling
Throttling keeps the SugarCRM API from being overwhelmed by too many calls during heavy data transfers. The throttle fields are required, but their values are pre-populated by the integration's settings, so they do not normally need to be changed. The Concurrent Batch Executions setting bounds how many calls the integration runs in parallel during batch transfers. For details on adjusting these values, refer to Subscription Configuration – Edit.
SugarCloud instances are also subject to SugarCRM's own published limit of 20 API requests per second; when that limit is reached, the transfer is retried automatically once the limit window resets.