Summary: With our Wrike integration, users can extend their Ziflow online proofing operations to Wrike. Users can automatically create and update tasks in Wrike for new proofs, comments, decisions, and more to keep their team up to date with the tools they're already using.
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 Wrike
To integrate Wrike with Ziflow, follow these steps:
Open your Ziflow account and navigate to the Connect tab.
Click on the Applications tab located on the left side of the screen.
Inside the Applications menu, click on the "Connect Application" button.
From the list of available applications, select Wrike.
Enter your Wrike account credentials.
Follow the authorization request to complete the process of connecting Ziflow and Wrike together.
Once this is done, you should see Wrike integration on a connections list.
Setting up Wrike automated flows
Once Ziflow and Wrike are connected, you can begin setting up automated flows to send information to Wrike. Start by going to the Connect tab and by clicking on the Create Flow button in the upper right 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 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 will be monitored by this flow.
Created by - select the user that 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 will be monitored by this flow.
Decision made
Triggered by decision made - select what level decision needs to be made in order to activate the flow.
Type of decision - choose the type of decision that needs to be made in order to activate the flow.
Created in - select the Ziflow folder that will be monitored by this flow.
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 will be monitored by this flow.
Comment resolved
Created in - select the Ziflow folder that will be monitored by this flow.
Comment labeled
Comment is labeled as - select which label(s) should trigger a Zibot.
Created in - select the Ziflow folder that will be monitored by this flow.
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 will be monitored by this flow.
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 Wrike action
After saving the event flow triggers, choose a Wrike Zibot action that will pass the information set in the previous step directly to Wrike:
Use the following Zibots:
Search Wrike folders - with this Zibot, you can search Wrike folders. Simply type in the folder name that you are looking for, and in the next step, you can use this information to make further updates.
Search Wrike task - with this Zibot, you can search for specific Wrike tasks. Simply type in the task name that you are looking for, and in the next step, you can use this information to make further updates.
Create Wrike task - with this Zibot, you can add new tasks to your Wrike folders/projects. Specify the folder where the task should be added, the task title & task description.
Update Wrike task - with this Zibot, you can update the Wrike task with changes from Ziflow:
Update Wrike custom field - with this Zibot, you can update the values of custom fields added to specific tasks.
Add Wrike comment - with this Zibot, you can post comments to specific Wrike tasks.
And you're done! Ziflow will now send or update data in the user's designated Wrike account.
Wrike flow examples
Create Wrike tasks for newly created proofs in Ziflow.
Once Ziflow is connected to Wrike, you can seamlessly set up Wrike flows. With this flow example implemented, any newly created proofs in Ziflow will automatically trigger a corresponding flow, effortlessly adding tasks on the Wrike end.
1. Create a new flow and select the needed event trigger. In this case, it will be a New Proof/Version. You can narrow down proofs that will trigger the automation by configuring event settings. In my case, each created proof should trigger the Wrike flow.
2. Add the Create Wrike task Zibot to your flow. Inside the Zibot configuration, select the folder where the task should be automatically added and also specify what should be entered in a task title field and in the task description.
3. Check if adding a new proof in your account will trigger automation.
Update Wrike task status when a proof is Accepted.
1. Create a new flow with Ziflow as an application. The Decision made event trigger should be selected. I've selected the Approved decision on a proof level in configuration. You may use a different configuration that works for your use case.
2. Add the Search Wrike task Zibot. For the query field, please select PROOF.NAME from a token selector.
3. In the next step, you'll need to add the Update Wrike task Zibot. Inside the Task ID field, please select a token containing Wrike task ID from a previous Zibot. In the task title, I decided to leave the proof name and change the task status to Completed.
4. Save the flow and check if the task status is updated after the proof's final status is calculated.
Post a comment to the Wrike task when a new proof fails.
1. Create a new flow and select the needed event trigger. In this case, it will be a New Proof/Version. You can narrow down proofs that will trigger the automation by configuring event settings. In my case, each failed proof in Ziflow should trigger the Wrike flow.
2. Add the Search Wrike task Zibot. For the query field, please select PROOF.NAME from a token selector.
3. In the next step, you'll need to add the Add Wrike comment Zibot. Inside the Task ID field, please select a token containing the Wrike task ID from a previous Zibot. In the comment text field, I decided to enter a token that will contain a proof ID so I can reach out to Ziflow support if needed.
