Resources · n8n integration

Typeform n8n integrationAutomate Typeform with n8n.

Every Typeform reply can start a workflow on its own. The Typeform n8n integration rests on a single node, the Typeform Trigger, which starts a workflow the moment somebody submits a form. Three settings shape what the next step receives, and 2 credential types get you connected.

Try the Typeform integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Typeform n8n integration actually do?

The Typeform n8n integration runs one way, and that is the first thing to know. n8n ships a single Typeform node, the Typeform Trigger, and it starts a workflow on a Typeform form submission before handing the answers to the next step. There is no Typeform action node in the catalog, so a workflow reacts to your forms, it never edits them.

The rest is plumbing: 2 ways to authenticate, 3 settings on the trigger, and whatever you decide to build after it.

Start with the classic case, a contact form on a landing page. Someone fills it in, the trigger fires, and the workflow writes a row in Google Sheets before posting the answers in the right Slack channel. Sales reads the lead while the visitor is still on the site, and nobody exports a CSV on Monday morning.

Second scenario, product feedback that sorts itself. Each survey answer lands in n8n, an OpenAI step groups it by theme and tone, and the result becomes a page in Notion. Switch on Simplify Answers before you build that one. The payload then arrives as question and answer pairs, which is much easier to hand to a model than a raw submission object.

Third scenario, event signups that confirm themselves. The trigger catches the registration, the workflow counts the remaining seats, sends the confirmation, and files the attendee. Only Answers keeps this one short: the node returns what people typed and drops the other data attached to the submission.

Now the part the node does not cover. It cannot create a form, read the answers collected last month, or reword a question. Anything in that register goes through the HTTP Request node, which calls Typeform's API directly with the same personal Access Token, plus the scopes that particular call needs. More work than a dropdown, and the only route available for this tool.

One last limit worth planning for: Form Name or ID holds a single form, so watching 4 forms means 4 triggers, in one workflow or several. The webhook, the URL n8n registers with Typeform so each submission is pushed to it, needs its own permissions. Strip Webhooks: Read or Write from the credential and the documentation warns the trigger can stop working. If the platform choice itself is still open, the n8n review digs into that question.

Connect

How do you connect Typeform to n8n?

  1. 01

    Generate a personal access token

    Log into Typeform, select your profile avatar in the upper right, then Account, Your settings, Personal Tokens. Select Generate a new token and give it a Name such as n8n integration. For Scopes, select Custom scopes, then tick Forms: Read and Webhooks: Read and Write. Copy the token into the n8n credential, the connection you save once in the Credentials menu and reuse in every workflow.

  2. 02

    Or register a developer app for OAuth2

    OAuth2 uses an app instead. In the upper left, open the dropdown for your organization, select Developer apps, then Register a new app. Fill in an App Name, put your n8n base URL in App website, and paste the OAuth Redirect URL from n8n into Redirect URI(s). Copy the Client Secret and Client ID into n8n.

  3. 03

    Add the trigger and point it at a form

    Search Typeform in the nodes panel. The Typeform Trigger is the only node that comes up, since the tool has no action node. Select your credential, open Form Name or ID and choose the form from the list. An expression works too, a short piece of code that n8n evaluates at run time, if you would rather set the identifier yourself than pick it from the list. Activate the workflow once the mapping looks right.

Triggers

What the Typeform Trigger listens to

Typeform Trigger is the node that starts a workflow each time Typeform receives a new submission. Pick the form, activate the workflow: n8n registers the webhook on your Typeform account.

What you see in n8n

Configuration notes

01Typeform TriggerOne node, one job. The Typeform Trigger starts the workflow on a Typeform form submission, and hands the answers to the next node. Nothing else in n8n speaks Typeform natively, which makes this node the entry point of any Typeform automation.

One node, one job. The Typeform Trigger starts the workflow on a Typeform form submission, and hands the answers to the next node. Nothing else in n8n speaks Typeform natively, which makes this node the entry point of any Typeform automation.

