When you’re setting up your Zap, each step includes fields where you can enter data. In these fields, you can:

• Manually enter values.
• Map fields from a previous step.
• Select a value from a preset list in a dropdown menu or use a custom value. 

The field type determines what values you can enter in a field. The field types available in a step will vary.

Note

Some apps:

• Have additional restrictions for what kind of info you can enter in a field type.
• Allow you to enter special formatting to output design elements, like bold text, bullet points, and code blocks.

Date/time fields

A date/time field is a field where you can only input a date and/or time. It displays a calendar icon.

Using timezones in date/time fields

If you have trouble using date/time, try including a timezone in the field.

Supported date/time formats

Zapier tries to interpret any date or time you provide. For example, Zapier supports the following date formats:

• tomorrow at noon.
• next Friday at 7PM (Friday of the next week, not the current week).
• 2/13/2020 8PM EST.
• 2020-10-26T16:56 (standard ISO format).
• 1393462573 (a UNIX timestamp).

Tip

You can:

• Adjust date/time values in Zaps by adding or subtracting time from the value within the field.
• Include a timestamp of when your Zap ran in your action steps.

Note

• Zapier uses the ISO 8601 standard for formatting dates, but some apps may use different date and time defaults.
• Zapier will use the timezone in your account settings unless you change the timezone in your Zap settings.
• If you enter a date or time that Zapier cannot interpret, the Zap will default to the date and time that the Zap runs.

Dictionary fields

Dictionary fields allow you to enter key/value sets. They do not have an icon. They consist of two columns:

• The left column is where you enter the name for the value set.
• The right column is where you enter the value for the value set.

After you enter a value set, click the:

• Plus sign icon below the last value set to add another blank value set.
• X icon next to a value set to remove it.

Dropdown menus

In dropdown menus, you can select a value from a list of preset options. If you do not see the option you need, you can use a custom value instead. They do not have an icon.

File fields

File fields in Zapier refer to the actual file object and have a file icon that looks like a page. To send a file in a Zap, you need to use a file object or certain types of URL links. The file field acts differently depending on what data you send it:

• Text: Zapier will turn text into a .txt file and upload it to your app.
• URL: if you enter a URL, Zapier will try to load the data available at that address and upload it as a file.
• File: if you map a file from another step, Zapier will upload it

Tip

If you have multiple file objects or URLs, you can separate them with a comma and a space to send them all at once. This will compress them into a single .ZIP file for uploading.

Note

• If a previous step has a file object, it will have "(Exists but not shown)" for the sample value.
• Your app determines the maximum file size you can use. Refer to the app’s documentation for more information.
  • Zapier must be able to upload or retrieve the file within 30 seconds or the file request will time out.

Line item fields

Line items are collections of separate data gathered into a single field. A single line item can consist of multiple fields and values. This contrasts with other field types that have one value per field. In programming terms, they are arrays of objects. Line item fields are usually found in commerce apps.

For example, when you create an invoice, each line in the invoice is a single line-item, but it includes multiple fields and values like the item name, quantity purchased, unit price, and total for that line item. 

Line item fields do not have an icon, but they are offset in a separate box with all related fields. Learn more about creating line items and using line items in Zaps.

List fields

List fields allow you to enter or select multiple options. They do not have an icon. Each time you enter a value in a list field, another blank list field will appear below it. 

• Click the X icon to the right of a list field to remove it.
• Hover over a list field. A grid icon of 6 dots will appear to the right of the list field. Click, hold, and drag the grid icon to rearrange the order of your list fields.

Number/decimal fields

You must enter numbers into both number and decimal fields.

• Number fields only accept whole number values. If you enter a decimal value in a number field, Zapier will round the number down to the next whole number.
  • They have an icon showing the numbers 1, 2, 3.
  • Dropdown menus are often number fields. You can use them to select ID numbers for users, projects, and other internal data from apps.
• Decimal fields allow you to enter any numeric value, including decimal values like 1.5.
  • They have an icon showing the number 1.0.
  • You must separate decimals from the integer with a period ..

Example

If you enter “4.7”:

• In a number field, Zapier will round the number down to “4”.
• In a decimal field, Zapier will use the exact number of “4.7”.

Password fields

Password fields are the same as string fields, but the value you enter is hidden from view. Some apps use password fields for sensitive data. They do not have an icon.

String/text fields

These are the default fields and do not have icons. They are general fields that allow you to enter a variety of values.

• String fields consist of a single input line for values like names and email addresses.
  • To add new lines in a string field, click Shift + Enter at the same time.
• Text fields consist of larger input boxes that allow you to enter more info, like email messages and notes.
  • To add new lines in a text field, click Enter.

True/false (boolean) fields

Boolean fields only have two values: "true" and "false". Depending on the app, these values may be different, such as "0" for false, or "1" for true. They do not have an icon. Boolean fields are often case-sensitive. For example, if an app expects "TRUE", it won't recognize "true" as a valid option.