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.
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.
From the list of available applications, select Wrike. This will open up a a flyout window where you should click on a Connect button.
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. To enable Wrike fields at the proof level, please go ahead and navigate to the connection settings and activate them by selecting the Show option.
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 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
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.
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.
Connect Ziflow proofs with Wrike tasks
Once you've connected Wrike 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 Wrike item details (project/folder and task).
Wrike flow examples
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.
Create Wrike tasks for newly created proofs in Ziflow and seamlessly populate application fields.
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. Next, you must add two internal Ziflow Zibots (Update proof integration property). They aim to populate the application fields (Project ID & Task ID) of a newly created proof with information sourced from Wrike.
5. Fill out the Update proof integration property Zibots configuration.
6. Check if adding a new proof in your account triggers the flow and populates fields on a proof level.
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.
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. 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 calculating the proof's final status.
