Make - Setup guide

Make (formerly Integromat) is an online automation platform that connects Document360 with various third-party tools and applications. It works by creating automated workflows called Scenarios — each Scenario consists of a trigger (an event in one app) and one or more actions (things that happen automatically in other apps as a result). Once you connect Document360 to Make using an API token, you can build Scenarios 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 Make extension

• You want to automate repetitive documentation tasks — for example, automatically creating a Document360 article when a new task is added in Asana, or when a form is submitted in Typeform.
• Your team uses project management tools like Asana or Monday.com and you want to trigger knowledge base article creation when items are added or updated.
• You want to connect Document360 to tools like Google Docs or Jira to keep your knowledge base aligned with your development and content workflows.
• You need more complex, multi-step automation than a simple trigger-action pair — Make's visual Scenario builder supports branching logic, filters, and multiple connected apps in a single workflow.

Before you begin

• You must have an active Make account. If you don't have one, sign up at make.com.
• You must have an account in the third-party application you want to connect with Document360 through Make.

Generate the API token in Document360

The API token is what Make 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. On the Make extension tile, click Connect.

3. A Make 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 Scenarios in Make. Keep it secure — treat it the same way you would a password.

Make use cases for Document360

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

Best practices

• Start with a simple Scenario before building complex multi-step workflows. Test a single trigger-action pair first to confirm the Document360 connection is working correctly, then add additional modules and logic.
• Use Make's built-in filters to control when a Scenario runs. Rather than triggering on every event in the connected app, add filter conditions so only the right events — for example, tasks that reach a specific status — create or update articles in Document360.
• Keep your API token secure. The Make integration token operates at the project level and gives broad access to your Document360 knowledge base. Do not share it publicly or store it in unsecured locations. Regenerate it from the Extensions page if you suspect it has been compromised.
• Test Scenarios in Make before activating them. Make's scenario editor lets you run a test execution before turning a Scenario on. Use this to verify that data is mapping correctly and articles are being created in the right category and workspace before the Scenario runs automatically.