Integrating With Google Drive

Connect Ziflow and Google Drive to automate the syncing of proof progress with Google Drive. Pro & Enterprise edition only.

Updated over a week ago

Summary: With our Google Drive SDK Integration, you are able to extend your Ziflow online proofing operations to include real-time synchronization between Ziflow & Google Drive for new proofs, comments, decisions, and more to keep your team up to date in the tools they're already working in.

Follow instructions on how to:


How to connect with Google Drive

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

Connecting Ziflow with Google Drive

After authenticating in Google Drive and granting Ziflow access to your account, you can establish automated actions between the two platforms.

Google Drive connection appears on your connections list

Please note that you must enable application fields for the Google Drive app to connect Ziflow proofs with Google Drive files via a special field in proof details.

Enable application fields for Google Drive integration in Ziflow

Setting up Google Drive automated flows

Once Ziflow and Google Drive are connected, you can begin setting up automated flows to send information to Google Drive. 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 your selected event. 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 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

Proof updated event settings in Ziflow
  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

Decision made event settings in Ziflow
  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

New comment/reply event settings in Ziflow
  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

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


Comment labeled

Comment labeled event settings in Ziflow
  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

Stage updated event settings in Ziflow
  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 this flow will monitor.


Comment reaction

Comment reaction event settings
  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 Google Drive Zibot action

After selecting the event flow triggers, select a Zibot action for Google Drive that will directly pass the information from the previous step to Google Drive:

Setting up Google Drive Zibot action in Ziflow

Use following Zibots

  1. Create a Google Drive folder - adds a new Google Drive folder.

    Create a Google Drive folder Zibot configuration

  2. Search Google Drive file - search for a specific file using its name.

    Search Google Drive file Zibot configuration

  3. Search for Google Drive folder - with this, Zibot users can search through Google Drive for relevant folders:

    Search for Google Drive folder Zibot configuration

  4. Upload file to Google Drive- allows uploading Ziflow proof files to selected Google Drive folder. Proofs must have the Allow download of the original file setting enabled on the proof level to let Ziflow send asset files to Google Drive.

    Upload file to Google Drive Zibot configuration

And you're done! Ziflow will now send or update data in your designated Google Drive

account.


Google Drive flow examples

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.

Upload assets to the Google Drive folder and populate application fields in Ziflow.

1. Create a new flow and select the needed event trigger. In this case, it will be a New Proof/Version event. This event will trigger once the new proof is created.

Create a new flow with a new proof/version as an event trigger

2. Add the first flow action, which will be the Search Google Drive Folder. I entered a JSON object in the folder name field to collect the name of a proof folder. In my use case, I've got Google Drive folders matching folders in Ziflow.

Search Google Drive Folder action configuration

I have Google Drive folders that correspond to the folders in Ziflow for my particular use case.
(Google Drive)

Google Drive folder name

(Ziflow)

Ziflow folder name

3. The next flow action is the Upload file to Google Drive Zibot. At this Zibot configuration (parent folder ID field), I used the search result from the previous step (Search Google Drive folder). This allows adding proof files dynamically based on search results.

Upload file to Google Drive action configuration

Proofs must have the Allow download of the original file setting enabled on the proof level to let Ziflow send asset files to Google Drive.

4. As the last flow step, please select the Update proof integration property Zibot, which will link the submitted proof with a Google Drive file.

Update proof integration property action configuration

5. To ensure the integration works correctly, you can test it by submitting a new proof in Ziflow. The integration will then check if there is a corresponding folder on the Google Drive side. If a proof folder matches the folder inside Google Drive, the integration will upload a proof file to your cloud storage. Once uploaded, the integration will link the proof with the uploaded file, which can be observed in the proof integrations tab.

Submit a test proof to see if the flow works correctly

Supporting Material:

Did this answer your question?