Integrating Typeform with Document360 using Zapier

Typeform is a platform for creating interactive forms, surveys, and quizzes in a conversational format. When customers or prospects submit questions and feedback through your Typeform forms, that information often contains valuable content that belongs in your knowledge base. By connecting Typeform and Document360 through Zapier, you can automate this: whenever a new Typeform entry is submitted, Zapier creates a corresponding article in Document360 automatically, turning form responses 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 — rather than internal task assignments — drive new article creation in Document360.

Before you begin

• You must be logged into your Zapier 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 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 Typeform as the trigger

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

3. Click the Account field — a Sign-in panel appears.
4. Enter your Typeform sign-in credentials.
5. Select the checkbox and click Let me in. 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 required fields from Typeform 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 the article located in the category you 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.

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 Publish to False so Typeform-triggered articles land in Document360 as drafts. Form responses are raw input — they almost always need editing, formatting, and review before they're ready to publish as knowledge base articles.
• Map a specific Typeform question field to the article title rather than using a generic placeholder. A question like "What were you trying to do?" makes a better article title seed than a submission ID or timestamp.
• Use a dedicated Typeform form for this Zap rather than connecting a general survey. A form specifically designed to collect questions or feedback for documentation gives you cleaner, more actionable data to work with in Document360.