Help

Understand different field types in Zaps

reference
Last updated:

When working within the Zap Editor, you may notice little icons next to certain field types. Here is an overview of all the different icons that you can see within the Editor:

Different icons to identify different field types


Date/time fields

A date/time field is a field where you can only input a date and time, and is represented by an icon of a calendar and a clock.

Timezones

If you don't provide a timezone, Zapier will assume the timezone you have configured in your Zapier profile, which you can change in your account settings. Nevertheless, there are some specific integrations where providing a timezone might not work as expected. If you think this is affecting your Zap, contact Zapier support for help with a closer look, as each app will have different rules.

What formats are supported

Sometimes, these can get a bit complicated, but Zapier does its best to interpret any date or time you provide. For example, all of the below are supported:

  • tomorrow at noon
  • next friday at 7pm
  • 2/13/2014 8pm EST
  • 2014-02-26T16:56 (standard ISO format)
  • 1393462573 (a unix timestamp)

Adjusting date/time values

You can adjust the date/time values in date/time fields by including a modifier after the date/time value. Note, you must include a space between the modifier and the date/time value.

In order to set the due date one day after the date from Step 1, we can add "1d" after the value.

A modifier includes:

  • A + or -, signifying forward or backward in time
  • A number
  • A unit of time: s (seconds), m (minutes), h (hours), d (days), month (months), y (years)

For instance:

  • +7h - 7 hours after the date/time in the field.
  • +10d - 10 days after the date/time in the field.
  • -45m - 45 minutes before the date/time in the field.
  • +30s - 30 seconds after the date/time in the field. Useful if you receive a duration in seconds.
  • +1y - 1 year after the date/time in the field.

You can mix and match those as well. These modifiers must be separated from date/time values and each other with spaces. In the example below, the Start Date & Time field has a space between the date/time value and the modifier, and the End Date & Time field does not have a space between the date/time value and the modifier.

Adjusting datetime values spaces

  • +5h +30m - 5 hours and 30 minutes after the date/time in the field
  • -2d -12h - 2 days and 12 hours before the date/time in the field.

Tip

If you need to do more advanced modifications or reformat a date, you can use a Formatter step. Learn how to modify dates and times with Formatter.


Number (Integers) fields


Numbers are very common in the world of Zapier and we do our best to convert information we receive into a clean number. For example, something like 2 burritos will be turned into 2.

numberfields

Often with these fields you'll see a dropdown with apparently "non-number" options in them (such as name or email), but don't be fooled! Lots of apps have ID’s that identify related objects, and you'll need to remember to select an item or send on the correct number!

If you have a drop-down that’s expecting a contact ID of sorts and you want to use a field from the trigger to make the selection more dynamic, you will need to choose a field with an ID next to it. You can read more about those here.

nameids

namenames


True/False (Boolean) fields - Data in the form of True or False


We do our best to turn normal words into their proper true or false representations. For example, "yes" is "true", as is "1" or any string at all! "No" is "false", as is "0" or "f" among others. You will need to look in your Zap to see how those fields are being represented based on the app you're using. If you click on the "Insert Fields" button, you'll be able to locate the checkbox field and see how those values are being presented.

If you are looking to set up a condition where certain action are taken based on whether a checkbox is checked or not, you will need to setup 2 Zaps with custom filters in each one. One Zap would have filter for true value and the other Zap would have a filter for the false value. These values can change depending on how the app sends over those checkbox values.

JFF

Here are some examples showing how Jotform sends over those values.


File fields - Data in the form of an actual file object or URL


When we reference files on Zapier, we mean the actual file object, and not a text field describing the file. For example, a file would be a photo itself, a field describing that file might be the Name, or the URL for that photo. If you put a string of text in a file field, we'll convert it to a .txt file for you. If you give us a URL, we'll inspect the URL and try to load in the data there and name it properly. And, if the item is a file from the trigger side, we'll bring it along.

Note: inserting multiple file fields into a single file field is unsupported.

Quick reference:

  • File: passes file to action app
  • URL: passes data from URL in the form of a single file to action app
  • Text: creates a .txt file containing the field contents and uploads to action app

Decimal (floats) fields - Data in the form of decimals

Decimals are pretty common and contrary to popular belief, they are not currency specific! They are very similar to numbers/integers except we'll allow a decimal here or add it if it is missing.


Was this doc helpful?

Need More Help?

Zapier Support

Contact our world class support team and we’ll be happy to help you get up and running!
Contact Us

Hire an Expert

We have a directory of professionals across the globe who are ready to help.
Find a Zapier Expert