Post-mapping transformations (partner-defined schema)

In this article, you will go through some common data transformation challenges that you might run into while building integrations.

For each example that follows:

  • We will be using dummy data which you might get from another service.

  • We will be showing possible pathways (Core connectors, JSONata, Javascript) for each example. You are free to take a different route as well.

Salesforce
Copy

1 - Preparing input for Salesforce update operation
Copy

We have the following dummy data:

Our Salesforce Connector's update operation expects the following input for the above data:

Please refer 'Determining Input schema' page which shows how to find out input and output data format for services.

You can import this project here. It contains three ways you could solve this:

2 - Preparing input for Salesforce create operation
Copy

We have the following dummy data:

Our Salesforce Connector's create operation expects the following input for the above data:

Please refer 'Determining Input schema' page which shows how to find out input and output data format for services.

You can import this project here. It contains three ways you could solve this:

Mailchimp
Copy

1 - Preparing input for Mailchimp batch subscribe operation
Copy

We have the following dummy data:

Our Mailchimp Connector's Raw HTTP operation to batch subscribe members expects the following input for the above data:

Please refer 'Determining Input schema' page which shows how to find out input and output data format for services.

You can import this project here. It contains three ways you could solve this: