Articles in this section

Configure results mapping

Results mapping adds the records a lookup step returns to the source record so later steps in the flow can use them. This article is for builders who add a lookup step to a flow and need to use its data downstream. Results mapping applies to lookup steps that have at least one step after them in the flow. For import steps, see Configure response mapping.

How results mapping works

A lookup step retrieves data from an application, but the data stays in the lookup's results until you map it. Results mapping copies selected parts of those results into fields on the source record. Every later step then receives the record with those fields.

If the source record already has a field with the name you choose, the lookup value overwrites it. Otherwise, integrator.io adds a new field. Every lookup step needs a results mapping for its data to be available later in the flow.

Configure results mapping

Before you begin, make sure the flow has at least one step after the lookup step.

  1. Open the flow in the flow builder.
  2. On the lookup step, select Results mapping mapping-icon.png.
  3. In Lookup response field, select the field to copy.
  4. In Source record field, enter the name of the field that will hold the value.
  5. Click Save & close.

The panel is titled Edit results mapping.

Results fields

Field Description
data The records the lookup returned, as an array.
errors Errors from the record processed in this step.
ignored true if the step ignored the record, otherwise false.
statusCode The status code from processing the record in this step.
dataURI When available, the link to the data the lookup retrieved.

Choose between data and data[0]

data is always an array, even if the lookup returns one record.

  • If the lookup returns one record, such as a search on a unique ID, map data[0]. It selects the first item in the array, so the new field holds one object.
  • If the lookup can return several records, map data. The new field holds all the objects, and later steps can read it as a normal JSON array.

Add more lookup steps

You can add as many lookup steps with results mappings as the flow needs. Use a different Source record field name for each lookup so that one result doesn't overwrite another.

For a worked example, see Example: Merge Mailchimp lookup results into a Salesforce import. For a lookup on a field inside an import mapping, see Add a lookup to an import mapping.