---
title: "Integrating Typeform with Document360 using Make"
slug: "typeform-and-document360-integration"
description: "Integrate Typeform with your knowledge base to track the responses. With Make, you can facilitate the content flow between these platforms easily."
tags: ["Extensions", "Make extension", "Typeform"]
updated: 2026-06-26T12:13:50Z
published: 2026-06-26T12:13:50Z
canonical: "docs.document360.com/typeform-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 Typeform with Document360 using Make
Typeform is a platform for creating interactive forms, surveys, and quizzes in a conversational format. When customers or prospects submit responses through your Typeform forms, that information often contains valuable content — questions, feedback, or data — that belongs in your knowledge base. By connecting Typeform and Document360 through Make, you can automate this: whenever a new response is submitted to a Typeform form, Make automatically creates a corresponding article in Document360, turning form submissions into documentation without manual effort.
---
## When to use this integration
- You use Typeform to collect frequently asked questions from customers or prospects and want each submission to automatically generate a draft article in Document360 so your team can turn answers into published documentation.
- You run feedback surveys through Typeform and want responses that reveal knowledge gaps to flow directly into your knowledge base workflow for follow-up.
- You want to build a documentation pipeline where form submissions — filtered by specific fields or completion status — drive new article creation in Document360 on a regular schedule.
---
## Before you begin
- You must have an active Make account.
- You must have a Typeform account with the form you want to use as a trigger.
- 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. The Make dashboard appears.
2. Click **Create a new scenario** at the top right.
3. Click the add (**+**) icon — a list of available applications appears.
4. In the Search field, type **Typeform**.
5. Select **Typeform** and choose the trigger you want to use. For example, select **Watch Responses** to trigger the Scenario when a new response is submitted.
### Step 2 — Configure the Typeform module
Connect your Typeform account and configure the trigger settings.
1. Click **Create a connection** and enter a **Connection name**.
2. Click **Save**.
3. Click **Accept** to allow Typeform to access your Make account. Your Typeform account is now connected to Make.
4. In the **Limit** field, enter the maximum number of responses Make will return per execution cycle.
5. Click the **Form ID** dropdown and select the form you want to watch.
6. If you want the Scenario to trigger only when specific fields are filled, add the desired fields using **Add item** in the **Fields** section.
7. In the **Completed** section, select the appropriate option:
- **Yes** — watch only forms that have been fully submitted.
- **No** — watch only forms that have not been submitted.
- **Empty** — watch only forms with empty responses.
8. In the **Query** field, enter a text string to watch only responses that contain that text.
9. Click **OK**.
10. In the **Choose where to start** popup, select the date and time from which you want to start watching for new responses.
11. Click **OK**.
### Step 3 — Connect Document360 as the action
Once Typeform is connected, add Document360 as the next module in the Scenario.
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**.
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 **Make** extension tile, click **Connect**.
7. Click the **Copy** icon to copy the token.
8. Head back to the Make panel and paste the API token into the field.
9. In the **Article Title** field, select the Typeform parameters you want to use as the article title. For example, select the **Task name** parameter.
10. In the **Article Content** field, select the parameters you want as the article content. For example, select **Assignee Name**, **Resource Type**, and **Due On**.
11. From the **Project Category ID** dropdown, select the category where the new article should be created.
12. Click **OK**.
### 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, submit a new response to the associated Typeform form.
3. Once the response is submitted, 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.
### 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.
Once activated, the Scenario runs automatically every 15 minutes and creates articles from new Typeform responses.
---
## Best practices
- **Use the Completed filter** to ensure the Scenario only triggers on fully submitted responses. Setting this to **Yes** prevents partial or abandoned form entries from generating incomplete articles in Document360.
- **Use the Query field** to narrow down which responses trigger the Scenario — for example, only responses that mention a specific product or topic. This keeps your Document360 content focused and avoids creating articles from irrelevant submissions.
- **Map a specific Typeform question field to the Article Title** rather than relying on a generic parameter. A question like "What is your main question?" produces a more useful article title seed than a response ID or submission timestamp.