Integrate iPaaS.com with Copper CRM to enable seamless data synchronization for people, addresses and transaction activity.
How to Connect
Prerequisites
Before configuring the Copper CRM subscription in iPaaS.com, obtain the following from your Copper CRM account. You need an account with permission to reach Settings in Copper CRM.
API URL: the Copper CRM API host,
https://api.copper.com.API Key: generated in Copper CRM under Settings → Integrations → API Keys, then Generate API Key. Copy the key when it is shown and store it somewhere safe.
API Email: the email address of the Copper CRM account the API Key was generated under.
Configuration Details
Each value you collect above is entered on the Copper CRM subscription in iPaaS.com:
API URL: the Copper CRM API host that every request is sent to. Example:
https://api.copper.comAPI Key: authorizes the integration against Copper CRM and is what allows iPaaS.com to subscribe to Copper CRM webhooks. Example:
a1b2c3d4e5f6g7h8i9j0API Email: identifies the Copper CRM user the API Key belongs to. Example:
integrations@yourcompany.com
Configure Subscription Settings
Open the Copper CRM subscription in iPaaS.com and complete the following fields.
Field | Description | Required | Example |
Name | A unique name for this subscription. | Yes | Copper CRM Production |
Versions | The iPaaS.com integration version this subscription runs. Pre-populated when the subscription is created. | Yes | v1.0.0 |
API Email | The email address of the Copper CRM account the API Key was generated under. Supplied together with the API Key. | No |
|
API Key | The key generated in Copper CRM. It is not required to save the subscription, but it is required in order to subscribe to Copper CRM webhooks. Without it, records transfer only by Manual Sync. | Conditional |
|
API URL | The Copper CRM API host that requests are sent to. | Yes |
|
API Throttle Limit | The maximum number of requests the integration sends to Copper CRM within each throttle window. | Yes | 500 |
API Throttle Seconds | The length of the throttle window, in seconds, that the limit above is measured over. | Yes | 60 |
API Throttle Limit (to iPaaS) | The maximum number of requests sent into iPaaS.com within each inbound throttle window. | Yes | 500 |
API Throttle Seconds (to iPaaS) | The length of the inbound throttle window, in seconds. | Yes | 60 |
Concurrent Connections | How many connections the integration opens at once. | Yes | 10 |
Concurrent Batch Executions | How many transfers the integration runs in parallel when processing a batch. | Yes | 10 |
Webhook API Key | Generated by iPaaS.com. It authenticates the webhook notifications Copper CRM sends to iPaaS.com, and is copied from this page when the webhook subscription is set up. | No | (generated) |
NOTE: As the settings page states, the throttle and concurrency values determine how frequently and how much data moves at once, and should be reduced if you encounter rate limit errors. See Throttling below.
Authentication Methods
Copper CRM accepts either an API Key or OAuth 2.0. You can use OAuth 2.0 for day-to-day requests, but an API Key is required in order to subscribe to Copper CRM webhooks, so enter an API Key if you want records to transfer automatically.
Option 1 — API Key
In Copper CRM, go to Settings → Integrations → API Keys.
Click Generate API Key.
Copy the generated key.
In iPaaS.com, enter the API URL, the copied API Key and the API Email on the Copper CRM subscription settings, then click Apply.
Option 2 — OAuth 2.0
Open the Copper CRM subscription settings in iPaaS.com.
Click the Authenticate (lock) button to start the OAuth flow.
Sign in to Copper CRM if prompted, then authorize iPaaS.com to read and modify your Copper CRM records.
Refresh the iPaaS.com subscription. An access token is generated automatically. The Copper CRM access token does not expire, so the authorization does not need to be renewed on a schedule.
Confirm the connection in Copper CRM under Settings → Integrations → Integrations, where iPaaS.com appears under Active Connections.
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.
To load a large volume of existing Copper CRM records, use the supported bulk sync using Postman approach.
Throttling
Throttling ensures that Copper CRM's API is not overwhelmed by excessive API calls, preserving system performance during heavy data transfers.
Copper CRM limits API traffic to 180 requests per minute on a rolling window and rejects requests beyond that limit. Set the subscription's throttle and concurrency values so the integration stays within that limit — this matters most during bulk or backfill runs, where a single transfer can consume several requests.
While the throttling fields are required, the values are pre-populated by the integration settings. For more details, refer to Subscription Configuration – Edit.
Related Documents