We have amazing news!

Four new members have joined our webhooks family 🎉

We are thrilled to announce that these long awaited webhooks are here:
1. When a subitem is deleted
2. When an item is deleted
3. When a subitem is archived
4. When an item is archived

Use them wisely 😎

We have added the possibility to use the changing of an item's name as a trigger!

This is available, in the automation center, in the recipe builder and as a trigger for a webhook:

Today we hit a big milestone – board IDs for new boards are now larger than 2147483647. Our users are creating more boards and workflows than ever!

This also means they cannot be stored as integers. More specifically, they are too large to be stored as a 32-bit signed int.

If you are currently handling board and item IDs in your application as integers, you need to update your application to use another data type such as bigInt.

You will also need to run migrations on any databases that store board IDs as integers, as they will fail to store any new board IDs.

We are proud to announce the latest version of the monday style guide — Monday Vibe!

It’s a brand-new central repository for all things monday style: React components, style guidelines, and UI notes in one place. Check it out at style.monday.com!

Monday vibe features:

• Full design guidelines to design your apps like monday’s own design guild
• 26 components for you to use in your apps
• A sandbox for testing each component
• Styleguides for fonts, animation, and presentations
• A logo library

We have also updated the Monday UI kit and you can check it out here!

Thank you to all the team for your contributions.

Happy building 🔧

We just released an amazing feature that will make your apps much more flexible for your users 💪

Now, your triggers and actions can be added to the automation center, so your users can incorporate them in their custom recipes.

Check out our full documentation here: Workflow Blocks

We just added a new feature that will notify a URL of your choice when an app is installed (and uninstalled) on a user's account.

To add this to a published app, please create a new minor version, add the relevant URLs, and then publish that version to live.

When the app is installed, your install URL will get the following JSON payload:

{
  "app_id": 3184,
  "account_id": 123456,
  "user_id": 234567,
  "timestamp": "2021-10-28T14:55:34+00:00",
  "version_data": {
    "major": 1,
    "minor": 1,
    "patch": 0,
    "type": "minor"
  },
  "type": "install"
}

For full details on this change, check out the following article: Install URLs

We recently added the ability to support the People column within dynamic mapping custom fields.

The People column will utilize a new primitive type as its input: user_emails. This user_emails type is an object with two keys: identifierType which is a String, and identifierValue which is an array of identifiers (i.e. email strings).

Here is an example:

"people": { identifierType: "email", identifierValue: ["[email protected]", "[email protected]" ....] }

As noted above, the People column will accept user_emails as both its inbound type as well as its outbound type. No other types are supported.

🚧

NOTE

Currently, if user emails are sent that do not exist in the monday.com account, or do not have permission to access the board, item, and/or column in question, the email will be omitted and no change will occur in the account.

For more information, check out the Item Mapping and Custom Entities documentation.

We released the ability to trigger webhooks, as well as some built-in trigger blocks for custom integration actions by changing the hours field in a date column.

You can learn more in our community post here.

We released the ability for admin users to restrict who is able to generate API tokens in their account.

You can learn more in our community post here.

We released a new built-in action block "Create an item with mapping and link."

You can learn more about this in our community post here.