Integrating Document360 with Google Drive using Zapier

If your team uses Google Drive as a central file repository, keeping it in sync with your Document360 knowledge base manually is time-consuming. By connecting Document360 and Google Drive through Zapier, you can automate file management: whenever an event occurs in Document360 - such as an article being published or updated - Zapier automatically performs an action in Google Drive, such as uploading a file to a designated folder.

When to use this integration

• Your team stores documentation files in Google Drive and wants Document360 article events to automatically create or update corresponding files in Drive without manual exports.
• You want to maintain a Google Drive archive of your published knowledge base articles for backup, sharing, or offline access.
• Writers or stakeholders who don't have Document360 portal access need to receive article content through Google Drive automatically when articles are published.

Before you begin

• You must be logged into your Zapier account.
• You must have a Google account with access to the Google Drive folder you want to write files into.
• You must have your Document360 API token ready. To generate one, navigate to Connections > Extensions , locate the Zapier tile, and click Connect to copy the token.

How to set up the Zap

Step 1 — Create a new Zap

1. Log in to your Zapier account.
2. From the left navigation menu, click Create then select Zaps.
3. A new Zap is created with a Trigger and Action flow.

Step 2 — Connect Document360 as the trigger

1. In the Trigger field, choose Document360.
2. On the Setup panel, select the desired event in the Event field.
3. Click the Account field — a Sign-in panel appears.
4. Enter your sign-in credentials and click Allow.

To generate the API token from Document360:

5. Navigate to Connections > Extensions in the left navigation bar of the Knowledge base portal.
6. On the Zapier extension tile, click Connect.

7. Click the Copy icon to copy the token.

8. Head back to the Zapier panel and paste the API token into the field.
9. Click Yes, Continue to Document360.

10. You can find the connected Document360 project on the Connect Document360 account page. To use a different account later, click Change.
11. Click Continue.

Step 3 — Connect Google Drive as the action

1. In the Action field, choose Google Drive.
2. On the Setup panel, select the desired action from the available options in the Event field.
3. Click the Account field — a Sign-in panel appears.
4. Enter your Google account credentials and click Allow.
5. Click Continue.

6. In the Configure panel, update the following fields:

7. Click Continue.

Step 4 — Test and publish the Zap

1. In the Test section, click Test step.

2. If successful, you will get the message Test item sent! Check your Google Drive account to view it.
3. Click Publish. A Zap published popup confirms the Zap is on.

4. Click Manage your Zap to go to the Zap overview page.

Zap overview

Once active, you can view and manage the Zap from the Zapier dashboard. The overview page shows the trigger, action, and run history for the Zap.

How to delete a Zap

1. Navigate to the Zapier dashboard. A list of all existing Zaps is displayed on the overview page.
2. Click the arrow (>) icon to the right of the Zap you want to remove and click Turn off and delete Zap. The Zap is permanently deleted.

Best practices

• Choose a dedicated folder in Google Drive for files created by this Zap, separate from files your team manages manually. Mixing automated and manual files in the same folder makes it hard to track what came from where.
• Use a consistent file naming convention in the File Name field — for example, including the article title and date — so files in Drive are easy to identify and search without opening them.
• Set Convert to Document to True if you want to be able to edit the content in Google Drive after it arrives. Set it to False if you only need a read-only archive copy.