---
title: "Integrating Asana with Document360 using Zapier"
slug: "asana-document360"
description: "You have chosen Document360 as your Knowledge base platform. Your company works with multiple external vendors for content contribution. Asana makes for a good collaboration platform, but you have the task of adding the articles created on Asana onto the Document360 knowledge base. Yes, it can be done manually, but it takes more effort, is time-consuming, and the probability of the mishap is high."
tags: ["Asana", "Integrations", "Zapier"]
updated: 2026-07-20T06:25:31Z
published: 2026-07-20T06:25:31Z
canonical: "docs.document360.com/asana-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 Asana with Document360 using Zapier

Many organizations use Asana to organize, track, and manage work across teams. When your team uses Asana to manage documentation tasks — for example, coordinating content creation with external vendors or tracking writing assignments across projects — there's often a manual step of transferring completed content into Document360. By connecting Asana and Document360 through Zapier, you can automate this: whenever a specified event occurs in an Asana project, Zapier creates a corresponding article in your knowledge base automatically.

---

## When to use this integration

- Your documentation team uses Asana to assign and track writing tasks with external contributors, and you want completed task content to flow into Document360 without a manual copy-paste step.
- You manage a content pipeline in Asana where tasks represent articles in progress, and you want new tasks to automatically generate draft articles in Document360 so writers have a place to work from the start.
- You want to keep your Asana project activity and Document360 content creation in sync, reducing the overhead of switching between tools to move content forward.

---

## Before you begin

- You must be logged into your [Zapier account](https://zapier.com/app/dashboard).
- You must have an Asana account with access to the workspace and project 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 Asana as the trigger

![Zapier editor showing Asana as the trigger and Document360 as the action](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/2_Screenshot-connecting_steps_Asana_Document360.png)

1. In the **Trigger** field, choose **Asana**.
2. In the **Trigger event** field, select the required event to trigger in Asana.

 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 Asana credentials and click **Allow**. Zapier runs a test to confirm the trigger is correctly configured.

 NOTE

If your account is already linked to Asana, you can directly select it from the Sign-in panel without entering credentials again.

1. Select your Asana account and click **Next**.
2. Select the desired **Workspace** and click **Next**.
3. Select the desired **Project** and click **Next**.

![Asana sign-in and workspace/project selection steps in Zapier](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/3_Screenshot-Asana_Sign_in_credentials.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%283%29.png)

1. You can find the connected Document360 project on the **Connect Document360 account** page. Click **Continue**.

### Step 4 — Map the fields

1. Map the required fields from Asana to Document360:

| Field | Description |
| --- | --- |
| **Title** | Choose a suitable title from the available Asana task fields. |
| **Content** | Choose suitable content based on your business requirements. |
| **Version** | Select the workspace in your Document360 project where the article should be created. |
| **Language** | Choose the language within the selected workspace. |
| **Article** | Choose the article within the selected category. |

 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 **Test step**.
2. If successful, you will get the message *A Document was sent to Document360*.
3. In your Document360 portal, you'll find the article located in the folder you previously selected.
4. Head back to the Zapier setup panel and click **Next**, then click **Publish**.
5. Review or edit the trigger and action settings as needed. 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 Asana to Document360 automation with run history](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/1_ScreenShot-Asana_extension.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

- **Scope the Zap to a specific Asana project** rather than a broad workspace trigger. Connecting to a focused project — for example, a dedicated documentation or content pipeline project — keeps the Zap from firing on unrelated task activity across your organization.
- **Map the Asana task name to the article title** so each Document360 article created from a task can be traced back to its Asana origin. Clear naming conventions in Asana will produce cleaner article titles in Document360.
- **Use a dedicated Asana project for documentation tasks** if possible. This makes it easier to manage the Zap scope, audit what's been created in Document360, and keep content work separate from other types of Asana tasks.