Mapping Fields Between Apps
Learn how to connect data fields from your trigger app to the corresponding fields in your action app so data flows to the right place.
Before you begin
Before you start, make sure you have:
- A workflow open in the builder with a trigger fully configured and tested
- The action step's Setup and Account tabs completed
- At least one test record available in your trigger app (so sample values appear in the picker)
What mapping does
Mapping is how you tell Conduitly: "Take this piece of data from the trigger app and put it in this field in the action app."
For example, if your trigger is a new employee record in EmCentrix and your action is creating a record in QuickBooks Desktop, mapping connects the First Name field from EmCentrix to the First Name field in QuickBooks, and does the same for every other field you want to carry across.
Without mapping, the Conduitly workflow doesn't know which data goes where. The mapping step is where you make those connections explicit.
Steps
1. Open the Mapping tab
In the workflow builder, click the action node you want to configure. The configuration panel opens on the right. Click the Mapping tab.
Note: The Mapping tab only appears on action steps, not trigger steps. If you don't see it, make sure you've clicked an action node.
2. Complete the resource selection step
The first sub-step of the Mapping tab asks you to identify the target resource in your action app, like which spreadsheet and worksheet to write to, or which record type to create.
Required fields are marked with a red asterisk (*). Fill in each required field, then click Continue →.
The blue header bar at the top of the tab shows your current sub-step and the total number of steps (e.g. "Step: 1 by 3").
3. Map your fields
In the following sub-steps, you'll see a list of destination fields for your action app. For each field you want to populate, click the blue + button on the right. This opens the Choose Data picker.
4. Choose the source data
The Choose Data picker shows all the data fields available from your trigger step or preceding action steps. Fields are listed by name in black, with a sample value in orange beside each one.
The orange sample values are real data pulled from your trigger app during the test step. Use them to confirm you're selecting the right field before mapping it.
Click the field you want to use. It will appear as a token in the destination field input.
Note: If you don't see sample values, go back to the trigger's Test tab and run the test first, then return to mapping.
5. Repeat for each field you want to map
Not every field needs to be mapped, only the ones your workflow requires. Work through the destination fields and map each one that should receive data from the trigger. Use ← Previous and Continue → to move between sub-steps if needed.
6. Complete the action configuration
Once you've mapped all the fields you need, click Complete ✓ on the final sub-step. This closes the action configuration and returns you to the canvas.
What to expect next
Your action step is now fully configured. On the canvas, the action node will show the app name and event you selected.
If you have additional action steps to configure, click each one and repeat the mapping process. Once you've added all the action steps you need, you're ready to test the workflow and then publish it. See Testing a workflow before publishing for the next step.
Tips for mapping
- Use sample values to verify your selections. The orange values in the Choose Data picker show real data from your trigger app. If the sample value looks right, the field is right.
- Required fields in the action app are marked with a red asterisk. Leave optional fields blank if you don't need them. You don't have to map everything.
- You can type directly into a field instead of using the picker. If you want to enter a fixed value (like a constant label or default text) rather than pulling from the trigger, click the Enter data... input and type it in.
- If your trigger has multiple steps, the Choose Data picker will show fields from each step as separate collapsible sections. Expand the relevant step to find the fields you need.
Related articles
- Understanding triggers and actions
- Testing a workflow before publishing
- Connect an app to your workflow
- Build your first workflow