Use these automation flows to keep Basecamp in step with your proof reviews. Each example lists what to enter in every field. Change the folders, projects, and text to match your team.

Available on: Pro Enterprise

Prerequisites

• Connect Basecamp to Ziflow and set Application fields on a proof to Show. See Connect to Basecamp.
• Connect the Ziflow application. See Connect your Ziflow app.

If you reconnect Basecamp, Ziflow adds a new connection with the same name, and existing flows keep using the old one. Open each Basecamp Zibot and select the new connection in Application.

Basic flow creation

1. Select Connect in Ziflow's main navigation and select Create Flow.
2. Select Ziflow as your flow's application.
3. Enter a name for your flow.
4. Select the event that starts the flow. See Ziflow events.
5. Add Basecamp Zibots to the flow.
6. Select Save & Turn on.

Create a Basecamp to-do when a proof is created

When someone uploads a proof to the Campaigns folder, Ziflow adds a to-do to the campaign's Basecamp list. The flow then links the to-do to the proof, so other flows can update or complete it.

1. Create a flow named Create Basecamp to-do for new proofs.

2. Select the New proof/version event and configure it:

   Field	What to enter
   Triggered by	New proof only. Clear New version, or the flow adds a to-do for every version.
   Created in	Your campaign folder, for example Campaigns
   Created by	Anyone
   Created from	Leave empty to include proofs from any source.

3. Select Next, select the Add Basecamp todo Zibot, and configure it:
   
   

   Field	What to enter
   Account	Your Basecamp account
   Which Project the todo should be created on	Select from projects in the account
   Select project	The campaign's project
   Select Todo set	To-dos
   Select Todo List	The list for reviews, for example Creative reviews
   Todo name	Insert Proof > Name, then type - review in progress
   Todo description	Insert Proof > Public link, then type - open this link to review the proof in Ziflow.

4. Select Next. Select +, select the Add or update proof integration property Zibot, and configure it:
   
   

   Field	What to enter
   Proof ID	PROOF.ID (added for you)
   Select application	Basecamp
   Select connection	Your Basecamp connection
   Select integration property group	Basecamp todo details
   Select integration property	Todo
   Integration property value	Insert Add Basecamp todo > ID

5. Repeat step 4 to add three more Add or update integration property Zibots, configured the same way except for these two fields:

   Select integration property	Integration property value
   Account	Add Basecamp todo > Account ID
   Project	Add Basecamp todo > Project
   Todo List	Add Basecamp todo > TODO list

6. Select Save & Turn on.

7. Upload a test proof to the folder. Check that the to-do appears in Basecamp and that the proof's Integrations tab shows the Basecamp to-do.

Update the Basecamp to-do when a new version is uploaded

When someone uploads a new version, Ziflow updates and replaces the linked to-do's description with a link to the new version, so the Basecamp team knows there's something new to review.

1. Create a flow named Update Basecamp to-do on new version.

2. Select the New proof/version event. Set Triggered by to New version only and Created in to the same folder.

3. Select Next, select the Update Basecamp todo Zibot, and configure it:

   Field	What to enter
   Account	Your Basecamp account
   Which Project the todo should be updated on	Provided from previous action or direct ID
   Project ID	Insert Basecamp todo details > Project
   Todo List ID	Insert Basecamp todo details > Todo List
   Todo Item ID	Insert Basecamp todo details > Todo
   Todo Item description	Insert Proof > Public link, then type - a new version is ready for review.

4. Select Save & Turn on.

Update Basecamp todo replaces the to-do's description. Include everything the description should say.

Complete the Basecamp to-do when a proof is approved

When a proof's final decision is Approved or Approved with changes, Ziflow checks off the to-do linked to it. 

1. Create a flow named Complete Basecamp to-do when proof is approved.

2. Select the Decision update event and configure it:

   Field	What to enter
   Triggered by decision	On a proof, so the flow waits for the proof's overall decision
   Type of update	Approved and Approved with changes
   Created in	The same folder

