Summary: With our monday.com integration, users can extend their Ziflow online proofing operations to monday.com. Users can automatically create, update & assign items in monday.com for new proofs, comments, decisions, and more to keep their team up to date with the tools they're already using.
Click the button below to watch videos showcasing our integration capabilities.
Follow the instructions on how to:
Please note that before setting up the integration between Ziflow and any third-party tool, it is necessary to connect Ziflow with the external application first. The process of connecting Ziflow to external applications can be found below.
How to connect with monday.com
As a first step when setting up the integration, you will need to install the monday.com plugin to let Ziflow connect with your monday.com board.
To integrate monday.com with Ziflow, open the Connect tab in the Ziflow account and click on the Applications tab on the left. Once inside the Applications menu, select monday.com from the list. You'll be asked to authenticate with monday.com credentials and then authorize Ziflow to access the monday.com account.
To enable monday.com fields at the proof level, please go ahead and navigate to the connection settings and activate them by selecting the Show option.
After successfully logging into monday.com and granting Ziflow permission to connect with your monday.com account, you can begin configuring automatic actions that link Ziflow and monday.com.
Setting up monday.com automated flows
Once Ziflow and monday.com are connected, you can begin setting up automated flows to send information to monday.com. Start by going to the Connect tab and then Flows. To proceed, please locate and select the "Create Flow" button located at the upper right-hand corner of the screen.
Select Ziflow as the Application and choose which Event (new proof/version, decision made, new comment/reply, comment resolved, comment labeled) you want to trigger the integration.
You will be presented with the event details page, which will vary depending on your selected event. There are nine different types of events:
New proof/version
New proof/version
Triggered by - select the type of request that will trigger the Zibot.
Created in - select the Ziflow folder that this flow will monitor.
Created by - select the user responsible for this flow activation.
Created from - you can also select a source event from which the flow will be triggered: Ziflow, Adobe Creative Cloud, Asana, monday.com, Zibot intake form, Dropbox, Google Drive, or Final Cut Pro.
Proof updated
Proof updated
Triggered by - select the type of request that will trigger the Zibot. Use various events that might trigger the flow: folder change, proof settings updated, custom property edited, integration properties changed.
Modified in - select the Ziflow folder that this flow will monitor.
Decision made
Decision made
Triggered by decision made - select on what level a decision needs to be made to activate the flow. We might distinguish three different levels of decision: on proof, on stage, and by reviewer.
Type of decision - choose the type of decision that needs to be made to activate the flow.
Created in - select the Ziflow folder that this flow will monitor.
New comment/reply
New comment/reply
Triggered by new comment / new reply - please select whether a comment or a new reply should trigger the flow.
Made by - choose if a Zibot should be activated by a specific reviewer or anyone who adds a comment/reply.
Created in - select the Ziflow folder that this flow will monitor.
Comment resolved
Comment resolved
Created in - select the Ziflow folder that this flow will monitor.
Comment labeled
Comment labeled
Trigger by label made - please determine whether this event should prompt action based on adding labels to comments, replies, or both.
Comment is labeled as - select which label(s) should trigger a Zibot.
Created in - select the Ziflow folder that this flow will monitor.
Stage updated
Stage updated
Triggered by - select which type of the stage updated event should trigger the Zibot. There are three types of stage update events: reviewer added, reviewer removed, stage locked, and deadline changed.
Modified in - choose the Ziflow folder that this flow will monitor.
Stage started
Stage started
Triggered by - select which type of the stage updated event should trigger the Zibot.
Modified in - choose the Ziflow folder that this flow will monitor.
Comment reaction
Comment reaction
Triggered by - choose to start a flow based on reactions added to comments, replies, or both.
Comment reacted with - select what type of reaction should trigger a flow.
Created in - select the Ziflow folder that this flow will monitor.
Setting up monday.com Zibot action
After saving the event flow triggers, choose a monday.com Zibot action that will pass the information set in the previous step directly to monday.com:
Use the following Zibots:
1. Obtain monday.com items details - this Zibot is capable of collecting monday.com items details. These details can be helpful when configuring the next actions in your flow.
1. Obtain monday.com items details - this Zibot is capable of collecting monday.com items details. These details can be helpful when configuring the next actions in your flow.
2. Create monday.com item - adds a new item inside the selected board and group. Item name field can be entered using our built-in token selector.
2. Create monday.com item - adds a new item inside the selected board and group. Item name field can be entered using our built-in token selector.
3. Update monday.com item column - lets users update needed column based on board & column ID. You can either look for a column to be updated by selecting it from your board column list or use the result of the Search monday.com column on board action.
3. Update monday.com item column - lets users update needed column based on board & column ID. You can either look for a column to be updated by selecting it from your board column list or use the result of the Search monday.com column on board action.
4. Search monday.com board - you easily search through monday.com boards. Once you enter the board name, you can collect important details to be used in future Zibots.
4. Search monday.com board - you easily search through monday.com boards. Once you enter the board name, you can collect important details to be used in future Zibots.
5. Search monday.com group - with this Zibot you can search through monday.com groups if you need to find the item ID or item name.
5. Search monday.com group - with this Zibot you can search through monday.com groups if you need to find the item ID or item name.
6. Update monday.com item group - let's update the monday.com group item with data from Ziflow.
6. Update monday.com item group - let's update the monday.com group item with data from Ziflow.
7. Search monday.com item - To find a particular item on monday.com, simply enter its name in the search field. Additionally, you have the option to use a token selector to refine your search with some data from Ziflow e.g. proof name.
7. Search monday.com item - To find a particular item on monday.com, simply enter its name in the search field. Additionally, you have the option to use a token selector to refine your search with some data from Ziflow e.g. proof name.
8. Write update to monday.com item - lets you send an update to a particular monday.com item.
8. Write update to monday.com item - lets you send an update to a particular monday.com item.
9. Create monday.com subitem - adds a subitem under the chosen item in monday.com.
9. Create monday.com subitem - adds a subitem under the chosen item in monday.com.
10. Update monday.com item date column - it's useful when updating some date column on a specific item in monday.com.
10. Update monday.com item date column - it's useful when updating some date column on a specific item in monday.com.
11. Search monday.com column on a board - with this Zibot, you can easily search for column IDs. This allows the creation of flows that could update columns on different boards.
11. Search monday.com column on a board - with this Zibot, you can easily search for column IDs. This allows the creation of flows that could update columns on different boards.
12. Obtain monday.com user details - this Zibot allows searching for specific users in monday.com. You can enter multiple emails in this Zibot configuration and it will find users on monday.com. In the Emails field, you can enter multiple email addresses or use in-built tokens to capture emails directly from a proof. This information can be later used for other monday.com actions e.g. you can re-assign monday.com item ownership when proof status changes.
12. Obtain monday.com user details - this Zibot allows searching for specific users in monday.com. You can enter multiple emails in this Zibot configuration and it will find users on monday.com. In the Emails field, you can enter multiple email addresses or use in-built tokens to capture emails directly from a proof. This information can be later used for other monday.com actions e.g. you can re-assign monday.com item ownership when proof status changes.
Combining various actions with the events described earlier allows you to create flows capable of handling multiple integration use cases. Using events and actions (also known as Zibots) will facilitate the sending or updating of data within the designated monday.com account. Also, at the end of this article, you can find a few examples of flows that can show how we use our flows functionality.
Connect Ziflow proofs with monday.com tasks
Once you've connected monday.com to Ziflow, you can start linking proofs with the monday.com items from the Integrations tab while creating proofs or editing proof details.
It's important to keep in mind that to use integration fields while configuring or editing proofs, you must enable them in the application settings.
Connecting proofs with integration items is very quick and straightforward. During the proof configuration, open an integrations tab and select the monday.com item details (board and item).
monday.com flow examples
Automatically create monday.com items when the proof is generated and seamlessly populate application fields.
Before you start configuring the flow, please make sure to read the Ziflow internal Zibots article. This step is necessary because you need to connect Ziflow as an internal application in order to use it to update proofs.
Start creating a flow by selecting an event trigger which will be a New proof/version.
Choose the Create monday.com item from the Zibot list:
Fill out all necessary data in the Zibot configuration. In my example, I want to add a new item with a name of a newly added proof in Ziflow. I want to add this item to the Ziflow proofs board and inside the Proofs in progress group. Please note that you can use various tokens from the list (I went with a PROOF.NAME).
Please add two additional Zibots to the workflow. These Zibots should be internal Ziflow Zibots (Add proof integration property), and their purpose is to populate the application fields of a newly created proof with information sourced from monday.com.
The first of them will be populating the board ID into proof integration details.
The second one is responsible for filling out the monday.com item ID into Ziflow proof.
If you want the item to have a specific status, simply add another Zibot (Update monday.com item) and configure it accordingly. In my example, I decided that newly added items should be updated with the in-progress status on the monday.com side.
Create a proof that will trigger the automation and check if it created the item on the monday.com side, and then filled in application fields on a proof level.
Update the monday.com item status and move it to a different group when a proof decision is calculated.
1. Start creating a flow by selecting an event trigger which will be a Decision made. I selected an Accepted decision made on a proof level as a trigger for the whole flow.
2. Choose the Search monday.com item from the Zibot list:
3. Fill in the Zibot configuration details. I selected my main board, which is the Ziflow proof board, and used a token selector to select a proof name for the search query.
4. Add the next Zibot to Update monday.com item column.
5. Fill in all necessary fields at the Zibot configuration. I wanted the column to be updated with the Accepted value from the monday.com status field.
6. To complete our task, we need to update the item group on monday.com. Simply select Zibot from the list and customize it to suit your requirements.
7. Test if the flow works correctly by submitting a proof decision. The flow should be started, and the monday.com item should be moved to the new group.
Update monday.com item version and deadline fields when a new proof version is uploaded in Ziflow.
In this flow example, we will guide you through the process of updating item fields in monday.com. The process involves using the Search monday.com column on a board to collect the unique column ID. This ID can then be used in later steps to update specific items based on Ziflow events.
Start by creating a flow with New proof/version selected as an event. Inside the event configuration, please make sure to select only the new version setting.
Add your first action to the flow, which will be Search monday.com on a board Zibot. This Zibot will be responsible for collecting the monday.com version column ID. In order to pick the board ID, as shown in the GIF below, you need to have monday.com application fields populated to Ziflow proofs, as in this flow example.
The next action will be to update the monday.com item version field with the value collected from Ziflow. Select Update monday.com item column Zibot and configure it accordingly.
Your last flow action is Update monday.com item date column Zibot. This action will be responsible for updating the deadline field in the monday.com item.
Test your flow by uploading a new proof version. Please note that this process only works for proofs where Ziflow and monday.com application fields have already been linked.
Update monday.com item owner, status and move item to the next group when a proof is approved.
Start by creating a flow with a Decision made selected as an event. Inside the event configuration, please make sure to choose the type of decision on which you want the flow to be based. In the shown use case, the flow will trigger once there is an approved or approved change status on a proof level.
Add first Zibot to the flow. It should be an Obtain monday.com user details Zibot. This Zibot will look for entered email addresses in your monday.com and collect information that can be used later in the next actions. I typed in two email addresses of users on the monday.com account side.
The next Zibot you should add is the Update monday.com item column Zibot. This Zibot will update the monday.com item owner to the specified user from the previous action. The board and item ID entered in the Zibot configuration are coming from data that is already saved on a proof level (this flow example shows how you can do that).
Inside the email field at the Zibot configuration, please use the token selector to enter the first email address collected by the Obtain monday.com user details Zibot.
You can also refer to the next email addresses using a JSONata expression. For example, the following JSONata (#{$.zibot[0].data.data.users[1].email}#) refers to the second email saved in the Obtain monday.com user details Zibot.
Depending on your flow built, this JSONata can be updated to collect a specific email address from the Obtain monday.com user details Zibot. For example, if the Obtain monday.com user details Zibot is a second Zibot in the flow, and you want to collect information about the fourth email from the list, then the JSONata should look like this:#{$.zibot[1].data.data.users[3].email}#
The third Zibot (Update monday.com item group) of the whole flow will move the monday.com item from one board group to another. Inside the Zibot configuration, simply select the group where the item should be moved and fill in the Item ID information using a token selector.
Please add the last Zibot (Update monday.com item column) that will change the monday.com item status according to your use case. In this case, we want to mark it as Done.
Test if a flow works correctly by updating a proof status to match what's been configured in the flow event. The flow should trigger the whole automation. First, it will obtain monday.com user details, then update the owner to the selected monday.com user, update the item group, and then change its status.
Create a monday.com item, obtain the monday.com user details, and assign an item owner.
Start by creating a flow with a New proof/version selected as an event. Inside the event configuration, please choose the New proof as an event trigger.
Add the Create monday.com item Zibot. While setting the Zibot configuration, you need to select the board and board where items should be added. As a last step of the Zibot configuration, please specify the item name. You can use a built-in token to automatically retrieve a proof name. Every time a new monday.com is added through integration, the token will collect a corresponding proof name dynamically.
Next, please add the Obtain monday.com user details Zibot, which will collect a specified monday.com user's details. This information can later be used in the next flow actions. In this case I want the monday.com item owner to match the proof owner from Ziflow.
Please add the last Zibot (Update monday.com item column) to update the monday.com owner to a user collected by the previous action.
Save the flow and test if it works by adding a new proof in Ziflow. The automation should start a new monday.com item and assign a new owner matching the proof owner.
