Integrating Confluence Server with Document360 using Zapier

If your team uses Confluence Server as a central wiki for project documentation and also maintains a customer-facing or internal knowledge base in Document360, keeping both platforms in sync manually is repetitive work. By connecting Confluence Server and Document360 through Zapier, you can automate this: whenever a new page or blog post is created in a Confluence space, Zapier automatically creates a corresponding article in Document360.

When to use this integration

• Your team creates project pages or blog posts in Confluence Server and wants those entries to automatically appear as articles in Document360 without manual copying.
• You maintain parallel documentation in both Confluence (for internal team use) and Document360 (for a wider audience) and want new Confluence content to trigger article creation in Document360 automatically.
• You're migrating content from Confluence Server to Document360 gradually and want new content created during the transition to land in both platforms simultaneously.

Before you begin

• You must be logged into your Zapier account.
• You must have a Confluence Server account with access to the space you want to monitor.
• You must have your Document360 API token ready. To generate one, navigate to Connections > Extensions , locate the Zapier tile, and click Connect to copy the token.

How to set up the Zap

Step 1 — Create a new Zap

1. Log in to your Zapier account.
2. From the left navigation menu, click Create then select Zaps.
3. A new Zap is created with a Trigger and Action flow.

Step 2 — Connect Confluence Server as the trigger

1. In the Trigger field, choose Confluence Server.
2. In the Trigger event field, select New Page or Blog Post.

3. Click the Account field — a Sign-in panel appears.
4. Enter your Confluence site's base URL, account email, and API token, then click Yes, Continue to Confluence Server.
5. Click Continue. Zapier runs a test to confirm the trigger is correctly configured.

6. In the Trigger configuration panel, select the space you want to monitor.
7. Choose the content type — either Blog post or Page — depending on what should trigger the Zap.
8. If you have a newly created space that doesn't appear in the list, click Refresh list to update it.
9. Click Test trigger, then click Continue.

Step 3 — Connect Document360 as the action

1. In the Action field, choose Document360.
2. On the Setup panel, select the desired event in the Event field.
3. Click the Account field — a Sign-in panel appears.
4. Enter your sign-in credentials and click Allow.

To generate the API token from Document360:

5. Navigate to Connections > Extensions in the left navigation bar of the Knowledge base portal.
6. On the Zapier extension tile, click Connect.

7. Click the Copy icon to copy the token.

8. Head back to the Zapier panel and paste the API token into the field.
9. Click Yes, Continue to Document360.

10. You can find the connected Document360 project on the Connect Document360 account page. To use a different account later, click Change.
11. Click Continue.

Step 4 — Map the fields

1. Map the required fields for the Document360 article:

2. Click Continue.

Step 5 — Test and publish the Zap

1. In the test section, click Test step.
2. If successful, you will get the message A Document was sent to Document360.
3. In your Document360 portal, you'll find a new article titled after the Confluence page or blog post, located in the category you selected.
4. Head back to the Zapier setup panel and click Next, then click Publish.
5. You will see a success message: Your Zap is on. Click Manage your Zap to go to the Zap overview page.

Zap overview

Once active, you can view and manage the Zap from the Zapier dashboard. The overview page shows the trigger, action, and run history for the Zap.

How to delete a Zap

1. Navigate to the Zapier dashboard. A list of all existing Zaps is displayed on the overview page.
2. Click the Zap actions () icon to the right of the Zap you want to remove and click Delete. The Zap is permanently deleted.

Best practices

• Monitor a specific Confluence space rather than your entire Confluence instance. Pointing the Zap at a single space makes it easier to control which content flows into Document360 and avoids pulling in unrelated team pages.
• Set Publish to False when mapping fields so that Confluence-sourced content lands in Document360 as a draft. Confluence pages often contain formatting or internal references that need cleanup before they're ready for a public knowledge base.
• Map the Confluence page title to the Document360 article title field so the article name in Document360 matches the source. This makes it easier to trace articles back to their Confluence origin and keep both platforms aligned.