Resources · Make integration

Document360 Make integrationAutomate Document360 with Make.

Can your knowledge base update itself when something changes elsewhere? The Document360 Make integration gives you 5 modules: 1 instant trigger, 3 actions and 1 search. This guide is for support and documentation teams, and it walks you from the API token to a working scenario.

Try the Document360 integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Document360 Make integration do?

The Document360 Make integration links your knowledge base to Make, a visual tool where you build a scenario: the automation itself, made of modules, each one a single brick such as a trigger, an action or a search. Once your account is connected, Make can react to new articles, create articles, find a document and add text to one, without any code.

Alert the team about every new article. Watch New Articles is an instant trigger: Document360 calls Make through a webhook when someone creates an article, so the scenario can pass the news to the chat or task tool your team already uses.

Turn content written elsewhere into articles. When a draft is approved in another tool, Create an Article drops it into the knowledge base. Put Find a Document in front of it if you want to check first that the topic is not already covered.

Keep a living changelog. Find a Document locates the page, then Append Text to Document adds the new entry at the end, so product updates pile up in one place instead of scattering across new pages.

The listed modules stop there: for anything else, Make an API Call reaches the rest of the Document360 API with the same connection. Be aware that the official Make documentation for this app says it was generated by AI and may contain mistakes, so check the details that matter with Document360. The same app can also exist on n8n; the n8n vs Make comparison sets out the criteria. To learn the editor properly, see the Make training, and Make pricing explains how plans count usage.

Connect

How do you connect Document360 to Make?

  1. 01

    Create an API token in Document360

    In Document360, open Settings then Knowledge base portal then API tokens and click Create API token. Give it a name, pick the allowed methods, click Create and copy the token shown in the list.

  2. 02

    Add a Document360 module in Make

    In your scenario, add any Document360 module and click Create a connection. A connection is your Document360 account linked to Make once, then reused by every Document360 module. The Connection name field is optional but helps later.

  3. 03

    Paste the token and save

    Paste the API token you copied, or follow the instructions Make shows on screen, and confirm. Make can now read and write in your knowledge base with the rights that token carries.

First scenario

Your first scenario with Document360

GoalWhen a release note arrives from another app, Make finds the changelog in Document360 and adds the note to the end of it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your release notes start, such as a form or a spreadsheet, and set its module.

  2. 02

    Add Find a Document

    Click the + on the right, search Document360 and choose Find a Document. Create the connection with your API token, then describe the changelog page you want Make to locate.

  3. 03

    Append the release note

    Add Append Text to Document, point it at the document found in the previous step and map the text of the release note from the first module into the text to add.

  4. 04

    Test with Run once

    Click Run once and open each module to read its bundles, the items passed from one module to the next. Check in Document360 that the note landed at the end of the right page.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default, and switch the scenario on. Each module run on a bundle is one operation, the unit Make counts on your plan.

Triggers

What starts a Document360 scenario

1 module starts a scenario when something happens in Document360. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Document360 as soon as it happens.

Document3601Watch New Articles

Watch New Articles

Instant trigger

In Make“Triggers when a new article is created.”

Watch New Articles starts your scenario as soon as someone creates an article in Document360, and hands Make that article as a bundle to pass along to the next modules. Nobody has to remember to tell the rest of the company that the knowledge base grew.

How it fires
it is an instant trigger, so Document360 calls Make through a webhook as soon as the article is created, with no waiting for a schedule.
When to use it
to announce new help content to support agents or to log each new article in a tracking sheet.
Watch out
while setting it up, click Create a webhook before Create a connection, otherwise Document360 has nowhere to send the news.
Modules

What Make can do in Document360

Document360 gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Document3601

Append Text to Document

Action

In Make“Appends text to an existing document.”

This module adds new text to the end of a document that already exists, so one page grows over time while its link stays the same for your readers.

When to use it
for a changelog, a known issues page or a running FAQ that receives new entries from another tool.
Watch out
it needs an existing document, so place Find a Document before it when you do not know which one to target.
Document3602

Create an Article

Action

In Make“Creates a document from the text in Document360.”

Here you get a brand new article in your knowledge base, written from text that comes from an earlier module, such as an approved draft or a form answer.

When to use it
when the content deserves its own page rather than a line added to an existing one.
Watch out
every run creates another article, so a scenario that runs twice on the same data leaves you with a duplicate.
Document3603

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call sends your own request to any part of the Document360 API from your scenario, reusing the connection you already created, so you are not stuck when no ready module fits.

When to use it
when the four other modules do not cover what you need to do in your knowledge base.
Watch out
you write the request yourself, so keep it for real gaps and prefer the ready modules when they do the job.
Document3604

Find a Document

Search

In Make“Finds the document from the knowledge base.”

Find a Document searches your knowledge base and returns what matches, so the next modules know exactly which page to work on instead of guessing.

When to use it
before Append Text to Document, or before Create an Article to check that the topic is not already covered.
Watch out
a search can return zero, one or several bundles, and each bundle runs the rest of the scenario once.
Need help

Need help automating Document360 with Make?

A person reads every message.

FAQ

Frequent questions about Document360 and Make

01Is the Document360 Make integration free?
Yes, on the Make side. Document360 is a standard app, available from the Free plan. That plan lets you run 2 active scenarios, with at least 15 minutes between two scheduled runs, up to 5 minutes of execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the limit on active scenarios, and usage is counted in operations each month. You still need an active Document360 account with API access, which Document360 bills on its own terms.
02What do you need to connect Document360 to Make?
An active Document360 account and a valid API token. You create the token in Document360 under Settings, Knowledge base portal, API tokens, by clicking Create API token, naming it, selecting the allowed methods and copying the result. In Make, add a Document360 module, click Create a connection, optionally name it, and paste the token. If the first module is the instant trigger Watch New Articles, click Create a webhook before Create a connection. The same connection then serves every Document360 module in your scenarios.
03Does the Document360 trigger in Make fire in real time?
Yes. Watch New Articles is an instant trigger: Document360 calls Make through a webhook as soon as an article is created, so the scenario starts right away. It is the only trigger of the app. When a scenario starts from another app instead, it follows the schedule set on its first module, every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval; paid plans go down to 1 minute. Remember to click Create a webhook when you add it, before creating the connection.
04What if the Document360 module you need is missing in Make?
Use Make an API Call. It sends any request to the Document360 API with the connection you already set up, so actions that have no dedicated module, among the 5 listed, stay within reach. You build the request from the Document360 API documentation. Keep in mind that the Make documentation for this app warns that it was produced by AI and may contain errors, so confirm important details with Document360 before relying on them in a live scenario.
05Should you use Make or n8n for Document360?
It depends on the tool your team already builds with, not on a winner. On Make, Document360 comes with 5 ready modules: an instant trigger for new articles, three actions including Make an API Call, and a search. That covers creating articles, adding text and finding documents without writing requests. Many apps also have an n8n node, so check whether one exists for Document360 and what it offers before switching. Compare both on the same scenario you plan to run, then pick the editor your team finds clearer.
Same platform

Other docs you might need on this stack.

Browse all integrations