When you go to create a new integration with Zapier that uses monday.com to create a new item or populate column values, some columns will require the information you send to be in JSON format to pass through correctly. Read on to find out more!

Which actions in Zapier is this relevant for?

Using JSON format is only necessary for operations that update the values ​​of an existing item or create a new item in a monday.com board:

How does it work?

• Status
• Dropdown
• Date
• Timeline
• Link
• Phone
• Email
• Numbers
• Text
• Long Text
• Location (you will need to use latitude and longitude coordinates)

You can find the full list of column types here .

How to place the correct data in the correct column?

That’s a great question! This is where the Column ID comes into play.

When you send data to a specific column on your dashboard, you will need to specify the Column ID. This will help the platform understand which specific column on your dashboard to save the data to, as each column has a unique identifier on the dashboard. If you are not sure where to find the Column ID, the following guide describes how to view it on a monday.com dashboard – Where to find the board, item, and column IDs

So far, what we have achieved:

Keep reading to learn specific examples of how to implement JSON format to keep your data flowing into monday.com.

How to apply JSON format to column values

When you set a value for a column within the “Create a new item on monday.com ” or “Change multiple column values” actions, some columns will require you to use JSON format to save your data.

You can find a list of the columns and the format of the data they expect to receive below:

• Connecting panels with one item: {“item_ids”:[1360856860] }
• Connecting panels with multiple items: {“item_ids”:[1360856860,1360856957] }
• Dependency column with one item: {“item_ids” :[1587277166] }
• Dependency column with multiple dependent items: {“item_ids” :[1587277166,1587277190] }
• Tag column with one tag: {“tag_ids” :[295026] }
• Tag column with multiple tags: {“tag_ids” :[295026,295064] }
• Country column: {“countryCode”:”US”,”countryName”:”United States”}
  • The countryCode key uses ISO Alpha-2 country codes ;

• World clock: {“timezone”:”Europe/London”}

  • You can find the list of available time zones here .

• Week: {“week”:{“startDate”:”2019-06-10″,”endDate”:”2019-06-16″}}
  • Submit the start and end dates in the format YYYY-MM-DD. The dates must be within 7 days (including the first and last date) and begin at the beginning of the work week defined in your account settings.
• Time: {“hour”:13,”minute”:0}
  • Make sure you remove any leading zeros from the data you send (i.e. send the number 9 instead of 09).
• Rating: {“rating”:5}
• Checkbox: {“checked”:”true”}

Below is an example showing the format for updating the column types mentioned above:

In the left field, enter Column IDs . In the right field, enter the corresponding value in JSON format (see the JSON format list by column type in the previous section).

And here are our results:

Below is an example that shows the format for updating a panel connection column, so we can go into even more detail:

So, how does it work?

• In the left field, we entered the Column ID
• In the right field, we entered the appropriate value in JSON format. For a table connection column, this would involve using {“item_ids”: to describe what type of data is being sent, followed by the item ID (in my case, 1192176644) that the platform needs to connect to. Since the board connection job allows you to connect to multiple items at once, your item IDs need to be sent in an array inside parentheses. Depending on these parts, we end up with: {“item_ids”:[1192176644] }