Key parameters

  • Form Name or ID: required, and the only setting that decides what the node watches. Choose the form from the list, or specify an ID with an expression, which is handy when the same workflow is deployed on several accounts.
Use cases
a lead form that feeds the CRM. A satisfaction survey works the same way, except the interesting part sits right after the trigger: a low score pings the account owner, a good one is simply filed.
When to use it
whenever the form is the starting point of the process. If the workflow should instead run at a fixed hour, a Schedule node plus an API call is the right shape, not this trigger.
02Simplify Answers and Only AnswersTwo optional toggles decide what the next node actually receives. Left alone, the trigger hands over the submission as it arrives. Switched on, they reshape the payload before the rest of the workflow ever sees it, which saves a mapping step later.

Two optional toggles decide what the next node actually receives. Left alone, the trigger hands over the submission as it arrives. Switched on, they reshape the payload before the rest of the workflow ever sees it, which saves a mapping step later.

Key parameters

  • Simplify Answers: converts the answers into key and value pairs, the field title on one side and the answer on the other, so the data reads like your form instead of like an API response.
  • Only Answers: returns the answers of the form and none of the other data that travels with a submission. Useful when the workflow only cares about what people typed.
Use cases
filling a spreadsheet column by column, handing clean text to a model, dropping answers into an email template.
When to use it
both on for short forms that feed a single tool. Leave Only Answers off when a later step needs the rest of the submission data.
Need help

Need help automating Typeform with n8n?

A person reads every message.

FAQ

Frequently asked questions

01Is the Typeform n8n integration free?
Yes. The Typeform Trigger is built into n8n, on n8n Cloud and on a self-hosted instance alike, and no license is charged for the node itself on top of your n8n plan. On the Typeform side, you need an account able to generate a personal access token, or an organization where you can register a developer app for OAuth2. Both are set up from Typeform's own admin panel. Which Typeform plan a given form needs is a Typeform question, and their pricing page answers it.
02What credentials or permissions does the Typeform Trigger need?
Two methods work, and they lead to the same result. The API token route uses a personal Access Token generated under Account, Your settings, Personal Tokens, with Scopes set to Custom scopes and these boxes ticked: Forms: Read, plus Webhooks: Read and Write. The OAuth2 route uses a Client ID and a Client Secret from an app registered under Developer apps, and it requests forms:read, webhooks:read and webhooks:write by default. Take the token for a quick setup on a single account, take OAuth2 when a long-lived secret sitting in a credential bothers you. Either way, keep the webhook scopes: the documentation warns that removing a default scope can stop the trigger working.
03What are the limits of the Typeform integration in n8n?
It listens, it does not write. n8n provides a Typeform Trigger and no Typeform action node, so a workflow cannot create a form, edit a question, or pull the responses collected last quarter through a ready-made node. All of that goes through the HTTP Request node against Typeform's API, using the same personal Access Token with the scopes each call requires. Second limit: Form Name or ID takes one value, so several forms mean several triggers. Third: the node reacts to new submissions, not to the answers collected before the workflow was activated, so plan a one-off import if you need the history.
04Does the Typeform Trigger react in real time?
Yes, or close enough. The node works through a webhook, meaning Typeform calls an n8n URL as soon as somebody submits the form, rather than n8n asking Typeform every few minutes whether anything changed, a pattern known as polling. That is precisely why the credential asks for Webhooks: Read and Write. Without permission to manage webhooks on the account, there is nothing for Typeform to call. One practical consequence: n8n registers that URL with Typeform when you activate the workflow, so submissions only reach n8n while the workflow is active.
05n8n or Make for Typeform?
It depends on what happens after the submission, because both tools catch it. The deciding factors sit downstream: branching logic, code steps, hosting, and how each platform counts your runs. n8n can run on your own server, which matters when form answers carry personal data you would rather keep in house. Make tends to be quicker to assemble for a linear chain of steps with no code in it. One honest detail on the n8n side: with no Typeform action node available, everything beyond listening goes through HTTP Request, and a team that dislikes raw API calls will feel that gap. The n8n review linked above compares the two in more depth.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations