Summary
An iPaaS.com Company is written back to a Salesforce Account through the Add/Update Salesforce Account FROM iPaaS.com mapping collection. When a Company is created or updated in iPaaS.com, a corresponding Account is created or updated in Salesforce, and the Company's address details flow to the Account's billing or shipping address through the child address collection. Write-back updates are partial: fields that are not mapped, or that are sent empty, are left unchanged in Salesforce rather than cleared.
ID Format
Manual Sync ID Format
When syncing a Company on demand from the Manual Sync page, enter the iPaaS.com Company id.
Example: 123456
External ID Format
After a Company writes back successfully, the integration stores the resulting Salesforce Account Id as the reference on the iPaaS.com record. 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 Account is updated rather than duplicated.
Deleted Record Support
Record deletion is not synced. Deleting a Company in iPaaS.com does not delete the corresponding Account in Salesforce, and no delete mappings are included in the default templates. To remove an Account, subscribers or their MiSP should manage that record directly in Salesforce.
Custom Field Support
iPaaS.com Company custom fields can be written back to Salesforce Account custom fields. The collection ships with one custom field example, Active__c, 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. A Company that is created or updated in iPaaS.com is written back to Salesforce as a new or updated Account.
Duplicate or Conflicting Mappings
This is the only active mapping for syncing iPaaS.com Companies to Salesforce Accounts. Additional mappings may be needed to write back other field values, such as phone number, fax number, website, and account number; the destination fields are specific to each implementation.
Collision Handling
When an Account is created in Salesforce and Salesforce reports a matching record, 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 record 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 FROM iPaaS.com: writes the Company's address details to the associated Salesforce Account's billing or shipping address.
System Caveats
Salesforce Caveats
Salesforce requires an Account Name to create an Account, so the Name mapping should always supply a value when a new Account is being created. Address details are written to the parent Account's Billing or Shipping address; there are no separate Salesforce address records.
iPaaS.com Caveats
For all fields other than Account Name, subscribers should validate requiredness and field behavior in a staging environment before relying on the integration in production. The public Salesforce write surface does not document hard requirements for these fields beyond Account Name.
Integration-Specific Caveats
Write-back updates are partial: a field that is not mapped, or that is sent empty, is left unchanged in Salesforce rather than blanked. To deliberately clear or force a value on an existing Account, map the field and supply the value explicitly (for example, with a static or destination value) rather than relying on an empty value to clear it. Change capture is scheduled rather than real-time, controlled by the Account Poll Days look-back setting (default 7 days). For large volumes, subscribers or their MiSP should stagger bulk changes so a single cycle is not overloaded.
Integration Flow
A Company is created or updated in iPaaS.com.
The integration checks whether a matching Salesforce Account already exists using the saved reference.
If no matching Account exists, a new Account is created from the mapped Company fields; an Account Name is required for this step.
If a matching Account exists, the Account is updated with the mapped Company fields. The update is partial, so unmapped or empty fields are left unchanged.
The Company's address details are written to the associated Account's billing or shipping address through the child collection, based on the default-billing and default-shipping control flags.
The Salesforce Account Id is saved as the reference on the iPaaS.com record so future updates match the same Account.
Mappings
Add/Update Salesforce Account FROM iPaaS.com
This collection writes iPaaS.com Company fields back to the Salesforce Account.
Because Salesforce does not expose a public field-requiredness API, the requiredness shown below reflects how the integration ships the mapping; subscribers or their MiSP should validate field requirements and write-back behavior in a staging environment before relying on them in production.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Salesforce) | Required / Recommended / Optional | Description |
Field | Name | Account Name | Recommended | Maps the company name from the Company to the Account Name field on the Account. Salesforce requires an Account Name to create an Account, so this mapping should always supply a value on create. On updates the write-back is partial: an unmapped or empty value leaves the existing Account Name unchanged. Subscribers should validate this field's behavior in a staging environment before relying on it in production. |
Field | Description | Description | Optional | Maps the description from the Company to the Description field on the Account. The write-back is partial: an unmapped or empty value leaves the existing Description unchanged. Subscribers should validate this field's behavior in a staging environment before relying on it in production. |
Field | PhoneNumber | Phone | Optional | Maps the phone number from the Company to the Phone field on the Account. The write-back is partial: an unmapped or empty value leaves the existing Phone unchanged. Subscribers should validate this field's behavior in a staging environment before relying on it in production. |
Field | FaxNumber | Fax | Optional | Maps the fax number from the Company to the Fax field on the Account. The write-back is partial: an unmapped or empty value leaves the existing Fax unchanged. Subscribers should validate this field's behavior in a staging environment before relying on it in production. |
Field | Url | Website | Optional | Maps the URL from the Company to the Website field on the Account. The write-back is partial: an unmapped or empty value leaves the existing Website unchanged. Subscribers should validate this field's behavior in a staging environment before relying on it in production. |
Field | AccountNumber | Account Number | Optional | Maps the account number from the Company to the Account Number field on the Account. The write-back is partial: an unmapped or empty value leaves the existing Account Number unchanged. Subscribers should validate this field's behavior in a staging environment before relying on it in production. |
Field | ParentCompanyId | Parent Account | Optional | Maps the parent company reference from the Company to the Parent Account field on the Account, establishing the account hierarchy. The referenced parent Account must already exist in Salesforce for the link to resolve. The write-back is partial: an unmapped or empty value leaves the existing parent relationship unchanged. Subscribers should validate this field's behavior in a staging environment before relying on it in production. |
Field | Active (custom field) | Active__c | Optional | Maps the value of an iPaaS.com Company custom field to the Salesforce custom field. This is an implementation-specific example of custom-field mapping — see Custom Field Support. |
Placeholder value — replace during implementation: the Active__c row is a custom-field example only; replace it with the custom fields relevant to the implementation.
Add/Update Salesforce Account Address FROM iPaaS.com
This child collection writes the Company's address details to the associated Salesforce Account's billing or shipping address. The destination address (Billing or Shipping) is determined by the default-billing and default-shipping control flags on the address. All address write-backs are partial, and subscribers should validate field behavior in a staging environment before relying on it in production.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Salesforce) | Required / Recommended / Optional | Description |
Field | Address1 | Street | Optional | Maps the first address line from the Company address to the street portion of the associated Account address. The write-back is partial: an unmapped or empty value leaves the existing street unchanged. |
Field | City | City | Optional | Maps the city from the Company address to the city portion of the associated Account address. The write-back is partial: an unmapped or empty value leaves the existing city unchanged. |
Field | Region | State | Optional | Maps the region from the Company address to the state or province portion of the associated Account address. The write-back is partial: an unmapped or empty value leaves the existing state unchanged. |
Field | PostalCode | Postal Code | Optional | Maps the postal code from the Company address to the postal code portion of the associated Account address. The write-back is partial: an unmapped or empty value leaves the existing postal code unchanged. |
Field | Country | Country | Optional | Maps the country from the Company address to the country portion of the associated Account address. The write-back is partial: an unmapped or empty value leaves the existing country unchanged. |
Field | IsPrimaryBilling | IsDefaultBilling | Optional | IsDefaultBilling is a special integration control field, not a standard Salesforce data field. It determines which billing address is used when the address is written to Salesforce. |
Field | IsPrimaryShipping | IsDefaultShipping | Optional | IsDefaultShipping is a special integration control field, not a standard Salesforce data field. It determines which shipping address is used when the address is written to Salesforce. |
Error Handling
Errors raised while writing back 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:
An Account update is attempted with no Account Id. Resolution: confirm the Company has been linked to an existing Salesforce Account, or allow the create path to run so the reference is established.
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 Company in iPaaS.com with a populated Name and confirm a corresponding Account is created in Salesforce.
Update a mapped field (for example, Phone or Website) on an existing Company and confirm the change writes back to the Account.
Confirm partial write-back: send a Company update with a field unmapped or empty and verify the existing Salesforce value is left unchanged rather than cleared.
Attempt to create an Account with no Name and confirm the Account is not created and an appropriate error appears in the Error Logs.
Manually sync a Company using its iPaaS.com id on the Manual Sync page and confirm it succeeds.
Populate the Company's address and the primary billing and shipping flags, then confirm the address writes to the correct Salesforce billing or shipping address.
Validation Checklist
The Company name appears as the Account Name on the Account.
Phone, fax, website, and account number values write back as expected.
Unmapped or empty fields are left unchanged on the Account, not blanked.
Address fields write to the billing or shipping address selected by the control flags.
The parent Account link resolves when the referenced parent Account exists.
No duplicate Account is created when the same Company writes back again.
Out of Scope
The following are not handled by this mapping collection, at the time this documentation was written:
Record deletion. Deleting a Company in iPaaS.com does not delete the Account in Salesforce.
Field blanking on update. Write-back is partial; unmapped or empty values do not clear existing Salesforce values. To force a value, map the field and supply it explicitly.
Real-time capture. Change capture is poll based; there is no real-time push of Company 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.