Skip to main content
Integrating With Basecamp

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

Updated over a week ago

Summary: With our Basecamp integration, users can extend their Ziflow online proofing operations to Basecamp. Users can automatically create, complete to-do's/lists, and update tasks in Basecamp for new proofs, comments, decisions, and more to keep their team up to date in 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 Basecamp

To integrate Basecamp 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 Basecamp from the list.

Connecting Ziflow with Basecamp application

Once you authenticate in Basecamp and authorize Ziflow to connect with the Basecamp account, you can start setting up automated actions between Ziflow and Basecamp.

Basecamp application listed in your applications list

Setting up Basecamp automated flows

Once Ziflow and Basecamp are connected, you can begin setting up automated flows to send information to Basecamp. 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 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 configuration 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 that will be responsible for this flow activation.


Proof updated

Proof updated event configuration 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 configuration 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 configuration 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 configuration in Ziflow
  1. Created in - select the Ziflow folder that will be monitored by this flow.


Comment labeled

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

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


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 configuration 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 will 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 Basecamp Zibot action

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

Setting up Basecamp Zibot action in Ziflow

Use following Zibots

  1. Create Basecamp todo list - adds a new item inside the selected board and group. Item name field can be entered using our built-in token selector.

    Create Basecamp todo list Zibot configuration

  2. Add Basecamp todo - lets users update the needed column based on board & column ID from the previously added item in the same flow:

    Add Basecamp todo Zibot configuration

  3. Search Basecamp project - with this, Zibot users can search through Basecamp projects to find item ID or item name:

    Search Basecamp project Zibot configuration

  4. Complete Basecamp todo - with this, Zibot users can complete the required todo in Basecamp:

    Complete Basecamp todo Zibot configuration

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

Basecamp flow examples

Add a new item and update the column

1. Select the needed event trigger. In most cases, it will be a New Proof/Version event. This event will trigger once the new proof is created.

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

2. Choose Add Basecamp todo from the Zibot list:

Choose Add Basecamp todo Zibot from Zibot list

3. Fill out all necessary data in the Zibot configuration. In my example, I want to add a new todo which will be a proof name of a newly added proof in Ziflow. I want to add the Ziflow proof review todo to the Ziflow team project. Please note that you can use a variety of different tokens from the list (I went with a PROOF.NAME and PROPERTIES.[PROOF.DETAILS].[DESCRIPTION] as a proof description).

Fill out all necessary data in the Zibot configuration

4. Create a proof that will trigger the automation and check if the todo was added correctly in Basecamp

Create a proof that will trigger the automation and check if the todo was added correctly in Basecamp

Supporting Material:

Did this answer your question?