- Print
- DarkLight
- PDF
Confluence Server + Document360
Many organizations around the world use wiki for storing project-related artifacts. One of those popular wiki platforms is Confluence, which makes it easy for teams to store artifacts securely and collaborate on projects.
Confluence provides team workspaces as it helps team structure, organize, and share work, so every team member has visibility into institutional knowledge and access to the information they need to do their best work. You can create pages or blogs to give your team a place to create, capture, and collaborate on any project or idea.
Use-Case
You have chosen Document360 as your Knowledge base platform. You have chosen Confluence as your team collaboration platform. When a new blog post or page is created in Confluence, you want to create a corresponding knowledge base article in Document360.
Currently, no direct integration option is available between Confluence and Document360 from either of the platforms.
Confluence Cloud + Document360
If you want to connect Confluence Cloud and Document360, use the Zapier workaround.
Keep your team updated with the latest content by seamlessly connecting Confluence Cloud and Document360. Automate the process of updating Document360 documents every time a new page or blog post is created in Confluence Cloud.
Workaround
As a workaround, you can use Zapier integration to bridge this gap. Connecting Confluence Server and Document360 on Zapier allows you to facilitate the content flow between these platforms easily.
Ensure that you have logged into your Zapier account.
Click the Try this template button. In the following window, click the Get started button.
Connecting Confluence Server and Document360 in Zapier
Step 1 - Connect Confluence Server
- Click on the Connect button and key in your credentials on the new access window. The credentials you need are your confluence site's base URL, your account's email, and an API token. Click on the Yes, Continue button
- Click on the Next button
- In the Which space do you want to use?
Choose a space you wish to use. If it is a newly created space, you can use the Refresh list button to refresh the list. - After selecting a space, click next
- In the Which type do you want to use?
Choose either a blog post or page depending upon your business requirement. Click on Next
Step 2 – Connect Document360
- Click on the Connect button, and a new pop-up window opens with an API token field to connect with the knowledge base project
- You can obtain the API token from the Document360 portal
API token generation
Obtain the Zapier token (API key) generated from the Document360 portal (Settings → Knowledge base portal → Extensions → Team collaboration), click on the generate icon, and copy the token by clicking on the copy button
- Head back to the pop-up window, paste the API token in the field, and click on Yes, continue
- You can find the connected Document360 project on the Connect your Document360 account page. Click on Next
If you wish to configure a different account later, you can do that by clicking on Reconnect or Connect a new account
Step 3 - Customize Zap
- Map the required fields from the Confluence Server into Document360
- By default, the Zap template would be
- Title in Confluence Server Page / Blog post → Title in Document360
- Body in Confluence Server Page/Blog post → Content in Document360
- However, you have a plethora of other options to choose from (depending on your business requirements)
- Click on the Next button
- In the How do you want Zapier to handle these changes in Document360?, you can choose the article location and publish option.
- Version - Choose the desired version in the knowledge base project you want the article to be created in
- Language - Choose the desired language in the selected version you want the article to be created in
- Category - Choose the desired category in the selected language you want the article to be created in
- Publish - Choose True for the article to be published. Choose False for the article to be in draft state.
- Click on the Next button
Step 4 – Test Zap
- Once you have configured the actions in Document360, the Zap needs to be tested to make sure it’s configured correctly
(Zapier would create an article on Document360 to make sure everything works.) - Click on the Send test button
- If successful, you get the message “Test Article sent! Check your Document360 account to view it.’’
- Visit your Document360 knowledge base portal, and you can find the article named “Title of your Page / Blog post” under the category you have previously selected
- Head back to the Zapier setup window and click on Next
Step 5 – Turn on Zap
Now that the Zap is tested and it works fine, review/edit the settings before turning on the Zap.
You can edit the settings configured on the trigger New Pages from Confluence Server new commit and the corresponding action of the new article in Document360
Finally, click on the Turn on Zap button.
You would get a success message window stating Your Zap is on. Click the Manage your Zap button to access your ConfluenceServer+Document360 Zap overview page.
Created Zap overview
Create articles in Document360 from new Confluence Server Page creation
You can view and edit the information about your created Zap on the Zap overview page
Zap runs
Whenever a new page/blog post is created in the Confluence Server, zap runs automatically to create a new article in Document360.