Determining input schema

This page shows the steps you need to take to find the required input schema for any operation under any Service Connector.

Determining service field names

When you are mapping from one service to another, some investigation is required to tell you what these fields are.

So in a case where we are mapping customers from Stripe to Salesforce:

We can look at the debug output of the List customers operation for the Stripe connector to find that 'name', 'id', 'phone' and 'currency' are what is used by Stripe:

To determine the fields that need to be mapped to in Salesforce we inspect the output for the Create Record (Account) operation:

Note that Stripe_ID__c and Currency__c are custom fields added specifically for mapping from Stripe.

You can then use this to build the list for Service 2:

Input schema requirements

The first example on this page of mapping data to Airtable is very simple as the Airtable 'Create records' operation accepts data as a simple list of fields.

However some services, such as and , will only accept data as key / value pairs.

In this case you will need to add a second data mapper step which makes use of the 'Map objects to list' operation:

And the output from the second data mapper can then be used as the input for the fields when creating a record in Salesforce:

As is demonstrated by the debug output from Map key/value pairs:

Mapping nested data

The above example shows you how to deal with simple 'flat' data payloads.

However, it is likely that you will be receiving payloads of 'nested' data, where fields are contained within objects, such as the following:

In order to deal with this, when converting the Mapping to config in your Source Workflow using the Data Mapper 'Map objects' operation:

You can simply use dot notation to specify the object and the fields within:

These mappings can then be made available for your End Users in the Config Wizard

The following debug output shows this at work: