Integrating GitHub with Document360 using Zapier

When developers commit new code or updates to a GitHub repository, corresponding changes often need to be reflected in your knowledge base. Manually creating or updating Document360 articles for every commit is time-consuming and error-prone. By connecting GitHub and Document360 through Zapier, you can automate this: whenever a specified event occurs in a GitHub repository, Zapier automatically creates a corresponding article in your Document360 knowledge base.

When to use this integration

• Your engineering team follows a docs-as-code approach and wants each GitHub commit to a specific repository to automatically generate a draft article in Document360 for review.
• You maintain a changelog or release notes knowledge base in Document360 and want new commits or releases in GitHub to trigger article creation automatically.
• Your development workflow includes documentation updates alongside code changes, and you want to ensure knowledge base articles are created in sync without a manual step.

Before you begin

• You must be logged into your Zapier account.
• You must have a GitHub account with access to the repository 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 GitHub as the trigger

1. In the Trigger field, choose GitHub.
2. In the Trigger event field, select the event that should trigger the Zap.

3. Click the Account field — a Sign-in panel appears.
4. Enter your GitHub credentials and click Authorize Zapier.
5. Choose the desired repository and click Continue. Zapier runs a test to confirm the trigger is correctly configured.

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 fields from GitHub to Document360:

2. Click Continue.

Step 5 — Test and publish the Zap

1. In the test section, click Send Test.
2. If successful, you will get the message Test Article sent! Check your Document360 account to view it.
3. In your Document360 portal, you'll find a new article titled "New commit in GitHub" 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

• Set the Publish field to False when mapping fields so that GitHub-triggered articles land in Document360 as drafts. This gives your documentation team a chance to review, format, and enrich the content before it goes live — since raw commit messages are rarely ready to publish as-is.
• Use a dedicated category in Document360 for GitHub-triggered articles, such as a "Changelog" or "Dev updates" category. This keeps automatically generated content separate from hand-crafted articles and makes it easier to review and promote.
• Choose a specific trigger event that matches your workflow — for example, a push to a release branch rather than every commit — to avoid generating articles for every routine code change that doesn't warrant a knowledge base entry.