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.
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 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.
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 who 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 this flow will monitor.
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 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 - 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 this flow will monitor.
Comment resolved
Created in - select the Ziflow folder that this flow will monitor.
Comment labeled
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 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 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.
Trello flow examples
Create Trello cards for newly created proofs 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.
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.
2. Add the Search Trello boards Zibot to your flow. Inside the Zibot configuration, I've typed "Board" because later I want to create cards in a board called "My company board".
3. Add the next Zibot, which is Search Trello lists. For the Board field, I used the outcome from the previous Zibot, which I selected from a token list. Inside query, I typed in because this is one of the lists that I use in my board. This is also the list where new cards will be added.
4. Next Zibot will be the Create a Trello card action. Use a token to pull the List ID from the previous Zibot. In the name field, I entered a proof name using a token, and inside the description, I decided to put the proof ID token.
5. The last Zibot in this flow will be the Create attachment on card action. It will add an attachment to the newly created card. Card ID can be pulled from the previous Zibot using a token selector. For the attachment URL, I used a proof public link also picked from a token selector.
6. Check if adding a new proof in your account will trigger automation.
Move Trello card when a proof is approved.
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 Trello boards Zibot. For the query field, I typed Board.
3. In the next step you'll need to add the Search Trello cards Zibot. Inside the Query field, please select Proof ID from a token selector.
4. Next should be the Search Trello lists Zibot. Please use an output ID from the Search Trello boards action or pick the board manually from the list. For a Query field, I entered Done because this is a list of where my card should be moved.
5. The last step of our flow will be an action to Move Trello cards to a list. For the Board field, please use the ID from the first Zibot (Search Trello boards) and enter the list ID inside a query field.
6. Save the flow and check if the card is moved to the configured list after the proof is created and the final status is calculated.