Summary
iPaaS.com customers can be transferred from Chargebee customers (billing accounts) through Chargebee webhooks, a scheduled poll or Manual Sync, using the Add/Update Chargebee Customer TO iPaaS.com mapping collection. Each transfer adds the customer the first time and updates the same iPaaS.com customer afterwards, carrying its name, email and company plus its billing status in four Chargebee custom fields. The customer's Chargebee billing address travels with it through the child collection Add/Update Chargebee Customer Billing Address TO iPaaS.com, where it becomes the customer's primary billing address.
ID Format
Manual Sync ID Format
Enter the Chargebee customer Id on the iPaaS.com Manual Sync page. This is the id shown on the customer's page in Chargebee: the id entered when the customer was created, or the id Chargebee generated when none was given (up to 50 characters), for example acme-1001 for a customer created with that id. The customer and its billing address are transferred together. A billing address cannot be sent on its own.
External ID Format
After a successful transfer, iPaaS.com saves the Chargebee customer Id as the customer's external ID on a dedicated external-ID record. That record is the primary match: every later transfer of the same Chargebee customer updates the same iPaaS.com customer. On a new customer, the default template also writes the Chargebee Id into CustomerNumber. This gives visibility of the Chargebee id on the iPaaS.com customer and serves as a fallback match when no external-ID record exists yet. Remapping CustomerNumber to a different source is supported, but it disables that fallback for customers that already exist in iPaaS.com.
The billing address is saved with its own external ID: the Chargebee customer Id followed by |billing. Each later transfer of the customer updates the same iPaaS.com address.
Deleted Record Support
The integration never deletes an iPaaS.com customer. When a customer is deleted in Chargebee and the customer_deleted scope is Active, the transfer depends on whether the customer is already linked to an iPaaS.com customer:
Linked customer: the iPaaS.com customer is kept. Its Chargebee Subscription Status becomes deleted, Chargebee Active Subscriptions and Chargebee Monthly Recurring Revenue become 0, and Chargebee Next Billing Date is cleared.
Customer never sent to iPaaS.com: normally nothing is sent and no error is raised.
Manual Sync right after a deletion
Chargebee states that deleting a customer "schedules the customer resource for deletion, and it is permanently deleted after a few minutes" (Chargebee: Delete a customer). For a short time after the deletion, Chargebee can still return the customer as if it were not deleted. The customer_deleted webhook is handled as described above. A transfer that reads the customer by its Chargebee id in that short time, for example a Manual Sync run right after the customer was deleted, treats it as not deleted:
A customer never sent to iPaaS.com is created in iPaaS.com. The new iPaaS.com customer carries the deleted customer's name, email, company and billing address, and it is linked to the deleted Chargebee customer. Its billing status is not marked deleted.
A linked customer can read none instead of deleted. Its billing status is written as none, with no active subscriptions, rather than deleted.
The transfer completes without an error. Wait a few minutes after deleting a customer in Chargebee before running a Manual Sync for it. If it happens, delete or deactivate in iPaaS.com the customer created for the deleted Chargebee customer, and treat a linked customer whose Chargebee customer was deleted as deleted even when its Chargebee Subscription Status reads none. Scheduled polls never send deleted customers: Chargebee leaves deleted customers out of its customer list.
Deletes FROM iPaaS.com to Chargebee are not supported: a Chargebee customer's invoices and subscriptions depend on it. A delete attempted through the Customer FROM iPaaS.com collection stops with CHGB-BIZL-1005.
Custom Field Support
Chargebee custom fields on the customer travel with each transfer under their Chargebee API names, which begin with cf_ (for example, cf_account_manager). No default mapping reads them. To bring one into iPaaS.com, subscribers or their MiSP add a Dynamic Formula mapping to Add/Update Chargebee Customer TO iPaaS.com that returns the Chargebee custom field by its API name, for example return cf_account_manager;, with an iPaaS.com custom field as the destination (add one from the mapping editor with + Add Custom Field). Chargebee API names are case-sensitive, so use the name exactly as Chargebee shows it under Settings > Configure Chargebee > Custom Fields (Chargebee: Custom fields). A customer with no value in that Chargebee custom field arrives with no value for it. Subscribers should validate a new custom field mapping in a staging environment before relying on it in production.
The billing address collection does not carry Chargebee custom fields.
The default mappings write four Customer custom fields that carry the customer's billing status: Chargebee Subscription Status, Chargebee Next Billing Date, Chargebee Monthly Recurring Revenue and Chargebee Active Subscriptions. Their values are described in the field mapping table below.
Mapping Collection Status
Status: Enabled
Trigger Events: Chargebee customer and subscription webhooks set Active in the subscription configuration's Inbound Data Flows section, a scheduled customer_poll event, Manual Sync, and an invoice or credit note whose customer is not in iPaaS.com yet. No automatic transfers occur until the scopes are set Active or the poll event is added.
Trigger | What it does |
customer_created, customer_changed | Sends the customer and its billing address when it is created or changed in Chargebee. |
subscription_created, subscription_activated, subscription_changed, subscription_cancelled, subscription_reactivated, subscription_renewed, subscription_paused, subscription_resumed | Sends the subscription's customer again, so its billing status stays current. |
customer_deleted | Updates a linked customer's billing status to deleted (see Deleted Record Support). |
customer_poll (scheduled poll) | Reads the Chargebee customers whose own record changed since the last poll, so a customer whose webhook was missed still arrives. The first poll looks back the number of days in the Initial Poll Days setting (7 when blank). |
Manual Sync | Sends the Chargebee customer whose Id is entered. |
Invoice or credit note | An invoice or credit note sent TO iPaaS.com sends its customer first when the customer is not in iPaaS.com yet. |
Whether a transfer adds or updates the iPaaS.com customer depends on whether the Chargebee customer is already linked to one, not on which trigger fired.
Duplicate or Conflicting Mappings
The following mapping collections operate on the same customers in the opposite direction:
Add/Update Chargebee Customer FROM iPaaS.com: creates or updates Chargebee customers from iPaaS.com customers.
Add/Update Chargebee Customer Billing Address FROM iPaaS.com: writes the iPaaS.com customer's primary billing address to the Chargebee customer's billing address.
Before enabling these collections alongside the FROM iPaaS.com collections, review the filters and Add/Update settings of both directions and decide which system is the source of truth for each customer field. With both directions active, a change written to Chargebee comes back TO iPaaS.com through the customer_changed scope. If another system also sends customers TO iPaaS.com, remove the fields Chargebee owns (name, email, billing address and the four Chargebee custom fields) from that system's update mappings, or the two systems overwrite each other.
Customer Matching by Email
Collision handling is not configurable on these collections. Instead, before a Chargebee customer that is not yet linked is mapped, the integration looks for an iPaaS.com customer with the same email address. The comparison ignores letter case.
Exactly one match: the Chargebee customer is linked to that iPaaS.com customer, which is then updated rather than duplicated. The CustomerNumber, Company and Comment formulas keep that customer's number, comment and, when Chargebee has none, its company.
Several iPaaS.com customers have the email: the transfer stops with CHGB-BIZL-1002. iPaaS.com refuses a second customer with an identical email, but it accepts emails that differ only in letter case (for example Jane@example.com and jane@example.com), and the integration counts those as the same email. Merge the duplicate iPaaS.com customers, then send the Chargebee customer again.
The match is already linked to a different Chargebee customer: the transfer stops with CHGB-BIZL-1006. Chargebee allows several customers to share one email; give one of the two Chargebee customers a different email, or merge them in Chargebee.
No match: a new iPaaS.com customer is added.
Once a Chargebee customer is linked, later transfers use the link and do not search by email again. Linking by email links the customer only, not its addresses; see the email-linked billing address caveat under System Caveats.
Unmapped Field Overwrite Risk
Warning — Unmapped Field Overwrite Risk: The iPaaS.com API replaces the whole customer record when it updates a customer, and the whole address when it updates an address, so any field these collections do not map is written empty on every update. In the default template, every customer field that can be overwritten is mapped; CustomerNumber, Company and Comment use DestinationValue formulas that write back the value iPaaS.com already holds, so a value set by another system is kept. Customer categories are not affected. The following address field is not mapped in the default template mappings for Add/Update Chargebee Customer Billing Address TO iPaaS.com, and an existing value in it on the iPaaS.com billing address is cleared each time an inbound transfer runs:
Type
If subscribers or their MiSP use the address Type in iPaaS.com, add a Dynamic Formula mapping to Type that carries the existing value forward, for example return DestinationValue != null ? DestinationValue.Type : null;. The same approach keeps any other field whose mapping is turned off or removed: an unmapped field is written empty on the next update, with no error. To stop Chargebee from owning a customer field, replace its mapping with a formula that keeps the iPaaS.com value instead of removing it. For example, to keep the iPaaS.com first name, map FirstName from return DestinationValue != null ? DestinationValue.FirstName : FirstName;, which keeps the existing first name and uses Chargebee's only for a new customer.
Supported Child Collections
Add/Update Chargebee Customer Billing Address TO iPaaS.com: transfers the customer's Chargebee billing address as the iPaaS.com customer's primary billing address. Chargebee keeps one billing address per customer. The address is linked by an external ID made of the Chargebee customer Id followed by |billing, and it is transferred only as part of the parent collection's transfer, never on its own.
System Caveats
Chargebee Caveats
Several customers can share an email: Chargebee notes that duplicate customer records "can still be created via API" (Chargebee: preventing multiple users with the same email). Two Chargebee customers with the same email cannot both be linked to one iPaaS.com customer; the second stops with CHGB-BIZL-1006.
Webhook endpoint limit: Chargebee states "You can create up to five webhook endpoints per site" (Chargebee: Webhook endpoints), and the integration uses one for each iPaaS.com subscription. If all five are taken, setting the first scope Active fails with CHGB-EXTN-1004. Remove an endpoint the site no longer uses in Chargebee, then set the scope Active again.
Rate limits: Chargebee limits how many API calls a site can make per minute (Chargebee: API rate limits). Each customer transfer reads the customer and its subscriptions. When the limit is reached, the transfer is rescheduled automatically and resumes after the limit resets; no action is required.
A brand-new subscription can be missed: Chargebee does not always list a subscription under its customer immediately after the subscription is created, and a customer transferred in that moment arrives without the new subscription in its billing status, with no error. When that subscription is the customer's only one, the customer reads Chargebee Subscription Status none, Chargebee Active Subscriptions 0, Chargebee Monthly Recurring Revenue 0 and no Chargebee Next Billing Date; a customer that already holds other subscriptions shows those, but not the new one. This is most likely on the subscription_created webhook, which arrives within seconds of the subscription being created. The next transfer of the customer after Chargebee lists the subscription, such as a later customer or subscription webhook for that customer or a Manual Sync, writes the correct values. Other systems that act on the billing status FROM iPaaS.com should allow for this.
Monthly recurring revenue catches up: Chargebee notes that a subscription's monthly recurring revenue "catches up with changes to the subscription in less than a minute" (Chargebee: Subscription object).
Deleted customers are still returned for a short time: a Manual Sync run right after a deletion treats the customer as not deleted; see Manual Sync right after a deletion under Deleted Record Support.
One billing address per customer: Chargebee stores a single billing address on each customer; its shipping addresses are not part of these collections. A customer with no billing address sends no address, and the customer still transfers.
Country and state codes: Chargebee stores the country as a two-letter ISO 3166-1 alpha-2 code (for example US), and Country arrives in iPaaS.com as that code. Chargebee supports state codes for the USA, Canada, India and the UAE only (Chargebee: Customer object); for an address in any other country, Region can arrive empty (see the Region row below).
iPaaS.com Caveats
Required customer fields: iPaaS.com requires a customer number, an email address, and at least one of first name, last name or company on every customer. The mapping filter sends only customers with an email, and CustomerNumber is always filled. A Chargebee customer that has an email but no first name, last name or company is refused by iPaaS.com with VALD-1039 - Company, First Name, or Last Name must not be null or empty. The transfer is retried and keeps failing until the customer has a name or company. Add a first name, last name or company to the customer in Chargebee, then send it again. Subscribers or their MiSP who hold such customers can also extend the mapping filter to skip them, as described under Mapping Filter below.
One customer per email: iPaaS.com refuses a second customer with an identical email address. A Chargebee customer whose email is shared by several iPaaS.com customers (for example, emails that differ only in letter case) cannot be linked until the iPaaS.com duplicates are merged (CHGB-BIZL-1002).
Billing-status custom fields: the default mappings write the four Chargebee Customer custom fields. Before the first transfer, subscribers or their MiSP should confirm that each appears on the parent collection's mappings in their iPaaS.com company.
The parent must transfer: the billing address reaches iPaaS.com only when its customer does. A customer skipped by the mapping filter, or refused by iPaaS.com, sends no billing address.
Downstream country names: if a system that receives customers FROM iPaaS.com expects full country names, translate the country in that system's FROM iPaaS.com mapping collection.
Integration-Specific Caveats
Email-linked customer gets a second primary billing address: when a Chargebee customer is linked by email to an iPaaS.com customer that already has a primary billing address, the Chargebee billing address is added as a new address marked as the primary billing address; it is not matched to the existing one. The customer then has two primary billing addresses, and later transfers update only the Chargebee one. Subscribers or their MiSP should review such customers' addresses in iPaaS.com and clear the primary billing flag on the address that should no longer be primary. A FROM iPaaS.com collection that sends the primary billing address back to Chargebee can otherwise pick up either address. To keep an identical address from being added again, subscribers or their MiSP can map a Static value of true to PreventDuplicate on Add/Update Chargebee Customer Billing Address TO iPaaS.com: iPaaS.com then skips a new address that matches an existing address in every mapped field, including the primary billing and primary shipping flags. Because a new Chargebee address is not marked as the primary shipping address, an existing address that is also the primary shipping address is never treated as a match. An address that differs in any field is still added, so the review above still applies.
Billing status is worked out from all subscriptions: the four Chargebee custom fields reflect every subscription the customer holds at the time of the transfer, not only one.
Billing status needs the subscription scopes: each poll reads customers whose own Chargebee record changed. A change to a customer's subscriptions reaches iPaaS.com through the subscription scopes; if those are inactive, the billing status is refreshed only when the customer itself changes or is sent by Manual Sync.
Setup Requirements
The integration-wide setup (API key, Chargebee Site and the subscription settings) is in the Chargebee Installation Instructions and is not repeated here.
Chargebee Configuration
A free webhook endpoint slot: when the first scope is set Active, the integration registers a webhook endpoint in Chargebee named "iPaaS.com subscription" followed by the subscription number, and it adds or removes events on that endpoint as scopes are set Active or inactive. No other setup is needed in Chargebee.
Custom field API names: to map a Chargebee custom field, note its API name under Settings > Configure Chargebee > Custom Fields.
iPaaS.com Configuration
Inbound Data Flows: set the customer and subscription scopes listed under Mapping Collection Status to Active.
Scheduled poll: add a scheduled event of the type Webhook (Poll Request) for this subscription with the customer_poll scope (see Events). No polls run until the event is added.
Billing-status custom fields: confirm the four Chargebee Customer custom fields appear on the parent collection's mappings.
Integration Flow
When a webhook arrives, a poll finds a changed customer, a Manual Sync is started, or an invoice or credit note needs its customer, the integration processes the customer in this order:
Read the customer from Chargebee. The integration reads the customer by its Chargebee Id. When Chargebee no longer returns it because it was deleted, the integration reads the deleted record: a customer never linked to iPaaS.com is not sent, and a linked customer continues with its billing status set to deleted (step 2 is skipped). A customer that Chargebee still returns shortly after its deletion is processed as a live customer (see Deleted Record Support).
Work out the billing status. The integration reads the customer's Chargebee subscriptions and sets Chargebee Subscription Status, Chargebee Active Subscriptions, Chargebee Next Billing Date and Chargebee Monthly Recurring Revenue from all of them.
Apply the mapping filter. A customer without an email is skipped, without an error.
Link by email when not yet linked. When the Chargebee customer has no iPaaS.com link, the integration looks for an iPaaS.com customer with the same email and links to it, stops with CHGB-BIZL-1002 or CHGB-BIZL-1006, or continues to add a new customer (see Customer Matching by Email).
Map the customer. The parent collection's mappings build the iPaaS.com customer, including the four billing-status custom fields.
Map the billing address. The child collection maps the Chargebee billing address, when the customer has one, as the customer's primary billing address with the external ID Chargebee customer Id followed by |billing.
Add or update the iPaaS.com customer. A linked customer is updated; otherwise a new customer is added. iPaaS.com saves the Chargebee customer Id as the customer's external ID, and the billing address external ID on its address. If iPaaS.com refuses the customer (for example, no name or company), the error appears in Dashboard / Integration Monitoring / Error Logs and the transfer is retried.
Mappings
Add/Update Chargebee Customer TO iPaaS.com
iPaaS.com data type: Customer
Description: Adds or updates one iPaaS.com customer per Chargebee customer, with its name, email, company and four billing-status custom fields.
Mapping Filter
// Customers with an email: iPaaS.com needs one on every customer return !string.IsNullOrEmpty(Email);
Filter Description: The template's filter passes only Chargebee customers whose Email has a value. A Chargebee customer with no email is skipped without an error, because iPaaS.com requires an email address on every customer. To bring such a customer into iPaaS.com, add an email to it in Chargebee; the next webhook or poll then sends it. The filter does not check names: a customer with an email but no first name, last name or company passes the filter and is then refused by iPaaS.com (see iPaaS.com Caveats). Subscribers or their MiSP may adapt this filter to their own data, for example by also requiring a first name, last name or company, and should validate a changed filter in a staging environment before relying on it in production.
Field Mapping Table
Mapping Type | Source Field (Chargebee) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| CustomerNumber | Required. Writes the Chargebee customer Id on a new customer, or on an existing iPaaS.com customer that has no number; an existing number is kept, including on a customer linked by email that another system created. Also the fallback match described under External ID Format. |
Field | FirstName | FirstName | Recommended. The customer's first name in Chargebee (up to 150 characters), replaced on every update. iPaaS.com requires at least one of FirstName, LastName or Company. |
Field | LastName | LastName | Recommended. The customer's last name in Chargebee (up to 150 characters), replaced on every update. iPaaS.com requires at least one of FirstName, LastName or Company. |
Field | EmailAddress | Required. The customer's email in Chargebee; the mapping filter sends only customers that have one. The email is also how a Chargebee customer is linked to an existing iPaaS.com customer (see Customer Matching by Email). | |
Dynamic Formula |
| Company | Recommended. Writes the Chargebee company (up to 250 characters). When Chargebee has none, an existing iPaaS.com company is kept, and a new customer gets an empty company. Keep it mapped as shipped. |
Dynamic Formula |
| Comment | Optional. Chargebee has no customer comment, so the comment iPaaS.com already holds is written back; a new customer gets none. Keep it mapped as shipped, or replace it with a Chargebee source field. |
Field | SubscriptionStatus | Chargebee Subscription Status (Custom Field) | Optional. One billing status from all of the customer's subscriptions (deleted subscriptions ignored); the most active state wins, in the order active, in_trial, non_renewing, paused, future, cancelled. none for a customer with no subscriptions, deleted for a linked customer deleted in Chargebee, and transferred when every subscription was moved to another business entity. Can miss a subscription created moments before the transfer (see Chargebee Caveats). |
Field | NextBillingAt | Chargebee Next Billing Date (Custom Field) | Optional. The earliest next billing date and time across the customer's live subscriptions (active, in_trial or non_renewing), stored in UTC in ISO 8601 format, for example 2026-12-01T00:00:00.0000000+00:00. Empty with no live subscription or for a deleted customer. |
Field | MonthlyRecurringRevenue | Chargebee Monthly Recurring Revenue (Custom Field) | Optional. The sum of Chargebee's monthly recurring revenue for the live subscriptions, as an amount in the subscriptions' currency, for example 49.99. 0 with no live subscription or for a deleted customer; empty when the live subscriptions use more than one currency. |
Field | ActiveSubscriptionCount | Chargebee Active Subscriptions (Custom Field) | Optional. How many of the customer's subscriptions are active, in_trial or non_renewing. 0 with none, or for a deleted customer. |
Add/Update Chargebee Customer Billing Address TO iPaaS.com (Child)
iPaaS.com data type: Customer Address
Description: Transfers the Chargebee customer's billing address as the iPaaS.com customer's primary billing address, as part of each transfer of its parent customer. This collection has no mapping filter.
Field Mapping Table
Mapping Type | Source Field (Chargebee) | Destination Field (iPaaS.com) | Description |
Field | FirstName | FirstName | Optional. First name of the billing contact (up to 150 characters); can differ from the customer's own first name. |
Field | LastName | LastName | Optional. Last name of the billing contact (up to 150 characters); can differ from the customer's own last name. |
Field | Company | Company | Optional. Company on the billing address (up to 250 characters); can differ from the customer's company. |
Field | Line1 | Address1 | Recommended. Line 1 of the billing address (up to 150 characters). |
Field | Line2 | Address2 | Optional. Line 2 of the billing address (up to 150 characters); empty when Chargebee has none. |
Field | Line3 | Address3 | Optional. Line 3 of the billing address (up to 150 characters); empty when Chargebee has none. |
Field | City | City | Recommended. City of the billing address (up to 50 characters). |
Field | StateCode | Region | Recommended. Chargebee's ISO 3166-2 state or province code without the country prefix, for example AZ for Arizona. Chargebee supports state codes for the USA, Canada, India and the UAE only, so Region can arrive empty for other countries; subscribers or their MiSP can change the source to the Chargebee State field, which holds the state or province name, and validate the result in a staging environment. |
Field | Country | Country | Recommended. The two-letter ISO 3166-1 alpha-2 country code, for example US or GB; not translated to a country name. |
Field | Zip | PostalCode | Recommended. Zip or postal code of the billing address (up to 20 characters). |
Static |
| IsPrimaryBilling | Recommended. Marks the address as the customer's primary billing address. A fixed value by design: the Customer Billing Address FROM iPaaS.com collection sends only the primary billing address back to Chargebee, so keep it as true. |
Dynamic Formula |
| IsPrimaryShipping | Recommended. Chargebee does not say whether the billing address is also the shipping address, so the flag iPaaS.com already holds is kept; a new address is not marked as the primary shipping address. Keep it mapped as shipped. |
Field | Phone | PhoneNumber | Optional. Phone number on the billing address (up to 50 characters); the customer's own phone is not mapped. |
Error Handling
Errors from these collections appear in Dashboard / Integration Monitoring / Error Logs. iPaaS.com retries a failed transfer automatically while its error is active; dismissing an active error stops its retry, but an error already showing Retry Pending is reprocessed anyway. Fix the cause so a retry can succeed. The Chargebee Error Messages article lists every code with its fix. The errors subscribers see most on this flow:
"CHGB-BIZL-1002 - … iPaaS.com customers have the email …, so Chargebee customer … can't be linked to one.": several iPaaS.com customers share the Chargebee customer's email, including emails that differ only in letter case. Merge the iPaaS.com customers, then send the Chargebee customer again.
"CHGB-BIZL-1006 - iPaaS.com customer … has the email … and is already linked to Chargebee customer …": two Chargebee customers share one email. Give one of them a different email, or merge them in Chargebee.
"VALD-1039 - Company, First Name, or Last Name must not be null or empty": iPaaS.com refused a customer that has no first name, last name or company. Add one to the customer in Chargebee, then send it again. An invoice or credit note whose customer is refused this way shows the same error.
CHGB-EXTN-1004 (webhook endpoint limit reached): raised when a scope is set Active and the Chargebee site already has five webhook endpoints. Remove an unused endpoint in Chargebee, then set the scope Active again.
Rate limit reached: no error is shown; the transfer is rescheduled automatically and resumes after Chargebee's per-minute limit resets.
A customer skipped by the mapping filter, a deleted customer that was never linked, and the billing-status values described under Chargebee Caveats produce no error.
Testing & Validation
Test Scenarios
Create a Chargebee customer with a first name, last name, email and billing address, and verify one iPaaS.com customer is created, linked to the Chargebee customer Id, with its primary billing address and the four billing-status custom fields.
Change the customer's last name in Chargebee and verify the same iPaaS.com customer is updated, with no second customer, and that its customer number and comment are unchanged.
Add a subscription to the customer in Chargebee and verify the billing-status custom fields update, including a Chargebee Next Billing Date in UTC. If the status reads none, the subscription was not yet listed when the customer was sent (see Chargebee Caveats); verify the values after the customer's next transfer.
Create a Chargebee customer with no email and verify it is not sent and no error is raised; create one with an email but no name or company and verify the VALD-1039 refusal in Dashboard / Integration Monitoring / Error Logs.
Create an iPaaS.com customer, then a Chargebee customer with the same email, and verify the two are linked rather than duplicated; review the customer's primary billing addresses.
Delete a linked customer in Chargebee and verify the iPaaS.com customer is kept and reads deleted. If it reads none, the customer was sent again by Manual Sync right after the deletion (see Manual Sync right after a deletion under Deleted Record Support).
Send a customer by Manual Sync using its Chargebee customer Id and verify the customer and its billing address transfer.
Validation Checklist
The customer and subscription scopes are Active under Inbound Data Flows, and a customer_poll event is scheduled.
The four Chargebee Customer custom fields appear on the parent collection's mappings.
The mapping filter matches how the subscriber's Chargebee customers are filled in (email, and a name or company).
Filters and Add/Update settings on the FROM iPaaS.com customer collections are set so the two directions do not overwrite each other.
Every mapping is kept on, or replaced with a formula that keeps the iPaaS.com value, so no field is cleared on update.
Additional Notes
Out of Scope
Deleting iPaaS.com customers: a Chargebee deletion only marks the billing status as deleted.
Customer categories: these collections do not set iPaaS.com customer categories.
Chargebee shipping addresses and the customer's own phone number are not mapped.
Initialization: these collections have no initialization run. Existing Chargebee customers arrive through the first poll (within Initial Poll Days), through webhooks as they change, or by Manual Sync. For a large history, use bulk sync using Postman.
Several Currencies
Chargebee Monthly Recurring Revenue is empty for a customer whose live subscriptions are billed in more than one currency, because those amounts cannot be added together.
Related Documents
Related Mapping Documentation