How to Connect
Prerequisites
Before setting up the SugarCRM integration in iPaaS.com, ensure the following:
API URL: Obtain the API URL for your SugarCRM REST API. The URL must use HTTPS and include the API version.
Example:
https://demo.sugarcrm.com/rest/v11_25
SugarCRM Credentials: Ensure you have valid API credentials, including a username and password with read/write permissions for accounts and contacts.
Web Logic Hooks:
In SugarCRM, navigate to Admin > Web Logic Hooks and enable the required hooks.
Configure
cron.php
on the SugarCRM server to process queued webhook events. It is recommended to run this as frequently as possible.
Configure Subscription Settings
Navigate to the SugarCRM subscription settings in iPaaS.com and provide the following details:
โ
Field | Description | Required | Example |
Name | A unique name for identifying your SugarCRM subscription. | Yes |
|
Version | Select the integration version. | Yes | `v1.0 (10700 |
API URL | The API endpoint for SugarCRM REST API. | Yes |
|
Username | The API username for accessing SugarCRM. | Yes |
|
Password | The password for the API username. | Yes |
|
Authentication Methods
The SugarCRM integration uses OAuth 2.0 for authentication. Follow these steps to authenticate:
Navigate to the Subscription Settings for SugarCRM in iPaaS.com.
Enter the following details:
API URL: The base URL for your SugarCRM REST API (e.g.,
https://demo.sugarcrm.com/rest/v11_25
).Username: Your SugarCRM API username.
Password: Your SugarCRM API password.
Save the configuration.
Return to the integration settings page, click on the lock icon at the top and follow the prompts to authenticate with SugarCRM.
Initialization Support
Currently, initialization is not supported for SugarCRM in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.
Throttling
Throttling ensures that SugarCRM' API isnโt overwhelmed by excessive API calls, preserving system performance during heavy data transfers.
While the throttling fields are required, the values are pre-populated by the integration settings. For more details, refer to Subscription Configuration โ Edit.
Webhook Information and Troubleshooting
Enabling Web Hooks:
Webhook Queue Handling:
SugarCRM uses
cron.php
to transfer queued webhook events. Ensurecron.php
is properly configured and executed as frequently as possible on the SugarCRM server.Refer to external guides for detailed configuration steps.
Troubleshooting Web Logic Hooks:
Webhook jobs are stored in the job_queue table. Use the following query to investigate issues:
SELECT * FROM job_queue WHERE target = 'class::WebLogicHook' ORDER BY date_modified DESC;
Important: A "Success" status in
job_queue
indicates the job was processed but does not confirm that data transfer to iPaaS was successful.
Limitations of SugarCRM's Web Logic Hooks:
Missing features include:
Eliminating redundant API calls.
Triggering calls based on advanced business logic.
Capturing responses from the target server.
Retrying failed jobs and notifying users.