Document360
CMS & ContentAuthor and organize Document360 knowledge bases programmatically. Agents create, update, and delete articles, route them into the right workspace and category, and reference Drive folders to keep self-service help centers current.
What This Integration Enables
A knowledge base earns its keep only while it is current, and currency is a workflow problem, not a writing problem: the knowledge exists, it just is not in the article yet. Document360's API treats articles, categories, and workspaces as addressable objects, and this connector puts FlowRunner agents to work keeping them true. Agents create articles into the right workspace and category, sync updates from sources of truth, pull current content for review, and retire what no longer belongs. - Publish new articles automatically when product content changes elsewhere - Sync article titles, bodies, and slugs from a source of truth like Notion or Confluence - Resolve workspace and category IDs so content lands in the right place in the hierarchy - Turn recurring support questions into drafted help articles - Retire outdated documentation through reviewed deletion - Reference Drive folders when organizing media tied to documentation The workspace and category structure is what separates this from generic content automation: List Project Versions and List Categories let agents route an article to the exact place in the hierarchy where readers and search will find it, in the right language variant, instead of dumping content at the root and hoping. Every article here is customer-facing the moment it saves, which is why FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) review sits between drafted content and the help center your customers search.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The release-notes-to-docs pipeline
When engineering merges a release, the workflow maps changed features to affected articles. Get Article pulls each live body, the agent drafts updates from the release notes, and the docs owner approves the diffs. Update Article applies them with correct attribution, and internal source pages in [Notion](/integrations/notion) or [Confluence](/integrations/confluence) stay linked as the canonical drafts. The help center stops being the last place to learn what shipped.
Tickets that write their own deflection
A recurring question pattern surfaces in [Zendesk](/integrations/zendesk). The agent drafts a help article from the best agent answers, calls List Categories to find the right section, and Create Article publishes the draft into the workspace with the ticket IDs logged in the body's source note. The support lead reviews before it goes live in the default language. Next quarter, that question routes to a link instead of a queue, and the deflection is measurable because the article body carries the tickets it was built to end.
The stale-content sweep
Quarterly, the agent walks the hierarchy with List Categories and Get Category, flagging articles untouched beyond the freshness window in categories tied to retired features. Each candidate gets pulled with Get Article and bundled into a retirement review: keep, rewrite, or delete. Approved rewrites route through Scenario 1's pipeline; approved deletions run through Delete Article one confirmed ID at a time. List Drive Folders identifies the media folders whose assets the deleted articles referenced, so cleanup extends to orphaned files.
Human-in-Loop Highlight
Delete Article is permanent, and in a knowledge base the blast radius is bigger than the article: every support macro, onboarding email, and community answer that links to it starts serving customers a dead page. So the retirement sweep on this page never deletes on its own schedule. It presents the case: "Article 'Configuring the legacy SFTP export' in Integrations, last updated 19 months ago, feature retired in the March release, 2 inbound links from active support macros. Delete, or redirect the macros first?" The docs owner sequences the work, the macros get repointed, and only then does the deletion run against the confirmed ID. Update Article carries a quieter version of the same weight, since an unreviewed sync can overwrite a carefully worded warning with generated text, which is why drafted changes ship as diffs for approval, not silent saves.
Agent Capabilities
8 actionsArticles
4- Get Article Retrieves an article by ID with title, content, HTML, category, workspace, status, and metadata, optionally in a specific language translation. The read that grounds every edit.
- Create Article Creates an article in a workspace, optionally inside a category, with title, author attribution, body content, content type (Markdown, WYSIWYG, or Block), order position, and custom slug.
- Update Article Updates an article's title, body, or slug, changing only the fields provided, with author attribution and optional language targeting. The sync step behind source-of-truth workflows.
- Delete Article Permanently deletes an article. Cannot be undone, which is why it sits behind this page's retirement gate.
Categories
2- List Categories Lists a workspace's categories with IDs, names, slugs, hierarchy, and article counts. The routing map for new content.
- Get Category Retrieves a category with its description, parent, order, and contained articles. The unit of audit in freshness sweeps.
Workspaces
1- List Project Versions Lists the project's workspaces with IDs, names, version numbers, and language settings. The first resolution step in any authoring workflow.
Drive
1- List Drive Folders Lists Document360 Drive folders with IDs, names, and hierarchy. Used to organize and reference the media assets documentation depends on.
Frequently Asked Questions
What can FlowRunner do with Document360?
FlowRunner agents can run Get Article, Create Article, and Update Article in Document360, plus 5 more actions.
Does connecting Document360 to FlowRunner require OAuth?
No. Document360 connects to FlowRunner with an API key, no OAuth flow required.
Can Document360 trigger a FlowRunner workflow automatically?
Document360 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Document360
$100 in credits. No card required. Connect in minutes.