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.

Available on: Pro & Enterprise editions.

• Follow instructions on how to:

  • Connect with Basecamp

  • Set up Basecamp automated flow

  • Set up Basecamp Zibot action

  • Connect Ziflow proofs with Basecamp todos'

  • Basecamp flow examples
    ​

  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 click on the Applications tab on the left. Once inside the Applications menu, select Basecamp from the list. You'll be asked to authenticate with Basecamp credentials and then authorize Ziflow to access the Basecamp account.

   

  

   

  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.

   

  

  To enable Basecamp fields at the proof level, please go ahead and navigate to the connection settings and activate them by selecting the Show option.

   

  

   

  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.

   

  

   

  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

  • Proof Updated

  • Decision made

  • New comment/reply

  • Comment resolved

  • Comment labeled

  • Stage updated

  • Stage started

  • Comment reaction

   

  New proof/version

   

  

  1. Triggered by - select the type of request that will trigger the Zibot.

      

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

      

  3. Created by - select the user responsible for this flow activation.
     ​

  4. 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

   

  

  1. 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.

      

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

   

  Decision made

   

  

  1. 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.

      

  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 this flow will monitor.

   

  New comment/reply

   

  

  1. Triggered by new comment / new reply - please select whether a comment or a new reply should trigger the flow.

      

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

      

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

   

  Comment resolved

   

  

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

   

  Comment labeled

   

  

  1. Trigger by label made - please determine whether this event should prompt action based on adding labels to comments, replies, or both.
     ​

  2. Comment is labeled as - select which label(s) should trigger a Zibot.

      

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

   

  Stage updated

   

  

  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

   

  

  1. Triggered by - select which type of the stage updated event should trigger the Zibot.

      

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

  Comment reaction

   

  

  1. Triggered by - choose to start a flow based on reactions added to comments, replies, or both.
     ​

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

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

   

   

  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:

   

  

   

  Use following Zibots

  1. Add Basecamp todo list - adds a new item inside the selected project and todoset. List name and list description fields can be entered using our built-in token selector.
     ​

     

      

  2. Create Basecamp folder - add a new folder to the selected project & folder set. The folder name field can be entered using our built-in token selector.
     ​

     

      

  3. Add Basecamp text document - adds a next text document to the selected project & folder.
     ​

     

     
     ​

  4. Create Basecamp project - allows adding a new project to your Basecamp instance.
     ​

     

     
     ​

  5. Add Basecamp todo - this Zibot can be used for adding new todos' to your Basecamp account. Todo name and todo description fields can be entered using our built-in token selector.

      

     

      

  6. Search Basecamp project - with this, Zibot users can search through Basecamp projects to find relevant projects and then use it to build follow-up actions:

      

     

      

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

     

      

  8. Update Basecamp todo - this allows updating already existing todo with new information, e.g., upon new proof version in Ziflow.

      

     

      

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

   

   

  Connect Ziflow proofs with Basecamp todos'

   

  Once you've connected Basecamp to Ziflow, you can start linking proofs with the Basecamp items 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 items is very quick and straightforward. During the proof configuration, open an integrations tab and select the Basecamp todo details (Project, Todo set, Todo list, and item).

   

  

   

   

  Basecamp flow examples

   

  Automatically create Basecamp todo when the proof is generated, seamlessly populate application fields, and update the status column.

  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. Select the needed event trigger. In this case, it will be a New Proof/Version event. This event will trigger every time a new proof is created.
  ​

  

   

  2. Choose Add Basecamp todo from the 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 proofs 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].[REVIEW TYPE] as a todo description).

   

  

   

  4. Next, you must add three internal Ziflow Zibots (Update proof integration property). They aim to populate the application fields (Account ID, Project ID, Todo Set ID, Todo List ID & Todo ID) of a newly created proof with information sourced from Basecamp.
  ​

  

   

  5. Fill out the Update proof integration property Zibots configuration.

  

  
  4. Name and save your flow.

   

  

   

  5. Create a proof to trigger the automation and check if the todo was added correctly in Basecamp.

   

  

  
  ​

  Supporting Material:

  • API Reference Page

• 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.

   

  Follow instructions on how to:

  • Connect with Basecamp

  • Set up Basecamp automated flow

  • Set up Basecamp Zibot action

  • Basecamp flow examples
    ​

  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.

   

  

  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.

   

  

   

   

  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.

   

  

  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

  • Proof Updated

  • Decision made

  • New comment/reply

  • Comment resolved

  • Comment labeled

  • Stage updated

  • Stage started

  • Comment reaction

   

  New proof/version

   

  

  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

   

  

  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

   

  

  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

   

  

  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

   

  

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

   

  Comment labeled

   

  

  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

   

  

  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

   

  

  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

   

   

  

  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:

   

  

  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.

      

     

      

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

      

     

      

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

      

     

      

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

      

     

  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.

   

  

  2. Choose Add Basecamp todo from the 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).

   

  

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

   

  

  Supporting Material:

  • API Reference Page