Summary: Our Microsoft Teams integration allows users to extend their Ziflow online proofing operations to Microsoft Teams. Users can automatically post messages or create channels in Microsoft Teams for new proofs, comments, decisions, and more to keep their team up to date with the tools they're already using. Please note that this integration supports just MS Teams for Work & School.
This article outlines how described functionality appears and operates in the old layout. If you are using Dashboard 2.0, please refer to the corresponding article in the Help Center.
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 Microsoft Teams
To integrate Microsoft Teams with Ziflow, open the Connect tab in the Ziflow account and then click on the Applications tab on the left. Once inside the Applications menu, click the "Connect Application" button and select Microsoft Teams from the list. You'll be asked to authenticate with O365 credentials and then authorize Ziflow to get access to your Microsoft account.
Once you authenticate in Microsoft Teams and authorize Ziflow to connect with the O365 account, you can start setting up automated actions between Ziflow and Microsoft Teams.
Setting up Microsoft Teams automated flows
Once Ziflow and Microsft Teams are connected, you can begin setting up automated flows to send information to MS teams. Start by going to the Connect tab and by clicking on the Create Flow button in the upper right corner of the screen.
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.
You will be presented with the event details page, which will vary depending on which event you selected. 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 who will be responsible for this flow activation.
Proof updated
Triggered by - select the type of request that will trigger the Zibot.
Modified in - select the Ziflow folder that this flow will monitor.
Decision made
Triggered by decision made - select what level decision needs to be made to activate the flow.
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 - choose which option should activate the flow.
Made by - choose if a Zibot should be activated by a specific reviewer or by anyone that 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
Comment is labelled 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 if you want to trigger a flow based on reactions added to comments or replies.
Comment reacted with - select what type of reaction should trigger a flow.
Created in - select the Ziflow folder that is going to be monitored by this flow.
Setting up Microsoft Teams Zibot action
After saving the event flow triggers, choose a Microsoft Teams Zibot action that will pass the information set in the previous step directly to Teams:
Use the following Zibots:
Search Team - with this, Zibot users can search through the MS Teams team.
Search Channel - with this, Zibot users can search through the MS Teams channels. This allows collection channel ID so it can be used in next flow actions.
Send to Channel - with this Zibot, users can send messages to MS Teams channels:
Create Channel - with this Zibot, users can create a new channel in MS Teams.
And you're done! Ziflow will now send in your designated MS Teams channel.
Microsoft Teams flow examples:
Send a message to MS Teams when a new proof is created.
1. Select the needed event trigger. In most cases, it will be a New Proof/Version event. This event will trigger once the new proof is created:
2. Choose the Send to channel Zibot from a list:
3. Fill out all necessary data in Zibot configuration. In my example, I want to send a message to the Channel for testing MS-Ziflow integration in Ziflow Ltd Team. The message will contain a proof name (PROOF.NAME) and proof owner name (PROOF.OWNER.FIRST_NAME & PROOF.OWNER.LAST_NAME).
4. Create a proof that will trigger the automation and check if the message was posted on the MS Teams channel:
