Summary
iPaaS.com Customer records can be written into Copper CRM as People through outbound data flows or Manual Sync. Each transfer writes the customer's name, a single email address and phone number with their categories, the address taken from the customer's primary billing address, and the company the person belongs to. Copper CRM person custom fields can also be populated.
ID Format
Manual Sync ID Format
Enter the iPaaS.com Customer ID — the identifier iPaaS.com assigns to the Customer record.
External ID Format
After a successful transfer, iPaaS.com records the Copper CRM person's identifier against the iPaaS.com Customer on a dedicated external-ID record. That link is the primary match for later transfers, routing a repeat transfer of the same Customer to an update of the existing Copper CRM person rather than creating a second one. Where no link exists yet, the integration falls back to matching a Copper CRM person on the email address and records the link once a match is found.
Deleted Record Support
Delete is supported. When a delete is dispatched for a linked Customer, the integration removes the corresponding person from Copper CRM using the recorded external-ID link.
Custom Field Support
iPaaS.com Customer custom field values can be written into Copper CRM person custom fields.
Custom fields are matched by name and must exist on both sides before any value moves. Create the Copper CRM field under Settings → Customize → Manage Fields On Records → People → Create Field, then create a Customer custom field with exactly the same name in the iPaaS.com Copper CRM subscription. If the names differ, no value is written.
Mapping Collection Status
Status: Enabled.
Trigger Events: the iPaaS.com Customer change events the subscriber enables under Outbound Data Flows. Whether a change results in a person being added or updated in Copper CRM depends on whether the Customer is already linked to a Copper CRM person, not on which event fired.
Duplicate or Conflicting Mappings
The following mapping collections operate on the same records in the opposite direction:
Add/Update Copper Person TO iPaaS.com: transfers Copper CRM People into iPaaS.com as Customers.
Add/Update Copper Person Address TO iPaaS.com: transfers the Copper CRM person's address into iPaaS.com as a Customer Address.
Before enabling both directions, review the mapping collection filters and decide which system is the source of truth for people data. With both active on the default mappings, changes may propagate back and forth. Because Copper CRM holds only one address per person, the inbound and outbound address mappings write to the same single address.
Supported Child Collections
This collection has no child collections. The address, email address and phone number are written onto the Copper CRM person record itself as part of this transfer, because Copper CRM holds one of each against a person rather than as separate records.
System Caveats
Copper CRM Caveats
One address per person: Copper CRM only permits one address to be saved against a person. The address written is taken from the iPaaS.com Customer's primary billing address; a Customer with no primary billing address transfers without address values.
One email and one phone entry: a single email address and a single phone number are written, each under the category set by the category mappings.
Email and phone categories are required: Copper CRM requires a category on every email address and phone number held against a person, so those mappings must not be left empty.
Companies must already exist: the integration attaches people to existing Copper CRM companies by name. It does not create a company that is not already there.
Custom fields must exist first: values can only be written to Copper CRM custom fields that already exist.
API request limits: Copper CRM limits API traffic to 180 requests per minute on a rolling window and rejects requests beyond it. Rejected transfers appear under Dashboard → Integration Monitoring → Error Logs. Set the subscription's API Throttle Limit, API Throttle Seconds, Concurrent Connections and Concurrent Batch Executions so the integration stays within the limit.
iPaaS.com Caveats
Primary billing address drives the address values: the address, and the phone number written with it, come from the Customer address flagged as primary billing. Customers whose addresses carry no primary billing flag transfer without those values.
Custom fields must exist first: a Customer custom field with a matching name must exist in the iPaaS.com subscription before its value can be written to Copper CRM.
Integration-Specific Caveats
Duplicate prevention by email: when an iPaaS.com Customer is not yet linked, the integration searches Copper CRM for a person with the same email address and links the two records instead of creating a duplicate. Leaving the email mapping empty therefore raises the risk of duplicate people.
Company linking is by name and fails silently: where no Copper CRM company matches the customer's company name, the person is created without a company link and no error is raised. Confirm company names are spelled the same way in both systems.
Setup Requirements
Copper CRM Configuration
Create any person custom fields you intend to write to, under Settings → Customize → Manage Fields On Records → People → Create Field.
Create the companies people should be attached to, so the company name lookup can resolve them.
iPaaS.com Configuration
Enter the API URL, API Key and API Email on the Copper CRM subscription. See the Copper CRM Connections and Settings article for the full field reference.
Create Customer custom fields with names matching the Copper CRM fields.
Enable the relevant iPaaS.com Customer events under Outbound Data Flows so changes transfer automatically.
Integration Flow
A Customer is created or changed in iPaaS.com and dispatched through the subscribed outbound data flow, or the transfer is started from the Manual Sync page using the iPaaS.com Customer ID.
The integration checks whether the Customer is already linked to a Copper CRM person. If it is not, it searches Copper CRM for a person with the same email address and records a link when one is found, so that an existing person is updated rather than duplicated.
The company the person should be attached to is resolved from the company name held on the Customer.
The person record is assembled: the name, the email address with its category, the phone number with its category, and the address taken from the Customer's primary billing address.
The person is created or updated in Copper CRM, and any mapped custom field values are written.
For a delete, the linked Copper CRM person is removed rather than updated.
Mappings
Add/Update Copper Person FROM iPaaS.com
Description. Writes the iPaaS.com Customer into Copper CRM as a person, including its single address, email address and phone number.
This collection has no mapping filter, so all Customer records dispatched through outbound data flows or Manual Sync are processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Copper CRM) | Description |
Static |
| EmailCategory | Required. Copper CRM requires a category on every email address held against a person. Set to work by default; may be changed to another Copper CRM email category but must not be empty. |
Static |
| PhoneNumberCategory | Required. Copper CRM requires a category on every phone number held against a person. Set to work by default; may be changed but must not be empty. |
Field | FirstName | FirstName | Recommended. Copper CRM identifies people by name, so a person created without one is hard to find. |
Field | LastName | LastName | Recommended. Together with the first name it forms the display name in Copper CRM. |
Field | EmailAddress | Recommended. Combined with EmailCategory to build the single email entry. Also drives duplicate prevention and is how transferred transactions are attached to the right person. | |
Dynamic Formula |
| Number | Recommended. The phone number held on the first address flagged as primary billing. Combined with PhoneNumberCategory to build the single phone entry. |
Dynamic Formula |
| Street | Recommended. The street line from the primary billing address. |
Dynamic Formula |
| City | Recommended. The city from the primary billing address. |
Dynamic Formula |
| State | Recommended. iPaaS.com labels this Region; Copper CRM labels it State. |
Dynamic Formula |
| Postal_code | Recommended. The postal or ZIP code from the primary billing address. |
Dynamic Formula |
| Country | Recommended. The country from the primary billing address, stored as free text in Copper CRM. |
Field | Company | CompanyName | Recommended where the person belongs to a company. Also the value used to find the matching Copper CRM company. |
Dynamic Formula |
| CompanyId | Recommended. Looks up the Copper CRM company whose name matches the customer's company name exactly, ignoring capitalisation, and links the person to it. Where no match exists, no link is set and no error is raised. |
Field | Interested Sports (custom field) | Favourite Sports (custom field) | Optional. Writes an iPaaS.com custom field value into a Copper CRM person custom field. Placeholder value — replace during implementation: Interested Sports and Favourite Sports are example custom fields; substitute your own names or remove the mapping. |
Error Handling
Errors raised during these transfers appear under Dashboard → Integration Monitoring → Error Logs. The most common causes are:
An email or phone category is empty: Copper CRM rejects an email address or phone number saved without a category, so both category mappings must resolve to a value.
Copper CRM is unavailable or rejects the request: including when the 180 requests per minute limit is exceeded. The transfer fails and can be retried by dispatching a new change or using Manual Sync.
Note that a company name with no match in Copper CRM is not an error — the person is created without a company link and the transfer succeeds.
For the full catalogue of subscriber-visible messages, see the Copper CRM Error Messages article.
Testing & Validation
Test Scenarios
Create a Customer in iPaaS.com with a name, email address and a primary billing address, then transfer it and verify a Copper CRM person is created with all values populated.
Update the Customer's name and verify the change reaches the existing Copper CRM person rather than creating a second one.
Transfer a Customer whose email address matches an existing Copper CRM person and verify the records are linked rather than duplicated.
Transfer a Customer whose company name matches an existing Copper CRM company and verify the person is attached to it.
Transfer a Customer whose company name has no match and verify the person is created without a company and no error is raised.
Transfer a Customer with no primary billing address and verify the person is created without address values.
Populate a mapped iPaaS.com custom field and confirm the value reaches the matching Copper CRM custom field.
Delete a linked Customer and confirm the person is removed from Copper CRM.
Validation Checklist
Copper CRM API Key and API Email are entered on the subscription.
The relevant iPaaS.com Customer events are enabled under Outbound Data Flows.
Custom fields exist on both sides with identical names.
The example custom field mapping has been replaced or removed.
Companies referenced by customer records exist in Copper CRM.
The email and phone category mappings are populated.
Throttle and concurrency values are set so the integration stays within Copper CRM's request limit.
Additional Notes
Only one address, one email address and one phone number are written per person, because Copper CRM holds only one of each. Customers carrying several addresses or contact points do not have the extra entries written.
The integration attaches people to existing Copper CRM companies but does not create companies.