---
title: "Integrating Asana with Document360 using Make"
slug: "asana-and-document360-integration"
description: "Integrate your knowledge base with Asana to track your tasks. Asana makes for a good collaboration platform, now you can add your tasks to knowledge base."
tags: ["Extensions", "Make extension"]
updated: 2026-06-26T12:08:00Z
published: 2026-06-26T12:08:00Z
canonical: "docs.document360.com/asana-and-document360-integration"
---

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

Asana is a versatile platform for organizing, tracking, and managing work across teams. Documentation teams that use Asana to coordinate writing tasks with contributors and external agencies can integrate it with Document360 through Make — so that when tasks are created or updated in an Asana project, Make automatically creates a corresponding article in Document360. This removes the manual step of transferring content between platforms and keeps your knowledge base in step with your project activity.

---

## When to use this integration

- Your documentation team tracks writing assignments in Asana and wants new tasks to automatically generate draft articles in Document360, giving writers a pre-created article to work from.
- You collaborate with external contributors through Asana and want completed task content to flow into Document360 without a manual handoff.
- You want a scheduled, recurring automation that checks for new or updated Asana tasks at a set interval and creates articles in Document360 as they appear.

---

## Before you begin

- You must have an active [Make account](https://www.make.com/).
- 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 **Make** tile, and click **Connect** to copy the token.

---

## How to set up the Scenario

### Step 1 — Sign in and create a new Scenario

1. Log in to your [Make account](https://www.make.com/). The Make dashboard appears.

![Make dashboard sign-in page](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/image-1733464343369.png)

1. Click **Create a new scenario** at the top right.
2. Click the add (**+**) icon — a list of available applications appears.
3. In the Search field, type **Asana**.
4. Select **Asana** and choose the task you want to use as the trigger. For example, select **Watch Tasks or subtasks** to get updates on new tasks.
5. Click **Create a connection** and enter a connection name.
6. Click **Save**.
7. Click **Allow** to let Asana access your Make account.
8. Click **OK**.

![Screen recording showing Asana being added as a trigger module in Make with connection and authorization steps](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/1_ScreenGif-Asana_Make.gif)

### Step 2 — Configure the Asana module

Connect your Asana account and configure the trigger settings in the Asana module.

![Asana module configuration panel in Make showing connection, filter, workspace, and project settings](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/image-1733466870362.png)

1. In the **Connection** field, select your Asana connection. If you have already connected Asana with Make, select it from the dropdown.
2. Click the **Filter** dropdown and select **Project**.
3. Click the **Workspace** dropdown and select the desired workspace.
4. Click the **Project ID** dropdown and select the project you want to monitor.
5. In the **Completed Since** field, enter a date in `MM/DD/YYYY HH:MM` format to only return tasks that are incomplete or completed since that time.
6. In the **Modified Since** field, enter a date in `MM/DD/YYYY HH:MM` format to only return tasks modified since that time.
7. In the **Limit** field, enter the maximum number of tasks Make will return per execution cycle.
8. Click **OK**.
9. In the **Choose where to start** popup, select the date and time from which you want to start watching for new tasks.
10. Click **OK**.

Your Asana account is now connected with Make.

### Step 3 — Connect Document360 as the action

Once Asana is connected, add Document360 as the next module in the Scenario.

![Make Scenario editor showing the option to add a new module after the Asana trigger](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/image-1733468868456.png)

1. On the Scenario editor page, click the **Add another module** (**+**) option.
2. In the Search field, enter **Document360**.
3. Select **Document360** and choose the action you want to perform. For example, select **Create an article** to create a draft article.
4. In the Document360 panel, select an existing connection. To create a new connection:
  - Click **Create a connection** and enter a **Connection name**.
  - Enter your Document360 API token and click **Save**.

![Screen recording showing Document360 being added as an action module in Make with API token connection](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/2_ScreenGif-Asana_Make.gif)

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 **Make** extension tile, click **Connect**.

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

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

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

1. Head back to the Make panel and paste the API token into the field.
2. In the **Article Title** field, select the Asana parameters you want to use as the article title. For example, select the **Task name** parameter.
3. In the **Article Content** field, select the parameters you want as the article content. For example, select **Assignee Name**, **Resource Type**, and **Due On**.
4. From the **Project Category ID** dropdown, select the category where the new article should be created.
5. Click **OK**.

![Document360 module configuration panel in Make showing Article Title, Article Content, and Project Category ID fields mapped from Asana](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/image-1733472905161.png)

### Step 4 — Test the Scenario

1. Click the **Run once** button at the bottom left to test the Scenario. Test details appear at the bottom of the page.
2. To trigger the test, create a new task in the associated Asana project.
3. Once the task is created, a new article is created in the associated Document360 category. You can verify this in the test details panel or by navigating directly to your Document360 project.

### Step 5 — Schedule the Scenario

1. Enable the toggle at the bottom left to schedule the Scenario. By default, this runs the Scenario every 15 minutes.
2. Click **OK** to save.

![Make Scenario editor showing the scheduling toggle enabled at the bottom left](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/4_ScreenShot-Asana_Make.png)

### Step 6 — Activate the Scenario

1. Click the **Exit editing** () icon at the top. The integration dashboard appears.
2. Turn on the **ON/OFF** toggle near the **Edit** option to activate the Scenario.

![Make integration dashboard showing the ON/OFF toggle to activate the Asana to Document360 Scenario](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/5_ScreenShot-Asana_Make.png)

Once activated, the Scenario runs automatically according to the schedule you set.

---

## Best practices

- **Use the Filter and Project ID fields** to scope the Scenario to a specific Asana project rather than your entire workspace. This prevents unrelated task activity from generating unwanted articles in Document360.
- **Map meaningful task fields to the Article Title** — the Asana task name is a good default, but consider whether other fields like a custom "Doc title" field better represent what the article should be called.
- **Adjust the execution limit** in the Limit field to match your team's task volume. Setting it too low may cause the Scenario to miss tasks between runs; setting it too high on a busy project may create more articles than expected in a single cycle.
- **Use the Run once button** to verify the Scenario is working correctly before activating it on a schedule. Confirm that the test article appears in the right Document360 category with the right title and content before going live.