Summary: Our integration for Slack lets you extend your Ziflow online proofing operations to include real-time Ziflow notifications in Slack for new proofs, comments, decisions, and more to keep your team up to date with the tools they're already working in.
Available on: Pro & Enterprise editions.
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 Slack
To integrate Slack 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 Slack from the list. You'll be asked to authenticate with Slack credentials and then authorize Ziflow to access the Slack account.
To enable Slack 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 Slack and granting Ziflow permission to connect with your Slack account, you can begin configuring automatic actions that link Ziflow and Slack.
Slack integration can function effectively on both public and private channels within your Slack workspace.
In order to integrate Ziflow with Slack's private channels, you need to, install the Ziflow app and then add the Ziflow app to the channels you want to use.
Set up Ziflow automated flows for Slack integration
Once Ziflow and Slack are connected, you can begin setting up automated flows to send information to Slack. Start by going to the Connect tab and then Flows. To proceed, please locate and select the "Create Flow" button at the screen's upper right-hand corner.
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
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
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
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
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
Created in - select the Ziflow folder that this flow will monitor.
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
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
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
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.
Set up Ziflow Zibot for Slack action
After saving the event flow triggers, choose a Slack Zibot action that will pass the information set in the previous step directly to Slack:
Use following Zibots:
Search Slack channel - with this, Zibot, you can search for a specific Slack channel (public or private). Later on, you can utilize the collected channel details for future actions.
Create Slack channel - adds a new Slack channel:
Send to Slack channel - allows sending a message to a chosen Slack channel (public or private). Start sending messages using various types of layouts. Slack Block Kit Builder lets you create rich, interactive UI for your messages.
Example of the blocks layout body you may use for your Slack message:
[
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Hello! New proof #{$.proof.name}# has been published in Ziflow."
}
},
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "View the proof by clicking on the Open Proof button down below."
}
},
{
"type": "divider"
},
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Please be aware that you may be asked to sign in to Ziflow before accessing the proof."
},
"accessory": {
"type": "button",
"text": {
"type": "plain_text",
"text": "Open Proof",
"emoji": true
},
"value": "click_me_123",
"url": "#{$.proof.public_link}#",
"action_id": "button-action"
}
}
]
Send to Slack user - allows sending a message to the specific Slack user. Start sending messages using various types of layouts. Slack Block Kit Builder lets you create rich, interactive UI for your messages.
Invite to Slack channel - with this Zibot, you can automatically invite a specific user to a Slack channel (public or private).
Invite Ziflow app to private channel - it's a one-time action that can invite the Ziflow app to any private channel. This will let you use other Slack actions in a private channel in your Slack workspace.
Obtain Slack user by email - this Zibot can be used to retrieve a Slack user ID. It's useful for creating flows that can locate and message specific users.
And, you're done! Ziflow will now send or update data in your designated Slack
account.
Set up Ziflow Webhook for Slack connection
After saving the event flow triggers, choose Webhook Zibot action:
Under Create, select POST. Under URL, copy the Webhook URL for your Workspace in Slack (NOTE: if you don't have a Webhook URL for your Workspace in Slack, you may need to create a Slack app and an Incoming Webhook). You can use your request body or copy/paste one of our examples below.
Create - select the type of request.
URL (required) - enter the application URL where you will send the data.
Query String Parameters - add which parameters you want to send.
Request body - you can use example requests posted below or create your own using JSON format (you can also use Slack formatting tool for testing how your message will look directly in-app).
Headers - enter the header values for each request.
For a New Proof Notification:
{
"attachments": [
{
"fallback": "Hi, there is one new proof to review.",
"color": "#1A18AB",
"pretext": "Hi, there is one new proof to review.",
"author_name": "{$.proof.owner.first_name} {$.proof.owner.last_name}",
"title": "{$.proof.name}",
"title_link": "{$.proof.public_link}",
"thumb_url": "{$.proof.thumbnail_link}"
}
]
}
For a New Comment or Reply:
{
"attachments": [
{
"fallback": "Hi, a new comment has been made.",
"color": "#dc9d3e",
"pretext": "Hi, a new comment has been made.",
"author_name": "{$.comment.reviewer.email}",
"title": "{$.proof.name}",
"title_link": "{$.proof.public_link}",
"thumb_url": "{$.proof.thumbnail_link}",
"text": "{$.comment.comment}"
}
]
}
For a Decision Made Notification:
{
"attachments": [
{
"fallback": "Hi, a new decision has been made.",
"color": "#2092e3",
"pretext": "Hi, a new decision has been made.",
"author_name": "{$.reviewer.email}",
"title": "{$.proof.name}",
"title_link": "{$.proof.public_link}",
"thumb_url": "{$.proof.thumbnail_link}",
"text": "{$.reviewer.decision_status}"
}
]
}
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.
And you're done! Ziflow will now send or update data in your designated Slack
account.
Connect Ziflow proofs with the Slack channel.
Once you've connected Slack to Ziflow, you can start linking proofs with the Slack channels from the Integrations tab while creating 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 Slack channel details.
Ziflow flow examples for Slack
Send Ziflow notifications to Slack about proof being created and link the proof with a relevant Slack channel.
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 Send to Slack channel from the Zibot list:
Fill out all necessary data in the Zibot configuration. In my example, I want to send a message to the ziflow-proofs channel. I decided to include some custom message to the notification along with a proof public URL to open the proof in Ziflow.
Please add another Zibot to the workflow. This Zibot should be an internal Ziflow Zibot (Update proof integration property), and its purpose is to populate the application fields of a newly created proof with information sourced from Slack.
Fill out the Update proof integration property Zibot configuration.
Save the flow and create a proof that will trigger the automation. Please ensure that a notification has been sent to the designated Slack channel, and verify that all fields in the Integrations tab have been filled out correctly on a proof level.
Send Ziflow notifications to Slack whenever someone uses @mention in Ziflow.
Select the needed event trigger. In this case, it will be a New Comment/Reply event. This event will trigger once a new comment or reply is added to the proof.
Click next and select a path action from the Zibot list.
For the path details, please fill out the Rules as shown in the screenshot below:
Click next and select the Obtain Slack User by email Zibot.
Fill out the email field at the Zibot configuration with the following expression:
#{$.proof.stages.members[id=$match($$.comment.comment, /\$\{reviewer:([a-f0-9-]+)\}/)[0].groups[0]].email}#Add another Zibot to the flow, which will be the Send to Slack user action.
Now, enter the user ID collected from the previous action to the User ID field. For the text message, I included some tokens so the user can see some details related to the mention.
Test if the flow works by using @mention on someone from your Slack workspace and see if they were notified about that fact in the Slack app.
Here's how the notification will look like inside the Slack application:
Adding the Ziflow app to your Slack channels
In order to allow Ziflow to send messages to your private channels, you need to invite the Ziflow app first. To ensure uninterrupted automation between Ziflow and Slack, it is important to make sure that the Ziflow app is added to your private channels.
Adding the Ziflow app to Slack channels is quick and straightforward, but if you need any help with that, please check the Slack Help Center for more details (Guide to apps in Slack & Add apps to your Slack workspace).
Supporting Material:
The Ziflow-Slack Webhook Integration requires you to create an Incoming Webhook and a Slack app.
When connecting with Webhooks, you can test your request body using the Slack message formatting tool.
Please also take a look at our Privacy Policy, which informs how Ziflow gathers, uses, discloses, and manages a customer's data.