Send data between steps by mapping fields

When you set up your Zap action, you can use static or dynamic values in the action fields.

  • Static values: When you type a value into an action field or select a value from a dropdown menu, the Zap will send the same value to your action app every time it runs.
  • Dynamic values: When you map a field from a previous step, the Zap will send the information received for that field every time it runs.

The action of using dynamic values is referred to as “mapping a field”. This means you select information that you receive from one app and send it to another.

actionEdit icon Example

If your Zap creates a new lead in your customer relationship management (CRM) app whenever a customer signs up for an event, you can:

  • Type a value like “April Block Party” into the Lead Source field. When the Zap runs, it will send “April Block Party” to the Lead Source field every time it creates a new lead. This is a static value, as it will be the same value every time the Zap runs.
  • Select a field like the phone number field from your event signup app to send to the phone number field in your CRM action. When the Zap runs, it will send whatever phone number your lead signed up with, changing each time the Zap runs. This is a dynamic value.
miscEye icon Note

You can use both static and dynamic fields in an action.

Mapping fields is a powerful tool to build dynamic and flexible workflows.

1. Map fields

To map fields when you set up your Zap action:

  1. Click on the field that you want to set up.
  2. In the dropdown menu, select one or more fields from a previous step that has the information you want to use.

In the previous example, when you click on the phone number field in the CRM action, the dropdown menu will show all fields received from the signup form that triggered the Zap. Clicking any of those fields will map them to the phone number field in the CRM action. So, when someone fills out the phone number field in your signup form, the Zap will send their phone number to your CRM.

Phone number field in action step showing mapped phone number field from trigger step

miscEye icon Note

You can only map fields from a previous step to a subsequent step. You can’t map fields from a later step to a previous step.

Was this article helpful?
1 out of 3 found this helpful