- Home
- Resources
- Integrations
- Document360
Document360 Zapier integrationAutomate Document360 with Zapier.
The Document360 Zapier integration gives you 1 trigger, 2 actions and 1 search. That is enough to announce every fresh article in a team channel, write documents from other tools, and add text to the pages your team already maintains.
Verified Trustpilot reviews · AI, automation & growth agency
What the Document360 Zapier integration actually does
It links your Document360 knowledge base to the other apps you use, without code. A Zap (the automation you build on Zapier: one trigger, then one or more actions) watches for a new article, or writes into your docs when something happens elsewhere. You set it up once and it runs on its own.
Three results people usually want. First, a heads-up: New Article fires as soon as a writer creates a page, so support or sales hears about it without checking the portal. Second, a document that writes itself: Create a Document turns a form answer, a ticket or a note into a draft in the right category. Third, a living page: Append Text to Document adds a line to an article that already exists, like a changelog that grows with each release.
The search, Find a Document, ties the last two together. It locates the page first, so the append lands in the right place.
What Zapier does not do here matters just as much. There is no trigger for an edited or published article, only for a new one. No action deletes, moves or renames a page. And nothing imports what you wrote before the Zap went live. If one of those gaps blocks you, the Document360 Make integration is worth a look, and the Make vs Zapier comparison is there if you are still choosing a platform.
Zapier vocabulary in one minute
Seven words come back on every Zapier screen. Here they are in plain English.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it to happen.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
- Task
- The unit Zapier bills. One task equals one action that finished successfully; your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the second the event occurs.
- Filter
- A step that lets the Zap continue only when the incoming item matches a condition you chose, and halts it otherwise.
- Search step
- A step that looks up something already stored in an app, so later steps can reuse what it found.
- Connection
- Your Document360 account, linked to Zapier one time, then reused by every step that talks to Document360.
What it really costs
Document360 is not a premium app, so it works on the free plan. The bill depends on actions, never on the trigger.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo
The trigger costs nothing, and neither do the checks Zapier runs. Each action that succeeds counts as one task; one that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a second action or Find a Document and it becomes a multi-step Zap, which needs a paid plan. The interval grid below only matters for polling triggers, and the one Document360 trigger is instant.
Connect Document360 to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. Type Document360 in the dialog and select it. You need a Document360 account first, with access to the project you want the Zap to touch.
- 02
Sign in to Document360
Click Add connection. A new tab asks you to log in to Document360. Use the account that can read and write in the knowledge base, not a reader-only profile, or the actions will have nothing to write into.
- 03
Grant access
Approve the access Zapier asks for. The connection then appears in your list and every Document360 step reuses it, so you never sign in again for each new Zap.
Your first Zap: tell Slack about each new help article
GoalEvery new article in Document360 posts a short note in a Slack channel, but only for the category your support team follows.
- 01
Create the Zap
Start a new Zap and pick Document360 as the app that starts it. Choose New Article as the event, then select the connection you made above.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent articles from your account, so you map fields on a real page instead of a blank sample. Note which value tells the categories apart.
- 03
Add the filter
Click the plus icon, choose Filter, then set the value you spotted, a text rule and the category name. The filter makes this a multi-step Zap, so it needs a paid plan.
- 04
Add the Slack action
Add Slack with Send Channel Message, pick the channel, and drop the article title from the trigger into the message. Test the step and read what Slack received.
- 05
Publish
Click Publish to switch the Zap on. From now on, each new article in that category lands in Slack. Articles written before this moment stay where they are.
Document360 trigger
1 event starts a Zap when something happens in Document360, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Article
Instant triggerIn Zapier“Triggers when a new article is created.”
Starts your Zap the moment someone creates an article in your Document360 knowledge base. The new page, with its title and the details Zapier receives, is ready for the next step to use.
Document360 actions
Document360 gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Append Text to Document
ActionIn Zapier“Appends text to an existing document.”
Adds text to the end of an article that already exists, leaving what is there untouched. You point it at the version, the language and the article, then pass the text to add.
Create a Document
ActionIn Zapier“Create document from text in Document360”
Writes a brand-new page in your knowledge base from text another app sends. You give it a title, the content, and say where it goes: version, language and category.
Document360 search
1 search step looks for data that already exists in Document360, so a later step can use it.
A search step does not change anything. It finds a page so the next step knows where to write. In the editor, it sits at the bottom of the action list, under the SEARCH heading.
Find a Document
SearchFind or createIn Zapier“Find the document from knowledgebase”
Looks through one version and one language of your knowledge base for the page matching your search term, then hands it to the following steps.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap, and the steps after it are skipped. Switch it on and the Zap keeps going with an empty result.
- Create document if it doesn’t exist yet?Tick it and the search turns into find-or-create: when no page matches, it asks for the fields needed to create one instead. The setting above then disappears.
- If multiple search results are found?Several pages match? Three ways out. Keep the first one, which is the default, stop the Zap right there, or pass every match to the steps that follow.
When it breaks
Zapier links no help article to Document360, so the known failure points are the general ones. They are easy to miss when you build your first Zap.
Most problems come from timing or from a Zap feeding itself. Check these four before you go looking for a bug, and keep the Zapier troubleshooting guide handy for the rest.
Old articles never show up
A Zap only reacts to what happens after you publish it. Articles that already existed are not picked up; moving that backlog is a separate job.The Zap keeps firing on its own
Pair New Article with Create a Document in the same project and every page the Zap writes starts it again, burning your task count fast.A bulk import stalls
When a migration suddenly produces a huge batch of articles, Zapier's flood protection can hold the run back instead of firing for each one.The append lands nowhere
Append Text to Document needs an existing article. If Find a Document comes back empty with the default setting, the Zap stops before writing.
Need help automating Document360 with Zapier?
A person reads every message.



