Overview
This document catalogs the user-facing error messages of the Copper CRM integration, grouped by mapping collection flow. It helps subscribers or their MiSP and iPaaS.com support staff identify, understand, and resolve errors encountered while synchronizing data between iPaaS.com and Copper CRM. Errors appear in iPaaS.com under Dashboard → Integration Monitoring → Error Logs.
Some integration behaviors that are not errors — such as a person being created without a company link when no matching company name exists in Copper CRM — produce no error message. Those behaviors are described in the relevant mapping collection documentation and in the Known Limitations article, not here.
Supported Flows
Authentication and Connection
Person — To iPaaS.com
Person — From iPaaS.com
Activity — From iPaaS.com
General API Errors
Authentication and Connection
Authorization Could Not Be Completed — Missing Credentials
Unable to complete OAuth process in ProcessAuthorization. ClientId is not specified in the CustomFields for this SystemTypeVersion
Description: The OAuth authorization was started but the credentials the integration uses to talk to Copper CRM are not configured. The same error appears for the client secret and the redirect URL. These values are part of the integration's own configuration, not settings the subscriber enters, so this indicates the integration has not been fully provisioned rather than a subscriber mistake.
Resolution: Contact iPaaS.com Support at support@ipaas.com. This is an integration configuration issue that iPaaS.com resolves; there is no subscriber setting to correct.
Authorization Could Not Be Completed — Handshake Failed
Unable to complete OAuth process in ProcessAuthorization. Failed to convert temporary code into a permanent token
Description: The subscriber started the OAuth authorization from the Copper CRM subscription settings, but the temporary authorization code returned by Copper CRM could not be exchanged for a permanent access token. A related message reports that the code returned from the authorize request is not correct. This usually means the authorization did not finish cleanly — for example the browser flow was interrupted or the authorization expired before it completed.
Resolution: Re-run the authorization from the iPaaS.com Copper CRM subscription settings by clicking the Authenticate (lock) button and completing the Copper CRM sign-in and approval. If the authorization still cannot be completed, contact iPaaS.com Support at support@ipaas.com.
Webhook Subscription Could Not Be Completed
Unable to update the Copper CRM webhook subscription.
Description: The integration could not complete a Copper CRM webhook subscription update.
Resolution: Confirm an API Key and API Email are entered on the Copper CRM subscription, since an API Key is required to subscribe to Copper CRM webhooks. If both are present and the error continues, contact iPaaS.com Support at support@ipaas.com.
Person — To iPaaS.com
These errors occur when a Copper CRM person is transferred into iPaaS.com as a Customer.
Existing Customer Could Not Be Linked
Unable to link to an existing customer record using the email address. This may result in duplicate customer records.
Description: During the transfer, the integration found an existing iPaaS.com Customer with the same email address as the Copper CRM person, but could not record the link between the two records. Because the link was not recorded, a duplicate iPaaS.com Customer may be created.
Resolution: Contact iPaaS.com Support at support@ipaas.com so the duplicate can be identified and the records linked. To reduce the chance of recurrence, keep email addresses consistent between the two systems.
Person — From iPaaS.com
These errors occur when an iPaaS.com Customer is written into Copper CRM as a person.
Existing Person Could Not Be Linked
Unable to link to an existing customer record using the email address. This may result in duplicate customer records.
Description: During the transfer, the integration found an existing Copper CRM person with the same email address as the iPaaS.com Customer, but could not record the link between the two records. Because the link was not recorded, a duplicate Copper CRM person may be created.
Resolution: Contact iPaaS.com Support at support@ipaas.com so the duplicate can be identified and the records linked. To reduce the chance of recurrence, keep email addresses consistent between the two systems.
Activity — From iPaaS.com
These errors occur when an iPaaS.com Transaction is written into Copper CRM as an activity.
Customer Not Found for the Transaction
The customer on this transaction was not found in Copper CRM. Ensure the customer exists in Copper CRM, or can be matched by email address, before transferring the transaction.
Description: The activity must be attached to a Copper CRM person, and the integration could not determine which person to use. This happens when the transaction's customer is not linked to a Copper CRM person, the automatic customer transfer did not produce one, and no Copper CRM person matches the transaction's email address.
Resolution: Confirm the transaction carries a customer, and that the customer either already exists in Copper CRM or has an email address that matches a Copper CRM person. Confirm the Add/Update Copper Person FROM iPaaS.com collection is configured, since the integration relies on it to create the person automatically. Re-transfer the transaction once the customer can be resolved.
Activity Type Not Found
The activity type named in the mappings does not exist in Copper CRM. Create the activity type in Copper CRM, or map an existing activity type name spelled exactly as it appears in Copper CRM.
Description: The activity type named in the mapping does not match an activity type that exists in Copper CRM. The integration looks the type up by name, so a name that is misspelled or not yet created in Copper CRM stops every transfer through this collection.
Resolution: Create the activity type in Copper CRM, or change the activity-type value in the mapping to the name of a type that already exists, spelled exactly as it appears in Copper CRM. Re-transfer the transaction.
Customer Prerequisite Could Not Be Created
Unable to create customer. This will prevent the transfer of the order.
Description: The transaction's customer was not yet in Copper CRM, so the integration tried to transfer the customer first and that transfer failed. Because the activity has no person to attach to, the transaction is not transferred either.
Resolution: Transfer the customer on its own through the Add/Update Copper Person FROM iPaaS.com collection and review the error it produces — it identifies why the person could not be created (for example a missing required value). Correct that, then re-transfer the transaction.
General API Errors
These errors can occur across any flow.
Copper CRM Rejected the Request
The message shown is the one returned by Copper CRM for the rejected request.
Description: Copper CRM rejected a create, update or delete request, and the integration surfaces the message Copper CRM returned. Common causes are a required value that Copper CRM will not accept as empty — for example an email or phone number sent without a category — or a value that Copper CRM considers invalid.
Resolution: Read the message text, which comes from Copper CRM and identifies what it rejected. Correct the mapped value or the source data in iPaaS.com and re-transfer. If the message is not actionable, contact iPaaS.com Support at support@ipaas.com.
Rate Limit Exceeded
Copper CRM returns a 429 response when the request rate is exceeded.
Description: Copper CRM limits API traffic to 180 requests per minute on a rolling window and rejects requests beyond that limit with a 429 response. The integration does not automatically reschedule a request that is rejected for this reason, so the affected transfer fails and appears in the error log. Because a single transfer can make several requests — and a transaction transfer can additionally trigger a customer transfer — high-volume or bulk runs are the most likely to reach the limit. (Copper CRM published limit, checked at the time this documentation was written.)
Resolution: Reduce the API Throttle Limit or increase the API Throttle Seconds on the Copper CRM subscription settings so the integration sends fewer requests per window, and lower Concurrent Connections and Concurrent Batch Executions for large jobs. Re-transfer the affected records. For loading a large volume of existing data, use the supported bulk-sync approach described in the Known Limitations article rather than a single large run.
Record Could Not Be Created or Updated
Error transferring the person to Copper CRM: {reason}
Description: A transfer failed part-way through, and the integration reports a general failure message ending with the specific reason returned by Copper CRM. The transaction flow shows the equivalent message beginning "Error transferring the transaction to Copper CRM". The {reason} at the end of the message is the actual cause.
Resolution: Read the reason at the end of the message and act on it — most causes are a rejected value (see Copper CRM Rejected the Request above) or a temporary connectivity problem, in which case re-transferring the record succeeds. If the reason is not actionable, contact iPaaS.com Support at support@ipaas.com.