Summary
A Salesforce Account is transferred to an iPaaS.com Company through the Add/Update Salesforce Account TO iPaaS.com mapping collection. When an Account is created or updated in Salesforce, a corresponding Company is created or updated in iPaaS.com, and the Account's billing and shipping address details flow to the Company through the child address collection. Change capture is schedule based: the integration polls Salesforce for new and changed Accounts rather than receiving real-time notifications.
ID Format
Manual Sync ID Format
When syncing an Account on demand from the Manual Sync page, enter the Salesforce Account record Id. Salesforce object Ids are 15 or 18 character alphanumeric values.
Example: 001Ux00000ABcdEFGH
External ID Format
After an Account syncs successfully, the integration stores the Salesforce Account Id as the external reference on the resulting iPaaS.com Company. Salesforce object Ids are 15 or 18 character alphanumeric values, for example 001Ux00000ABcdEFGH. This saved reference is what the integration uses to match the same Account on later updates so that an existing Company is updated rather than duplicated.
Deleted Record Support
Record deletion is not synced. Deleting an Account in Salesforce does not delete the corresponding Company in iPaaS.com, and no delete mappings are included in the default templates. To remove a Company, subscribers or their MiSP should manage that record directly in iPaaS.com.
Custom Field Support
Salesforce Account custom fields can be mapped to iPaaS.com Company custom fields. The collection ships with one custom field example, Active, to demonstrate the pattern.
To map a custom field, create a matching custom field in iPaaS.com (under Data Management, Custom Fields), keeping the data type consistent with the Salesforce field, and create the corresponding field within the Subscription named to match the Salesforce API name. Once the field exists in both places, add the mapping.
Placeholder value — replace during implementation: the custom field example is for demonstration only. The actual custom fields to map depend on the implementation, so subscribers or their MiSP should replace the example with the fields relevant to their Salesforce org.
Mapping Collection Status
Status: Enabled
Trigger Events: Create, Update. An Account that is created or updated in Salesforce is picked up on the next poll cycle and synced to iPaaS.com.
Duplicate or Conflicting Mappings
This is the only active mapping for syncing Salesforce Accounts to iPaaS.com. Additional mappings may be needed to preserve other iPaaS.com Company field values, such as Email Address or Tax Id Number; the source values for those are specific to each implementation. The same applies to the address mappings.
Collision Handling
When an Account is created in iPaaS.com and a matching Company already exists, the outcome depends on whether a collision-handling method is selected on the mapping collection in the iPaaS.com mapping UI. When a method is selected, the integration can link to the existing Company instead of creating a duplicate. When no method is selected, the integration surfaces a duplicate error rather than guessing. See the Salesforce Error Messages article for the duplicate-detected condition and its resolution.
Supported Child Collections
This is a parent-level mapping collection. It has one child collection:
Add/Update Salesforce Account Address TO iPaaS.com: syncs the Account's billing and shipping address details to the address on the associated iPaaS.com Company.
System Caveats
iPaaS.com Caveats
A Company in iPaaS.com requires a Name. Every Account that syncs must have its Name populated in Salesforce, otherwise the Company cannot be created. The address fields and all other Company fields have no required values at the destination.
Salesforce Caveats
Address details are stored on the parent Salesforce Account (its Billing and Shipping address fields). There are no separate Salesforce address records; the address child collection moves those parent fields.
Integration-Specific Caveats
Change capture is poll based, not real-time. The poll look-back is configurable through the Account Poll Days setting (default 7 days), which controls how far back the integration looks on the initial poll. Because capture is scheduled, a newly created or updated Account appears in iPaaS.com after the next poll rather than instantly. For large volumes, subscribers or their MiSP should stagger bulk changes so a single poll cycle is not overloaded.
Integration Flow
The integration polls Salesforce for Accounts created or changed within the configured look-back window.
For each Account, the integration checks whether a matching Company already exists in iPaaS.com using the saved external reference.
If no matching Company exists, a new Company is created from the mapped Account fields; the Account Name is required for this step.
If a matching Company exists, the Company is updated with the mapped Account fields.
The Account's billing and shipping address fields are synced to the address on the associated Company through the child collection.
The Salesforce Account Id is saved as the external reference on the Company so future updates match the same record.
Mappings
Add/Update Salesforce Account TO iPaaS.com
This collection maps Salesforce Account fields to the iPaaS.com Company.
Mapping Type | Source Field (Salesforce) | Destination Field (iPaaS.com) | Required / Recommended / Optional | Description |
Field | Name | Name | Required | Maps the Salesforce Account Name to the Name field on the iPaaS.com Company. This is the only required field to create a Company, so every Account that syncs must have a name populated in Salesforce. The name is carried across exactly as entered. |
Field | Description | Description | Optional | Maps the Salesforce Account Description to the Description field on the Company, carrying the free-text summary or notes. When the Account has no description, no value is sent and the Company description is left unchanged. |
Field | Phone | PhoneNumber | Optional | Maps the Salesforce Account Phone number to the PhoneNumber field on the Company. The value is carried across exactly as entered, so subscribers or their MiSP should keep the phone number formatted consistently. An empty phone number leaves the Company value unchanged. |
Field | Fax | FaxNumber | Optional | Maps the Salesforce Account Fax number to the FaxNumber field on the Company. The value is carried across exactly as entered. An empty fax number leaves the Company value unchanged. |
Field | Website | Url | Optional | Maps the Salesforce Account Website to the Url field on the Company. When the Account has no website, no value is sent and the Company value is left unchanged. |
Field | Account Number | AccountNumber | Optional | Maps the Salesforce Account Account Number to the AccountNumber field on the Company. When the Account has no account number, no value is sent and the Company value is left unchanged. |
Field | Parent Account | ParentCompanyId | Optional | Maps the Salesforce Account Parent Account to the ParentCompanyId field on the Company, linking the Company to its parent Company in iPaaS.com. For the link to resolve, the parent Account must already have synced to iPaaS.com as a Company. Applies only to Accounts that have a parent Account in Salesforce. |
Field | Active (custom field) | Active | Optional | Maps the value of the Salesforce custom field Active to the corresponding Company custom field. This is an implementation-specific example of custom-field mapping — see Custom Field Support. |
Placeholder value — replace during implementation: the Active row is a custom-field example only; replace it with the custom fields relevant to the implementation.
Add/Update Salesforce Account Address TO iPaaS.com
This child collection maps the Salesforce Account's billing and shipping address details to the address on the associated iPaaS.com Company. The address fields are stored on the parent Salesforce Account and flow to iPaaS.com together with the rest of the Account address.
Mapping Type | Source Field (Salesforce) | Destination Field (iPaaS.com) | Required / Recommended / Optional | Description |
Field | Street | Address1 | Optional | Maps the Salesforce Account Street to the Address1 line of the address on the Company. An empty street leaves the corresponding value on the Company unchanged. |
Field | City | City | Optional | Maps the Salesforce Account City to the City field of the address on the Company. An empty city leaves the corresponding value unchanged. |
Field | State | Region | Optional | Maps the Salesforce Account State to the Region field of the address on the Company. The value is carried across as entered, so subscribers or their MiSP should keep state or region values consistent. An empty state leaves the corresponding value unchanged. |
Field | Postal Code | PostalCode | Optional | Maps the Salesforce Account Postal Code to the PostalCode field of the address on the Company. An empty postal code leaves the corresponding value unchanged. |
Field | Country | Country | Optional | Maps the Salesforce Account Country to the Country field of the address on the Company. The value is carried across as entered, so subscribers or their MiSP should keep country values consistent. An empty country leaves the corresponding value unchanged. |
Field | Default billing indicator | IsPrimaryBilling | Optional | When the address is the Account's default billing address in Salesforce, it is marked as the primary billing address in iPaaS.com. |
Field | Default shipping indicator | IsPrimaryShipping | Optional | When the address is the Account's default shipping address in Salesforce, it is marked as the primary shipping address in iPaaS.com. |
Error Handling
Errors raised while syncing an Account appear under Dashboard, Integration Monitoring, Error Logs. The conditions that most often affect this direction are documented in the companion Salesforce Error Messages article, which describes each message together with why it occurs and how to resolve it. Common conditions include:
A duplicate Account is detected on create with no collision-handling method selected. Resolution: select a collision-handling method on the mapping collection so the integration can link to the existing record, or resolve the duplicate in Salesforce.
A Salesforce API call fails. Resolution: review the error detail in the Error Logs and confirm the connection settings and Salesforce permissions, then re-run the sync.
Testing & Validation
Test Scenarios
Create a new Account in Salesforce with a populated Name and confirm a corresponding Company is created in iPaaS.com on the next poll cycle.
Update a mapped field (for example, Phone or Website) on an existing Account and confirm the change propagates to the Company.
Attempt to sync an Account with no Name and confirm the Company is not created and an appropriate error appears in the Error Logs.
Manually sync an Account using its Salesforce Account Id on the Manual Sync page and confirm it succeeds.
Populate the Account's billing and shipping address and confirm the address details and the primary billing and shipping flags appear on the Company.
Set a parent Account that has already synced, then confirm the parent Company link resolves on the child Company.
Validation Checklist
The Account Name appears on the Company.
Phone, fax, website, and account number values match between the Account and the Company.
Billing and shipping address fields and the primary flags match.
The parent Company link resolves when the parent Account has been synced.
No duplicate Company is created when the same Account syncs again.
Out of Scope
The following are not handled by this mapping collection, at the time this documentation was written:
Record deletion. Deleting an Account in Salesforce does not delete the Company in iPaaS.com.
Real-time capture. Change capture is poll based; there is no real-time push of Account changes.
Separate address records. Addresses are limited to the Account's Billing and Shipping fields on the parent record; there are no multiple, independent address records.
Custom-field assignment. The custom-field example is implementation-specific; the fields to map depend on each subscriber's Salesforce org and are configured during implementation.