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:
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.
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
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 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
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.
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.
Add Basecamp text document - adds a next text document to the selected project & folder.
Create Basecamp project - allows adding a new project to your Basecamp instance.
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.
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:
Complete Basecamp todo - with this, Zibot users can complete the required todo in Basecamp:
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.
Basecamp flow examples
Add a new item and update the column
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. Name and save your flow.
5. Create a proof that will trigger the automation and check if the todo was added correctly in Basecamp
