Integrating Google Sheets with Document360 using Zapier

If your team maintains a Google Sheets log of all articles in your Document360 knowledge base — tracking titles, categories, publish dates, or other metadata — updating that sheet manually every time a new article is added is repetitive and easy to forget. By connecting Document360 and Google Sheets through Zapier, you can automate this: whenever a new article event occurs in Document360, Zapier automatically adds a new row to your designated spreadsheet.

When to use this integration

• Your team tracks knowledge base content in a Google Sheet - for example, a content calendar, an article inventory, or a review log - and wants it updated automatically whenever articles are added or changed in Document360.
• You report on knowledge base activity to stakeholders who work in Google Sheets and need an up-to-date record without manual exports.
• You want to create an audit trail of article activity in Document360 that non-portal users can access in a shared spreadsheet.

Before you begin

• You must be logged into your Zapier account.
• You must have a Google account with access to the spreadsheet you want to write rows into.
• Before building the Zap, set up your Google Sheet with column headers that match the Document360 article attributes you plan to map. Zapier reads the headers when configuring the action. Refer to Work with Google Sheets in Zaps for guidance on preparing your sheet.
• 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 Sheets as the action

1. In the Action field, choose Google Sheets.
2. On the Setup panel, select Create Spreadsheet Row 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. As soon as you select the worksheet, the column headings are listed. Map each column heading to the corresponding Document360 article attribute you want to capture.

8. Click Continue, then move to the Test section and click Publish. A Zap published popup confirms the Zap is on.

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

• Set up your spreadsheet column headers before building the Zap. Zapier reads the headers when you select the worksheet in Step 3, so the columns must already exist for mapping to work correctly.
• Keep your column headers descriptive and consistent with how Document360 labels article attributes — for example, "Article Title", "Category", "Published Date" — so the mapping is easy to understand and maintain.
• If you track articles across multiple workspaces, build a separate Zap for each workspace and route the rows to separate worksheets or spreadsheets, so your log stays organized by workspace.

FAQ