ClickUp flow examples

Create a ClickUp task, populate application fields, and set a task status when new Ziflow proof is created

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.

Create a flow with a New Proof/Version as a flow event trigger

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.