Integrating With monday.com instance Using Webhooks

Send Ziflow events to your monday.com using Webhooks.

Updated over a week ago

Summary: With our monday.com Webhook integration, you can extend your Ziflow online proofing operations to automatically create and update tasks in real-time updates in monday.com for new proofs, comments, decisions, and more to keep your team up to date in the tools they're already working in.

Available for: Users with Admin privileges on Enterprise edition.

Our Webhook Zibot allows you to trigger a flow when the following events occur on a proof:

  • New proof/version: triggers when a new proof is ready for review.

  • Decision: triggers when a decision is made by a reviewer or when a decision is updated on the stage and/or proof.

  • New comment/reply: triggers when a reviewer adds a comment/reply to the proof.

  • Comment resolved: triggers when a comment is marked as resolved.

  • Comment labeled: triggers when a reviewer labels a comment.

  • Proof updated: triggers when the proof folder, setting, or custom property changes.

  • Stage updated: triggers when a stage is started or when a reviewer is added/removed.
    ​

  • Comment reaction: triggers when a comment reaction is added on a comment/reply level.

Learn how to:


Create Ziflow Webhook Flow

To integrate monday.com with Ziflow, you need to click on the Connect tab and then click on the + Create Flow button, choose 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.

Create Ziflow Webhook Flow

Set up Flow Event settings

The first step is selecting the event that will trigger your Zibot:

Set up Flow Event settings in Ziflow

Next, you will be presented with the event details page, which will vary depending on which event you select:


New proof/version

New proof/version event settings in Ziflow
  1. Triggered by - select the type of request that will trigger the Zibot.

  2. Created in - select the Ziflow folder that this flow will monitor.

  3. Created by - select the user that will be responsible for this flow activation.


Decision made

Decision made event settings in Ziflow
  1. Triggered by decision made - select what level decision needs to be made to activate the flow.

  2. Type of decision - choose the type of decision that needs to be made to activate the flow.

  3. Created in - select the Ziflow folder that this flow will monitor.


New comment/reply added

New comment/reply added event settings in Ziflow
  1. Triggered by new comment / new reply - choose which option should activate the flow.

  2. Made by - choose if a Zibot should be activated by a specific reviewer or by anyone that adds a comment/reply.

  3. Created in - select the Ziflow folder that this flow will monitor.


Comment resolved

Comment resolved event settings in Ziflow
  1. Created in - select the Ziflow folder that this flow will monitor.


Comment labeled

Comment labeled event settings in Ziflow
  1. Comment is labeled as - select which label(s) should trigger a Zibot.

  2. Created in - select the Ziflow folder that this flow will monitor.


Proof updated

Proof updated event settings in Ziflow
  1. Triggered by - select which type of the proof updated event should trigger the Zibot.

  2. Modified in - choose the Ziflow folder that this flow will monitor.


Stage updated

Stage updated event configuration
  1. 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.

  2. Modified in - choose the Ziflow folder that this flow will monitor.


Comment reaction

Comment reaction event settings
  1. Triggered by - choose if you want to trigger a flow based on reactions added to comments or replies.
    ​

  2. Comment reacted with - select what type of reaction should trigger a flow.
    ​

  3. Created in - select the Ziflow folder that is going to be monitored by this flow.


Set up monday.com Webhook Zibot:

Next, choose a Webhook Zibot:

Set up monday.com Webhook Zibot in Ziflow

Add first Webhook with data that you want to pass over:

Add first monday.com Webhook with data that you want to pass over

Under Create, select POST. Under URL, type in "https://api.monday.com/v2?".

Under Headers, type in "Authorization" for the key and your Monday.com API key for the value (NOTE: if you don't have a Monday.com API token, you will need to access it from your monday.com account; please see the Additional Information below for more details).

Click +Add under Headers, for the key type in "Content-Type" and "application/json" for the value.

Copy the below SDK and update YourMondayBoardId (NOTE: if you do not know your monday.com Board ID, please see the Additional Information below for more details) in the Request body section.

To automatically create a new task on a board in monday.com when an event occurs on a proof in Ziflow:

{"query":"mutation {create_item (board_id: {YourMondayBoardId}, item_name: \"{$.proof.name}\"){board{id}, id}}","variables":null}

Add a second Webhook with data that you want to pass over:

Click + under the Webhook you just created to create another webhook.

Add a second monday.com Webhook with data that you want to pass over

Under Create, select POST. Under URL, type in "https://api.monday.com/v2?".

Under Headers, type in "Authorization" for the key and your monday.com API key for the value.

Click +Add under Headers, for the key type in "Content-Type" and "application/json" for the value.

Copy the below SDK Request body section.

{"query":"mutation {create_update (item_id: {$.zibot[0].data.data.create_item.id}, body: \"There is new proof to review: {$.proof.public_link} \") {id} }","variables":null}

Ener SDK request body to Zibot configuration

Once you hit the Next button, Ziflow will confirm if the flow looks good. If there are no problems, name the flow and turn it on.

image1-54

And you're done! Ziflow will now send automatically create a task to your designated Monday.com board.


Additional information:

Supporting Material:

Did this answer your question?