3. Select Next, select the Complete Basecamp todo Zibot, and configure it:
   
   

   Field	What to enter
   Account	Your Basecamp account
   Which Project the todo should be completed on	Provided from previous action or direct ID
   Project ID	Insert External applications > Basecamp > Basecamp todo details > Project
   Todo ID	Insert External applications > Basecamp > Basecamp todo details > Todo

4. Select Save & Turn on.

Add a revisions to-do when changes are required

When a proof's final decision is Changes required, Ziflow adds a new to-do to the same list, so the designer knows there's work to do.

1. Create a flow named Add a revision to-do when changes are required.

2. Select the Decision update event and configure it:

   Field	What to enter
   Triggered by decision	On a proof, so the flow waits for the proof's overall decision
   Type of update	Changes required
   Created in	The same folder

3. Select Next, add the Add Basecamp todo Zibot:

   Field	What to enter
   Account	Your Basecamp account
   Which Project the todo should be created on	Provided from previous action or direct ID
   Project ID	Insert Bascamp todo details > Project
   Todo List ID	Insert Bascamp todo details > Todo List
   Todo name	Insert Proof > Name, then type - revisions needed
   Todo description	Insert Proof > Public link, then type - changes were requested. Review the comments and upload a new version.

4. Select Save & Turn on.

Save an approval record to the project

When a proof is approved, Ziflow adds a document to the project's Docs & Files, so the team has a record of what was approved and where to find it.

1. Create a flow named Save an approval record to the project.

2. Create a flow with the Decision update event, configured as in Complete the Basecamp to-do when a proof is approved.

3. Select the Add Basecamp text document Zibot and configure it:
   
   

   Field	What to enter
   Account	Your Basecamp account
   Which Project the document should be created in	Select from projects in the account
   Select project	The campaign's Basecamp project
   Which folder the document should be created on	Main project folder
   Select folder set	Docs & Files
   Document title	Insert Proof > Name, then type - approved
   Document content	Insert Proof > Public link, then type - approved in Ziflow. Open the link to see comments, decisions, and version history.

4. Select Save & Turn on.

You can add this Zibot and Complete Basecamp todo to the same flow instead of building two flows.

Add the to-do to the project that matches the folder name

If each campaign has a Ziflow folder and a Basecamp project with the same name, one flow can send proofs from every campaign folder to the right project. Because Search Basecamp Project doesn't return a to-do list, this flow creates a new list for each proof and adds the to-do to it.

1. Create a flow named Add the to-do to project matching folder name.

2. Select the New proof/version event. Set Triggered by to New proof only, and Created in to the campaign folder. The folder name must match the Basecamp project name exactly.

3. Add the Search Basecamp Project Zibot:
   
   

   Field	What to enter
   Account	Your Basecamp account
   Search project query	Insert Proof > Folder > Name

4. Add the Add Basecamp todo list Zibot:

   Field	What to enter
   Account	Your Basecamp account
   Which Project the list should be created on	Provided from previous action or direct ID
   Project ID	Insert Search Basecamp Project > Project ID
   List set ID	Insert Search Basecamp Project > Todo list set data > Todo list set ID
   List name	Insert Proof > Name

5. Add the Add Basecamp todo Zibot:

   Field	What to enter
   Account	Your Basecamp account
   Which Project the todo should be created on	Provided from previous action or direct ID
   Project ID	Insert Search Basecamp Project > Project ID
   Todo List ID	Insert Add Basecamp todo list > Todo list ID
   Todo name	Insert Proof > Name
   Todo description	Insert Proof > Public link

6. Select Save & Turn on.

If no Basecamp project matches the folder name, the flow fails for that proof. See Troubleshoot failed flows.

Related articles

• Connect to Basecamp
• Ziflow events
• Ziflow Zibots
• Troubleshoot failed flows