Integrating With Asana

Connect Ziflow and Asana to automate the syncing of review progress with Asana.

Updated over a week ago

Summary: With our Asana integration, users can extend their Ziflow online proofing operations to Asana. Users can automatically create, update & assign tasks in Asana 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 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 Asana

To integrate Asana 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 Asana from the list. You'll be asked to authenticate with Asana credentials and then authorize Ziflow to access the Asana account.

Connect Ziflow with Asana application

Once this is done, you should see Asana integration on a connections list.


Setting up Asana automated flows

Once Ziflow and Asana are connected, you can begin setting up automated flows to send information to Asana. Start by going to the Connect tab and by clicking on the Create Flow button in the upper right corner of the screen.

Create flow button in Ziflow

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.

Select Ziflow event type that will trigger the flow

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

New proof/version event settings in Ziflow
  1. Triggered by - select the type of request that will trigger the Zibot.

  2. Created in - select the Ziflow folder that will be monitored by this flow.

  3. Created by - select the user who will be responsible for this flow activation.


Proof updated

Proof updated event settings in Ziflow
  1. Triggered by - select the type of request that will trigger the Zibot.

  2. Modified in - select the Ziflow folder that will be monitored by this flow.


Decision made

Decision made event settings in Ziflow
  1. Triggered by decision made - select what level decision needs to be made to activate the flow.

  2. Type of decision - choose the type of decision that needs to be made to activate the flow.

  3. Created in - select the Ziflow folder that will be monitored by this flow.


New comment/reply

New comment/reply event settings in Ziflow
  1. Triggered by new comment / new reply - choose which option should activate the flow.

  2. Made by - choose if a Zibot should be activated by a specific reviewer or by anyone that adds a comment/reply.

  3. Created in - select the Ziflow folder that will be monitored by this flow.


Comment resolved

Comment resolved event settings in Ziflow
  1. Created in - select the Ziflow folder that will be monitored by this flow.


Comment labeled

Comment labeled event settings in Ziflow
  1. Comment is labelled as - select which label(s) should trigger a Zibot.

  2. Created in - select the Ziflow folder that this flow will monitor.


Stage updated

Stage updated event configuration
  1. 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.

  2. Modified in - choose the Ziflow folder that this flow will monitor.


Stage started

Stage started event settings in Ziflow
  1. Triggered by - select which type of the stage updated event should trigger the Zibot.

  2. Modified in - choose the Ziflow folder that is going to be monitored by this flow.


Comment reaction

Comment reaction event settings
  1. Triggered by - choose if you want to trigger a flow based on reactions added to comments or replies.

  2. Comment reacted with - select what type of reaction should trigger a flow.

  3. Created in - select the Ziflow folder that is going to be monitored by this flow.


Setting up Asana Zibot action

After saving the event flow triggers, choose an Asana Zibot action that will pass the information set in the previous step directly to Asana:

Setting up Asana Zibot action in Ziflow

Use the following Zibots:

  1. Create Asana task - adds a new item inside the selected workspace and project. The Item name and Task description field can be entered using our built-in token selector.

    Create Asana task Zibot configuration

  2. Search Asana - with this Zibot, you can search for projects, tasks, and users.

    Search Asana Zibot configuration

  3. Update Asana task - with this Zibot, you can update the required task in the Asana workspace.

    Update Asana task Zibot configuration

  4. Update Asana task column - with this Zibot, you can update the required Asana task column.

    Update Asana task column Zibot configuration


  5. Update Asana task section - with this Zibot, you can update the required Asana task section.

    Update Asana task section Zibot configuration

  6. Assign Asana task - with this Zibot, you can assign the required Asana task.

    Assign Asana task Zibot configuration

  7. Send proof URL - this Zibot will attach a proof URL as an external attachment to the selected Asana task.

  8. Create a story (comment) on Asana task - this Zibots lets you add stories (comments) to selected Asana tasks.

    Create a story (comment) on Asana task Zibot


And you're done! Ziflow will now send or update data in users' designated Asana account.

Supporting Material:

Did this answer your question?