Overview
This article catalogs every error the Copper CRM integration can record in the iPaaS.com error logs, grouped by the flow that produces it. Errors appear in iPaaS.com under Dashboard → Integration Monitoring → Error Logs.
Each error carries a stable code in the form COPR-{CATEGORY}-{NUMBER} — for example COPR-NFND-1001. The code appears at the start of the logged message and never changes, even if the wording is later improved. Search this page for the code to find the entry that explains it.
Some resolutions ask you to involve your Managed Integration Service Provider (MiSP) — the partner who set up and maintains your integration. Your MiSP owns your mapping configuration, your connection credentials, and any reconciliation between the two systems, so they are the right first stop whenever an error points at configuration rather than at your data.
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.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Authentication and Connection
Person — To iPaaS.com
Person — From iPaaS.com
Activity — From iPaaS.com
All Flows
Error Collection
Authentication and Connection
These errors occur while connecting to Copper CRM, completing the authorization, or maintaining the webhook subscription.
Connection to Copper CRM Could Not Be Established
COPR-AUTH-1001 - {connection validation message returned by Copper CRM}
Description: The integration tested the connection to Copper CRM before running any transfer and Copper CRM did not accept it. The text after the code is the reason Copper CRM returned. The usual cause is an API Key or API Email that is missing, mistyped, or belonging to a Copper CRM user whose access has been removed.
Resolution: Open the Copper CRM subscription settings in iPaaS.com and confirm the API Key and API Email match a currently active Copper CRM user. Generate a fresh API key in Copper CRM under Settings → Integrations → API Keys if the existing one may have been revoked, re-enter it, and run the connection test again.
Authorization Could Not Be Completed - Client ID Not Configured
COPR-AUTH-1002 - Unable to complete the Copper CRM authorization. The client ID is not configured for this integration version.
Description: The authorization was started but the client ID the integration uses to identify itself to Copper CRM has not been configured. This value is part of the integration's own provisioning, not a setting you enter, so it indicates the integration version was not fully provisioned.
Resolution: This cannot be corrected from the subscription settings. Contact iPaaS.com Support at support@ipaas.com and include the error code and the time the authorization was attempted.
Authorization Could Not Be Completed - Client Secret Not Configured
COPR-AUTH-1003 - Unable to complete the Copper CRM authorization. The client secret is not configured for this integration version.
Description: The authorization was started but the client secret paired with the integration's client ID has not been configured. Like the client ID, this is part of the integration's provisioning rather than a subscriber setting.
Resolution: This cannot be corrected from the subscription settings. Contact iPaaS.com Support at support@ipaas.com and include the error code and the time the authorization was attempted.
Authorization Could Not Be Completed - Redirect URL Not Configured
COPR-AUTH-1004 - Unable to complete the Copper CRM authorization. The redirect URL is not configured for this integration version.
Description: The authorization was started but the redirect URL that Copper CRM returns the subscriber to after approval has not been configured for this integration version.
Resolution: This cannot be corrected from the subscription settings. Contact iPaaS.com Support at support@ipaas.com and include the error code and the time the authorization was attempted.
Authorization Could Not Be Completed - Invalid Authorization Code
COPR-AUTH-1005 - Unable to complete the Copper CRM authorization. The code returned from the authorization request is not valid.
Description: Copper CRM returned a temporary authorization code that the integration could not use. This normally means the browser authorization flow did not finish cleanly — for example the window was closed part-way, the back button was used, or the code expired before the exchange was attempted.
Resolution: Re-run the authorization from the iPaaS.com Copper CRM subscription settings by clicking the Authenticate (lock) button, then complete the Copper CRM sign-in and approval without interruption. Make sure you are signed in to the correct Copper CRM account in that browser before starting.
Authorization Could Not Be Completed - Token Exchange Failed
COPR-AUTH-1006 - Unable to complete the Copper CRM authorization. The temporary code could not be exchanged for a permanent token.
Description: The temporary authorization code was received but Copper CRM rejected the request to exchange it for a permanent access token. This can happen when the authorization is retried after the code has already been used or has expired.
Resolution: Start the authorization again from the beginning using the Authenticate (lock) button on the Copper CRM subscription settings, rather than refreshing or resubmitting the previous attempt. If the exchange fails on a clean attempt as well, ask your MiSP to confirm the subscription is pointing at the intended Copper CRM account.
Webhook Subscription Could Not Be Completed
COPR-EXTN-1003 - Unable to update the Copper CRM webhook subscription.
Description: The integration tried to create or update the Copper CRM webhook subscription — the registration that tells iPaaS.com when records change in Copper CRM — but the Copper CRM connection was not available at that moment. This reports a connection that failed to initialize, rather than a problem with the webhook registration itself or with any value on the subscription.
Resolution: Re-authenticate the subscription using the Authenticate (lock) button on the Copper CRM subscription settings, then ask your MiSP to re-save the subscription so the webhook registration is retried against the refreshed connection. If the error repeats on a freshly authenticated connection, contact iPaaS.com Support at support@ipaas.com — the connection is failing to initialize and no subscriber setting corrects that.
Person — To iPaaS.com
These errors occur when a Copper CRM person is transferred into iPaaS.com as a Customer.
Existing Record Could Not Be Linked by Email
COPR-BIZL-1001 - Unable to link to an existing customer record using the email address. This may result in duplicate customer records.
Description: The integration found an existing iPaaS.com Customer carrying the same email address as the Copper CRM person, but could not record the external-id link between the two records. Because the link was not recorded, a subsequent transfer may create a duplicate iPaaS.com Customer instead of updating the existing one. The same code is used for the opposite direction.
Resolution: Ask your MiSP to check the Customer mapping collection for the record — they can confirm whether a link already exists and re-establish it so the two records resolve to one another. To reduce recurrence, keep email addresses consistent between Copper CRM and iPaaS.com, and avoid maintaining two Copper CRM people who share one email address.
Person — From iPaaS.com
These errors occur when an iPaaS.com Customer is written into Copper CRM as a person.
Existing Record Could Not Be Linked by Email
COPR-BIZL-1001 - Unable to link to an existing customer record using the email address. This may result in duplicate customer records.
Description: The integration found an existing Copper CRM person carrying the same email address as the iPaaS.com Customer, but could not record the external-id link between the two records. Because the link was not recorded, a subsequent transfer may create a duplicate Copper CRM person instead of updating the existing one. The same code is used for the opposite direction.
Resolution: Ask your MiSP to check the Customer mapping collection for the record — they can confirm whether a link already exists and re-establish it so the two records resolve to one another. To reduce recurrence, keep email addresses consistent between Copper CRM and iPaaS.com, and avoid maintaining two Copper CRM people who share one email address.
Person Could Not Be Created or Updated
COPR-EXTN-1004 - Error transferring the person to Copper CRM: {reason}
Description: The person transfer failed for a reason that did not carry its own error code — most often an unexpected internal failure or a connectivity problem during the call. The {reason} at the end of the message is the actual cause. If Copper CRM itself rejected a value, the log shows COPR-EXTN-1001 instead of this code.
Resolution: Read the reason at the end of the message and act on that. A connection or timeout problem usually succeeds on a re-transfer. If the reason is not actionable, ask your MiSP to review the mapping configuration for this collection and re-run the transfer.
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
COPR-NFND-1001 - 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: A Copper CRM 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 matching a Copper CRM person. Transfer that customer first through the Add/Update Copper Person FROM iPaaS.com collection, then re-transfer the transaction. If the collection is not configured, ask your MiSP to enable it — the integration relies on it to create the person automatically.
Activity Type Not Found
COPR-NFND-1002 - 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 until it is corrected.
Resolution: Create the activity type in Copper CRM under Settings → Activity Types, or ask your MiSP to change the activity-type value in the mapping to the name of a type that already exists. The name must be spelled exactly as it appears in Copper CRM. Re-transfer the transaction once the type resolves.
Customer Prerequisite Could Not Be Created
COPR-EXTN-1002 - 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 attempted 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 read the error that transfer produces — it identifies why the person could not be created, for example a required value Copper CRM rejected. Correct that, then re-transfer the transaction.
Transaction Could Not Be Created or Updated
COPR-EXTN-1005 - Error transferring the transaction to Copper CRM: {reason}
Description: The transaction transfer failed for a reason that did not carry its own error code — most often an unexpected internal failure or a connectivity problem during the call. The {reason} at the end of the message is the actual cause. If Copper CRM itself rejected a value, the log shows COPR-EXTN-1001 instead of this code.
Resolution: Read the reason at the end of the message and act on that. A connection or timeout problem usually succeeds on a re-transfer. If the reason is not actionable, ask your MiSP to review the mapping configuration for this collection and re-run the transfer.
All Flows
These errors can occur in any flow.
Copper CRM Rejected the Request
COPR-EXTN-1001 - Error calling Copper CRM ({action}): {Copper CRM response} (Http Code: {status})
Description: Copper CRM rejected a request and the integration surfaces the response it returned, along with the HTTP status code. Common causes are a required value Copper CRM will not accept as empty — for example an email or phone number sent without a category — or a value Copper CRM considers invalid. An Http Code of 429 means the request rate was exceeded: Copper CRM limits API traffic to 180 requests per minute on a rolling window, and the integration does not automatically reschedule a request rejected for this reason.
Resolution: Read the Copper CRM response in the message, correct the mapped value or the source data in iPaaS.com, and re-transfer. For an Http Code of 429, lower the API Throttle Limit or raise the API Throttle Seconds on the Copper CRM subscription settings, and reduce Concurrent Connections and Concurrent Batch Executions before re-running large jobs; for loading a large volume of existing data, use the bulk-sync approach described in the Known Limitations article rather than one large run. If the response text does not identify an actionable field, ask your MiSP to review the mapping that produced the value. If the failing call is a webhook registration, also confirm an API Key and API Email are entered on the Copper CRM subscription settings — Copper CRM requires an API key for webhook management, separately from the OAuth authorization used for data calls, and a blank key is rejected at the point of the call.
Invalid Primary Key Value
COPR-VALD-1001 - Invalid data passed to {ClassName}.SetPrimaryKey{.FieldName}: {PrimaryId}
Description: The integration was given a record identifier it could not interpret as a valid key for the record type being transferred. This normally means a mapping is supplying an identifier from the wrong field, or the source record's identifier is empty.
Resolution: Ask your MiSP to review the mapping that supplies the identifier named in the message and confirm it is sourced from the correct field. Once corrected, re-transfer the affected records.
Invalid Key Value - Integer Expected
COPR-VALD-1002 - Invalid key value at {Location}. MappingCollectionType = {type}, ExpectedDataType = Integer, PKValue = {Id}
Description: The identifier supplied for this record type must be a whole number, and the value received was not one. The message names the collection type and the value that failed.
Resolution: Ask your MiSP to review the mapping for the collection type named in the message and confirm the identifier is sourced from a numeric field. Once corrected, re-transfer the affected records.
Invalid Key Value - One Separator Expected
COPR-VALD-1003 - Invalid key value at {Location}. MappingCollectionType = {type}, ExpectedDataType = String with one separator, PKValue = {Id}
Description: This record type is identified by a composite key made of two parts joined by a separator, and the value received did not have that shape. The message names the collection type and the value that failed.
Resolution: Ask your MiSP to review the mapping for the collection type named in the message and confirm the identifier is built from both parts of the composite key. Once corrected, re-transfer the affected records.
Invalid Key Value - Two Separators Expected
COPR-VALD-1004 - Invalid key value at {Location}. MappingCollectionType = {type}, ExpectedDataType = String with two separator, PKValue = {Id}
Description: This record type is identified by a composite key made of three parts joined by separators, and the value received did not have that shape. The message names the collection type and the value that failed.
Resolution: Ask your MiSP to review the mapping for the collection type named in the message and confirm the identifier is built from all three parts of the composite key. Once corrected, re-transfer the affected records.