---
title: "Integrating GitHub with Document360 using Zapier"
slug: "github-document360"
description: "Create articles in your Document360 projects from new GitHub commits automatically."
tags: ["Extensions", "Github", "Premium", "Zapier"]
updated: 2026-07-20T06:31:09Z
published: 2026-07-20T06:31:09Z
canonical: "docs.document360.com/github-document360"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](https://zapier.com/app/dashboard).
- 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.

---

## Set up the Zap

### Step 1 — Create a new Zap

1. Log in to your [Zapier account](https://zapier.com/app/dashboard).
2. From the left navigation menu, click **Create** then select **Zaps**.
3. A new Zap is created with a **Trigger** and **Action** flow.

![Screen recording showing a new Zap being created in the Zapier dashboard with Trigger and Action flow](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/1_ScreenGif-Zapier_Google_Docs.gif)

### 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.

 NOTE

To change the trigger app later, click **Change** in the Trigger field.

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

![Zapier trigger configuration showing GitHub connected with repository selection and trigger test](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/1_ScreenShot-Zapier_Github.png)

### 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:

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

![Document360 extensions page showing the Zapier tile with the Connect option](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/Zapier%20integration.png)

1. Click the **Copy**  icon to copy the token.

![Zapier token details popup in Document360 showing the generated API token and copy option](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/Zapier%20token%20ID.png)

1. Head back to the Zapier panel and paste the API token into the field.
2. Click **Yes, Continue to Document360**.

![Zapier sign-in panel showing the Document360 API token field](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/5_Screenshot_Zapier_API_Token_Pasting%281%29.png)

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

### Step 4 — Map the fields

1. Map the fields from GitHub to Document360:

![Zapier field mapping panel showing GitHub commit fields mapped to Document360 article fields](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/6_Screenvideo-Map_fields_from_GitHub_into_Document360.png)

| Field | Description |
| --- | --- |
| **Title** | By default, **New Commit in GitHub** is selected. Other options are available based on your requirements. |
| **Content** | By default, **Commit Message** is selected. Other options are available based on your requirements. |
| **Version** | Choose the workspace in your Document360 project where the article should be created. |
| **Language** | Choose the language within the selected workspace. |
| **Category** | Select the category where the article will be created. |
| **Publish** | Set to **True** to publish the article immediately. Set to **False** to save it as a draft. |

 NOTE

The **Continue** button is only enabled after all required fields have been mapped.

1. 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.

![Zapier Zap overview page showing the GitHub to Document360 automation with run history](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/2_ScreenShot-GitHub.png)

---

## 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.