What can we help you with?

Cross-Board Automations

Do you have boards on monday.com that organize separate projects and tasks but still contain information directly related to each other? 

Cross-board automation recipes offer the ability for boards to interact by allowing an action in one board to trigger an action in a completely separate board. Many of these recipes will also link connected items across boards.

These automation recipes add a new layer to team collaboration and allow your team to manage interrelated projects seamlessly and cohesively.

 

How to add an automation

To add the relevant cross-board recipe to your workflow, you will first need to visit our automation store at the top of your board:

Frame_487.png

There you will be able to choose from our different recipes and set up the cross-board automation that supports your workflow. Try searching "in board" or "in another board" to easily locate relevant recipes: 

Frame_485.png

Be sure to scroll down to view more cross-board recipes:

Frame_486.png

There are many options to choose from!

 

Note: In order to map across boards, the column you want to map must exist on both boards. Additionally, the information in the updates section will only move over when using "move item" automations but not when using automations that create new items. 

 

Mapping columns

If the recipe you choose creates or moves an item, you'll have the opportunity to map out what information carries over to the selected board and where that information will go within the selected board's structure. This is called mapping. Check out the mapping section of the Automations article to learn more.

Some information will not carry over. The below column types are considered "static" and are not currently supported in mapping:          

  • Mirror
  • Dependency
  • Link to Item
  • Files
  • Time Tracking

When mapping an item, static columns will not have a blue + sign next to them:

Frame_489.png
 

Note: In order to map column values, the mapped columns will need to be on the source board and the receiving board. 

 

Cross-Board Examples 

Example #1

A Project Management team has a high-level iteration board. Everyone's tasks are listed on this board so that the whole team has a clear picture of each iteration.

Frame_491.png

The team also needs identical tasks to be created on low-level team member boards. They'll use the following recipe:

When person is assigned to someone, create an item in another board and connect them in the selected board

Frame_490.png

With this recipe, when the selected person is assigned to an item, a new item will be created in the board selected under "another board". This will allow the team member to have a separate board with a complete list of their tasks!

 

Note: When you click on the "connect them" field, you will have the option to add a Connect Boards Column on the selected board in the "another board" field. 

 

 

Example #2

A marketing company is using an embedded monday.com form for their mailing list. Once the form is completed, an item is sent to a monday.com board. If approved, the item needs to be automatically moved to the next board in the pipeline. This is what the origin board looks like:

board_2.png

 

To complete their workflow, they'll use the following recipe:

When status changes to something, move item to board

Frame_492.png

 

Note: For automation purposes, moving an item to a board isn't considered a new item. So if on the receiving board you have an automation set to notify when a new item is added then it will not trigger.

 

 

Want to learn more about our variety of automations? Please check out this article!

And if you have any further questions, feel free to reach out to our customer success team at support@monday.com. We are here for you 24/7 and always happy to help! 😄