How to Connect
Prerequisites
Before setting up the Copper CRM integration in iPaaS.com, ensure the following settings are configured in your iPaaS subscription:
API URL:
https://api.copper.comAPI Key:
Navigate to
Settings > Integrations > API Keysin Copper CRM.Click Generate API Key.
Copy the generated API Key and save it for use in your iPaaS subscription.
Configure Subscription Settings
Navigate to the Copper CRM subscription settings in iPaaS.com and provide the following information:
Field | Description | Required | Example |
Name | A unique name for the subscription. | Yes | Copper CRM Integration |
Version | API version to use. | Yes |
|
API URL | URL for your Copper CRM instance. | Yes |
|
API Key | For development purposes only. Should always be set to | Yes |
|
API Email | Email address associated with the API Key. | No |
|
Authentication Methods
You can authenticate either with the information you obtained above or via oAuth.
Option 1: API Key Authentication
Navigate to Settings > Integrations > API Keys in Copper CRM.
Click Generate API Key to create a new key.
Copy the generated API Key.
In iPaaS.com, enter the API URL () and the copied API Key in the subscription settings.
https://api.copper.com
Option 2: OAuth Authentication
Open the Copper CRM subscription settings in iPaaS.com.
Click the Lock icon (Authentication button) to initiate the OAuth flow.
Log in to Copper CRM if prompted and authorize the iPaaS integration.
After authorization, refresh your iPaaS subscription. An access token will be generated automatically.
Verify the connection in Copper CRM:
Navigate to Settings > Integrations > Active Connections.
Ensure the iPaaS connection is visible.
Initialization Support
Currently, initialization is not supported for Copper CRM in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.
Throttling
Throttling ensures that Shopware’s 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.