account
object from Salesforce and the companies
object from HubSpot to a unified label like company
, your read action results will be delivered under the object name of company
. The original object name will still be available in the response’s rawObjectName
key.
If you wish to write data to company
, you can inherit the mapping from the read action.
Here’s an example of a Salesforce integration that maps the account
object to company
:
mobilephone
field to phone
. Read results will deliver the field under the phone
key, and when you make a call to the Write API, you can use phone
to update the original mobilePhone
field if the write action inherits the mapping.
notes
.
Example:
notes
field in your integration.field_a
, while User B uses field_b
.notes
, accommodating custom fields unique to each consumer.notes
field, if you inherit the mapping.requiredFields
or optionalFields
, you’ll specify:
notes
populated, and Ampersand will automatically strip it from the request before writing to the provider API to prevent errors.
For example: SampleApp is using Ampersand to integrate with their customer’s HubSpot. SampleApp needs to ask the customer to map their SampleApp fields to their HubSpot fields, and different customers can have different sets of fields in SampleApp.To achieve this, you can pass in the mapping configuration in the
fieldMapping
property of the InstallIntegration
component:
amp.yaml
):
amp.yaml
) and dynamically mapped fields (defined in the UI component) will be present in result.mappedFields
Priority
,
SampleApp has the values Very High
, High
, Medium
, Low
while HubSpot has the values
P1
, P2
, P3
, and P4
. SampleApp would like the user to map the correlation between the SampleApp values and HubSpot values.InstallIntegration
component like below: