Summary: With our ClickUp integration, users can extend their Ziflow online proofing operations to ClickUp. Users can automatically create and update tasks in ClickUp 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 ClickUp
To integrate ClickUp 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, select ClickUp from the list. You'll be asked to authenticate with ClickUp credentials and then authorize Ziflow to access the ClickUp account.
Once this is done, you should see ClickUp integration on a connections list.
To enable ClickUp fields at the proof level, please go ahead and navigate to the connection settings and activate them by selecting the Show option.
Setting up ClickUp automated flows
Once Ziflow and ClickUp are connected, you can begin setting up automated flows to send information to ClickUp. 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 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 ClickUp Zibot action
After saving the event flow triggers, choose a ClickUp Zibot action that will pass the information set in the previous step directly to ClickUp:
Use the following Zibots:
Create ClickUp task - to add a new item to a selected workspace and project, simply specify the location within Clickup by selecting the appropriate dropdowns for workspace, space, folder, and list. Then, fill in the task name and description using the built-in token selector.
Search ClickUp list - with this Zibot, you can search for a ClickUp list. This Zibot will collect list ID, and based on that, you can add the next Zibots, which will use this information further.
Update ClickUp task - with this Zibot, you can, for example, update an already created ClickUp task when a new proof version is added to Ziflow.
Search ClickUp task - with this Zibot, you can search the required ClickUp task. This Zibot will collect task ID, and based on that, you can add the next Zibots, which will use this information further.
Comment ClickUp task - with this Zibot, you can post comments on the ClickUp tasks:
Update ClickUp custom field values - with this Zibot, you can update the values of the task's custom fields in ClickUp.
And you're done! Ziflow will now send or update data in the user's designated ClickUp account.
Connect Ziflow proofs with ClickUp tasks
Once you've connected ClickUp to Ziflow, you can manually link proofs with the ClickUp tasks from the Integrations tab while creating proofs or editing proof details.
It's important to remember that integration fields must be enabled in the application settings to be used while configuring or editing proofs.
Connecting proofs with integration tasks is very quick and straightforward. During the proof configuration, open an integrations tab and select the ClickUp task details (workspace, space, folder, list, and task).
ClickUp flow examples
Create a ClickUp task, populate application fields and set a task status upon new proof creation in Ziflow.
Once Ziflow is connected with ClickUp, you can start setting up ClickUp flows. With this flow example in place, newly created proofs in Ziflow will trigger flow, adding tasks on the ClickUp end.
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.
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 Trello flow.
3. Add the first Zibot Create a ClickUp task action. You can configure the Zibot to create a task within the selected space and list. For the task & description, please feel free to use in-built tokens. I used a proof name token and a description field which is a custom filed on a proof level.
4. Add another Zibot to the flow. This time it will be Update ClickUp task custom field values action. With this Zibot, you will be able to send necessary information for the selected custom field/column in ClickUp. At the card ID, I selected the card ID token coming from the first flow Zibot. For the custom field value (status column), I used a PROOF.DECISION.STATUS token using a token selector.
5. Please add another Zibot to the workflow. This Zibot should be an internal Ziflow Zibot (Update proof integration property). Its purpose is to populate the application fields of a newly created proof with information sourced from ClickUp.
6. Fill out the Update proof integration property Zibot configuration.
7. Save and turn on the flow as a last step of flow configuration.
8. Check if adding a new proof in your account will trigger automation.
