Summary: With our Trello integration, users can extend their Ziflow online proofing operations to Trello. Users can automatically create and update lists & tasks in Trello 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 Trello
This integration requires generating a Trello access token for Ziflow. To generate the token, please visit Trello website, allow Ziflow to read and update Trello data, and then copy the generated access token.
To integrate Trello 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 on the "Connect Application" button and select Trello from the list. You'll be asked to name the connection and enter Trello token access credentials.
Once this is done, you should see Trello integration on a connections list.
To enable Trello fields at the proof level, please go ahead and navigate to the connection settings and activate them by selecting the Show option.
Setting up Trello automated flows
Once Ziflow and Trello are connected, you can begin setting up automated flows to send information to Trello. 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 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 Trello Zibot action
After saving the event flow triggers, choose a Trello Zibot action that will pass the information set in the previous step directly to Trello:
Use the following Zibots:
Search Trello boards - with this Zibot, you can search Trello boards:
Create Trello card - with this Zibot, you can add new cards to your Trello lists:
Move Trello card to a list - with this Zibot, you can move a Trello card to a different list:
Search Trello cards - with this Zibot, you can search through Trello cards:
Search Trello lists - with this Zibot, you can search through Trello lists:
Send comment to a Trello card - with this Zibot, you can update the values of the task's custom fields.
Create attachment on a card - use this Zobot if you want to add any attachments to Trello cards:
And you're done! Ziflow will now send or update data in the user's designated Trello account.
Connect Ziflow proofs with Trello cards
Once you've connected Trello to Ziflow, you can start manually linking proofs with the Trello cards 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 Trello card details (workspace, board, and card).
Trello flow examples
Create a Trello card, populate application fields and upload attachments upon new proof creation in Ziflow.
Once Ziflow is connected with Trello, you can start setting up Trello flows. With this flow example in place, newly created proofs in Ziflow will trigger flow, adding cards on the Trello 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 Trello card action. You can configure the Zibot to create a card within the selected board and list. For the card name and 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 Create attachment on card action. With this Zibot, you will be able to include the original file image link under the card in Trello. At the card ID, I selected the card ID token coming from the first flow Zibot. For the attachment URL, you can use PROOF.DOWNLOAD_LINK 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 Trello.
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.
