Mappers

Workflow mappers are one of the most critical pieces of the workflow builder, allowing you to manipulate data between steps and prepare it for the next. It also allows you to combine data that you had to iterate over into a single object.

For details on accessing needed data from prior steps, reference Workflow Step Fundamentals.

A map is fundamentally very simple and requires just a few steps:

Actions

Here you select which app steps to import data from (you can select multiple):

Note: For any action that is within an iterate step, you can select “Group,” and all values from each time the step is run will be passed into the mapper in an array. This will initially be passed in as a two-dimensional array, which you may need to flatten depending on how you plan to use the data in later steps.

Mapper Config

Here you can add batch processing as needed to increase efficiency when mapping an iteration with multiple values:

Code

The next step is to code the mapper itself. It starts out with a minimized code window and an AI prompt, simply pulling in the data from the steps you’ve mapped plus anything in the Workflow Memory and System values.

Here you can either code a rapid workflow manually, or you can use the AI prompt to have it code the workflow automatically.

To make it easier, you can also expand the map coding interface to show the code, input, and output in realtime, allowing you more easily adjust and code the workflow itself. The AI prompt here is especially useful, allowing you to refer to anything within the input and determine the exact output without having to write a line of code.

Output

Once you run the mapper, you can then view the output of the mapper in it’s final form: