In this lesson you’ll learn:
How to use the Data Mapper Helper to convert field values
How to dynamically set the input field based on workflow data variables
How to avoid using static values in your workflows
Introduction
Right now, our workflow sets the patient’s Gender field to a static value—Male. That’s not very useful for real-world scenarios, where gender should be populated based on the form submission.
Also, DrChrono expects gender values like "Male", "Female" or "Other", while Jotform submissions might return "M", "F", or even custom values.
We can see the issue here in our case as in Jotform our form has these values:
And in DrChrono if we open the "Gender" input we see that the expected values are:
In this lesson, you’ll learn how to fix this by using the Data Mapper Helper to convert form values into the exact values expected by DrChrono.
Step 1: Add a Data Mapper Helper
What is the Data mapper?
The Data Mapper works like a simple lookup table.
It takes data from previous steps (like form responses) as input.
Then, it outputs a new value based on a list of mappings you define.
You can learn more about the data mapper here.
The fastest way is to describe it in the chat panel (left side of the editor):
"Add a Data Mapper helper before the Branch step to convert gender values from Jotform — M to Male, F to Female, O to Other."
Click Update workflow to confirm.
Manual option:
Click the + icon before the Branch step
In the Add new step panel, go to the Helpers tab
Select Data helpers, then Data mapper
-
Configure the Datamapper:
Lookup key(s) : Map the Gender field from Jotform.
-
Mapping Values:
M→MaleF→FemaleO→Other(Add more mappings as needed)
- Test the step to have the data available in the workflow and ensure it works as expected.
In that way we have configured the data mapper so when in Jotform the answer is M then our helper will transform it to Male so it is exactly as DrChrono expects it.
💡 Tip: Inside the Data Mapper configuration panel, use the "How to configure this?" and "How to use" buttons for additional guidance.
With this configuration, when Jotform returns M, the helper transforms it to Male — exactly as DrChrono expects.
📌 Missing a helper? Use the "Missing a helper? Request a helper" banner at the top of the Helpers tab.
Step 2: Map the Transformed Value
Describe it in the chat panel:
"In the Create/Update Patient step, use the output from the Data Mapper helper for the Gender field."
Or manually:
In the Create/Update Patient step, click on the Gender field.
Navigate to the Steps tab and select the output from the Data mapper Helper.
📌 Important: Using the Datamapper ensures that your workflow always sends valid, expected values—even if the form response varies.
Step 3: Test Your Workflow
- Publish your workflow
-
Submit the form selecting
"M"for gender.Verify that the workflow sends
"Male"to DrChrono.
-
Submit the form with
"F".Ensure that
"Female"is sent correctly.
Success!
You’ve now made your workflow more dynamic and reliable by mapping values automatically.
Try it yourself:
Using the chat, describe the data mapping you need:
"Add a Data Mapper helper before the Branch step to convert gender values — M to Male, F to Female, O to Other."
Run a test and confirm the output matches what DrChrono expects before moving on.
What's next?
You should now be confident building workflows that include logic control and data transformations to handle real-world automation scenarios.
Ready for more? Continue your learning journey with our Advanced Course, where you’ll master even more powerful techniques!
In the Advanced Course, you’ll learn how to:
Work with files in your workflows
Add code steps to perform advanced data transformations
Use For Each loops to process lists of items dynamically
Make custom HTTP calls to replicate actions not yet supported by built-in connectors
Next Course: (Advanced) Master Advanced Workflow Automation