Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Zaps
  • Zap basics

Enter data in Zap fields

Written by Owner

Updated at August 20th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Tables
    Work with tables Manage tables Create tables Troubleshoot Zapier Tables
  • Product updates
    Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
  • Zaps
    Zap basics Zap history Troubleshoot Zaps Manage your Zaps Do more with Zaps
  • Your Zapier account
    Plans Billing Account profile Notifications Data privacy & security Get help User roles and permissions
  • Interfaces
    Troubleshoot Zapier Interfaces Create an interface Use interface components Manage interfaces
  • Canvas
    Create a canvas Collaborate on a canvas
  • Chatbots
    Add logic and knowledge to chatbots Troubleshoot chatbots Create chatbots Manage chatbots
  • Getting started
    Intro to Zapier Set up your Zapier account Use case templates
  • Agents
    Create agents Manage agents Troubleshoot agents
  • MCP
    Set up MCP
  • Built-in tools
    Filter & Paths Formatter Schedule & Delay Email, IMAP, SMTP, & Email Parser Webhooks & Code Storage, Digest, & RSS Sub-Zap & Looping Other built-in tools Custom Actions & API Requests Functions AI by Zapier & AI actions Copilot Human in the Loop
  • Lead Router
    Create routers
  • Apps
    Connect and manage your app connections AI apps on Zapier Apps on Zapier
+ More

Table of Contents

Types of values Static values Dynamic values How to enter values in a field Manually entering a value Field mapping Selecting from a dropdown menu

When you build your Zap, you decide what data should automatically flow through each step. You do this by entering values into fields in each step. Those values can be static, meaning they’re the same every time the Zap runs, or they can be dynamic, meaning they change. How you enter values in a field will vary depending on the field.

Types of values

There are two types of values: static and dynamic.

Static values

Static values are fixed and do not change. Use static values when you want to send the same value every time the Zap runs.

Dynamic values

Dynamic values are variable and will change. Use dynamic values when you want to send a different value every time the Zap runs.

Note

Each field is limited by its field type. Each field type will only accept values that are formatted in a specific way. Learn more about field types in Zaps.

How to enter values in a field

There are three ways to enter values in fields: by manually entering a value, mapping fields from previous steps in your Zap, or selecting a value from a dropdown menu.

Manually entering a value

You can manually enter a value by typing or pasting it directly into the field. This is how you enter static values.

GIF displaying a user typing a static value into a field

Field mapping

Field mapping is a way to connect two fields so data flows between them. When you map fields, your Zap will automatically take the output of the first field and enter it as an input in the second field. This is how you enter dynamic values in the second step.

You can only map fields that are in separate steps. Data will always flow in one direction, from the preceding step to the subsequent step.

Diagram of mapping two fields so the value from the preceding step flows into the subsequent step

The mapped field is displayed as a pill, or bubble, encasing info about the preceding step where the value is coming from. This includes the:

  • Icon for the app used.
  • Step number.
  • Field name (black, bold text) followed by a colon.
  • Field value (plain gray text).
    • The value is a placeholder that comes from the test record created when you tested the preceding step. It will only be used by your Zap when you test this step during editing.
    • Once you publish your Zap, real data from your apps will flow through the Zap.

You can manually enter values or map fields from previous steps or variables in any field that has a “+” button at the end of the input box. Learn how to map fields in Zaps.

Body field displaying a mapped Direct Link field from the previous step

GIF displaying a user selecting a field from a previous step to map it to the current field

Selecting from a dropdown menu

You can identify a dropdown menu field by the stacked up and down arrows at the end of the input box. They have preset options for you to choose from. When you click on the field, the dropdown menu opens so you can select an option. Your selection is a static value.

GIF displaying a user selecting options from dropdown menus

If you want to enter a different value than what is offered in the dropdown menu, you must use a custom value instead. Custom values allow you to manually enter or map fields in the dropdown menu. To the right of a dropdown menu, there’s a settings button that allows you to switch between the default static option and a custom option in the dropdown menu field. Learn how to use a custom value in a field.

Modal field displaying settings button

GIF displaying a user switching from a static value to a custom value by clicking the settings icon next to a dropdown menu field, then mapping a field from a previous step

Example

You want to create a workflow where every time you create a new monthly sales spreadsheet, you send an email that includes a URL link to the spreadsheet. Your trigger includes a field, Direct Link, that contains the link you want to use. In the action step:

  • You can enter the email subject as a static value in the Subject field by typing in “Monthly sales report”. You also want to include the timestamp for when the spreadsheet was created, which is available in your trigger’s Created Date field, so you can map that after your static value.
  • In the Body field, you can map the Direct Link field from the trigger step as a dynamic value. Each time you create a new spreadsheet, the Direct Link field will have a different link that corresponds to the new spreadsheet. Because you mapped it to the Body field, the value will adjust accordingly.
  • In the Body type field, you can select “Plain” so you can use plain text in the Body field, instead of HTML.
    • If you wanted to dynamically update the value in the Body type field, you could use a custom value instead of selecting from the dropdown menu. For example, if you wanted to use Html as a value, you'd enter "html" to match the ID shown in gray text in the dropdown menu.

alternatetext

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Copy and paste triggers and actions across Zaps
  • Use the power of AI to generate Zaps
  • Use the editor to build and view your Zaps
  • Test Zap steps
  • How to find an app’s ID to use in a Zap field

Copyright 2025 – OBZ-Zapier.

Knowledge Base Software powered by Helpjuice

Expand