Skip to main content
Three types of fields exist for users to see in the Zap editor:
  • Input fields
  • Dynamic fields
  • Line item groups

​
Input fields

Input fields are most commonly used and include 10 types that look and act differently in the Zap editor. Depending on the type, users can either enter plain text data, make a selection or map variables from previous triggers and actions. Zapier does not validate the data to ensure users added the correct item for that field type.

​
String

The default input field, which accepts text input. Typically used to gather individual text values such as a name or email address.

​
Text

Displays large, <textarea>-style entry box, accepts longer text input. Often used to enter notes.

​
Integer

Accepts integer number values, shown with a 1 2 3 tag beside the field in Zap workflows. Typically used along with a dropdown type field to select ID numbers for objects in your app, also used to gather whole numbers.

​
Number

Accepts any numeric value, including decimal numbers, shown with a 1.0 tag beside the field in Zap workflows.

​
Boolean

Allows users to select between yes and no values in a dropdown in their Zap to send a corresponding 1 or 0 in the request to your app’s API.

​
Datetime

Accepts both precise and human-readable date-time values. Sends an ISO-formatted time string in the request to your app’s API.

​
Password

Displays entered characters as hidden, accepts text input, just like standard string fields. Does not accept input from previous steps.

​
Dictionary

Users enter their own value sets, with a plain text name followed by a String field to enter or map data from previous Zap steps. Click the + button on the right to add additional dictionary field entries.

​
Copy

Does not allow users enter data and is not passed to your app’s API. Shows the Help Text field copy in a display-only formatted note, with no input field. Supports Markdown. Typically used for important notices to users.

​
JSON

This field type is only available in the Platform CLI (v18.4.0+).
Accepts a JSON object or array. Optionally pair with a schema property containing a JSON Schema to validate the input’s structure at runtime. Use for structured data like request bodies, configuration objects, or nested payloads. For more details and examples, see JSON Fields.

​
Dynamic fields

This feature is only available in the Platform CLI.
Dynamic fields make a request to your app’s API, showing the returned data in a dropdown menu in live time. Users select the object needed. Typically used for folders, projects, assignees, and other data that would need to be chosen from within your app.

​
Line item groups

Line item groups allow users to input line items provided from the trigger or prior action. Those items will then be sent in the request as an array of individual objects. Users cannot input comma separated values into a line item field, they need to be provided from the trigger or a prior action in line item format for them to be sent this way. Typically used to add multiple lines of similar details to an app, for example in invoice and accounting apps.
Last modified on August 18, 2026