Field Types#

When you are setting up your Action's template you'll notice that some fields have icons next to them. That's because certain field types are looking for certain formats of data. In this guide we'll cover those field types so you can make sure you're sending on the right kind of data and avoid running into errors.

Icons#

Found an Icon and not sure what it means? Select your icon's title below to find out more.


Datetime fields

Number Fields

True/False (Boolean) fields

File fields

Decimal fields

Field descriptions#

Find descriptions for each field type below.

Datetimes#


Datetime fields are only looking for a date to be sent on. They can also be fairly complicated, but we do our best to interpret any date or time you throw at us! 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)

You can also modify your dates with dynamic modifications. These are useful if you want to add or subtract time from your date field.

It’s important to note that the datetime examples above will only work if the field on the action side contains the calendar and clock icon like this:

datetime icons

Numbers or Integers#


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 - Using Checkboxes#


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.

Files#


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*

Decimals or Floats#

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.

Arrays#

An array is a list of data. For example, invoicing apps that have "line items" will often send and receive this data as an array. Arrays pop up in a lot of situations, for example: line items, checklists, addresses, etc.

We only have really limited support for arrays right now, so only certain apps and certain triggers and actions have this functionality.

You can see which fields on an action support line items as they are intended in a box like this:

You are welcome to insert single values in here (for example, no line item in the trigger and array support only on the action), but when given a trigger that provides arrays we will automatically create as many items as needed (for example, array support in both the trigger and action).

This means to send and receive data as an array, you'll need to make sure both the trigger and action both support this.

This will be clarified on the actual trigger and action when you are setting up the Zap like this: with line item support

Arrays are mostly automatic, you just insert what you want to map to this field and we'll figure out the rest for you. If you have a different or specific use case for this, please get in touch and we'll be happy to advise further.

↑ Was this documentation useful? Yes No (Suggest Edits)
Get Help