Zapier - Setup guide

Zapier is an online automation tool that connects Document360 with hundreds of third-party applications without requiring any code. It works by creating automated workflows called Zaps - each Zap consists of a trigger (an event in one app) and an action (something that happens automatically in another app as a result). Once you connect Document360 to Zapier using an API token, you can build workflows that move data between Document360 and the tools your team already uses, reducing manual work and keeping your knowledge base in sync with the rest of your stack.

When to use the Zapier extension

• You want to automate repetitive documentation tasks — for example, automatically creating a Document360 article draft when a new row is added to a Google Sheet, or when a form is submitted in Typeform.
• Your team uses project management tools like Asana, Trello, or monday.com and you want to trigger knowledge base updates when tasks reach a certain stage.
• You want to connect Document360 to CRM platforms like HubSpot, Zoho CRM, or Pipedrive to keep product documentation aligned with sales and support workflows.
• You need to automate notifications or content updates across tools like Gmail or Mailchimp when articles are published or updated in Document360.

Before you begin

• You must have an active Zapier account. If you don't have one, sign up at zapier.com.
• You must have an account in the third-party application you want to connect with Document360 through Zapier.
• If you are new to Zapier, check out Zapier's getting started guide to learn how to build workflows and automate tasks before setting up your first Zap.

How to generate the API token in Document360

The API token is what Zapier uses to authenticate and connect to your Document360 knowledge base.

1. Navigate to Connections () > Extensions () in the left navigation bar of the Knowledge base portal.
2. Under Team collaboration, on the Zapier extension tile, click Connect.

3. A Zapier details popup appears with a generated token.
4. Click the Copy icon to copy the token.

This API token is used to authenticate Document360 when building Zaps in Zapier. Keep it secure — treat it the same way you would a password.

Zapier use cases for Document360

Once you have the API token, you can build Zaps connecting Document360 to any of the following platforms. Each use case article walks through a specific Zap with step-by-step configuration:

Best practices

• Generate the API token only when you are ready to start building your first Zap — the token is active immediately and grants access to your knowledge base as soon as it is created.
• Store the API token securely. If you suspect it has been compromised, return to Connections > Extensions and generate a new one — the old token will be invalidated.
• Test each Zap thoroughly in Zapier before turning it on. Use Zapier's built-in test step to verify that the trigger and action are working as expected with real data before the workflow runs automatically.
• Start with simple single-step Zaps (one trigger, one action) before building multi-step workflows. This makes it easier to identify which step is failing if something goes wrong.
• Name your Zaps clearly — for example, "Typeform submission → Create Document360 draft" — so your team can understand what each automation does without having to open it.

FAQ