Pipedream Typeform steps in n8n

Typeform is a classic Pipedream starting point: a form submission arrives and goes to a sheet, a CRM or an email. n8n's answer is the Typeform Trigger, and this is one of the few app triggers our converter maps on its own.

The n8n side

Typeform Trigger (n8n-nodes-base.typeformTrigger): webhook-based, one form per trigger, one event (a form response). Options:

• Simplify Answers: converts answers to question title: answer pairs.
• Only Answers: drops metadata such as hidden fields and timestamps.

n8n has no Typeform action node. Calls to the Typeform API (forms, responses) go through HTTP Request with the Typeform credential.

What maps where

Pipedream (app typeform)	In n8n	Status
New Submission (source)	Typeform Trigger, form ID taken from the source	automatic, connect credential
List Responses, Lookup Responses	HTTP Request → GET /forms/{id}/responses	manual
Get a Form, List Forms	HTTP Request → GET /forms/{id}, GET /forms	manual
Create a Form, Duplicate a Form, Update Form Title, Delete Form	HTTP Request → forms endpoints	manual

Steps after the trigger depend on their own apps: Google Sheets, Slack, Airtable and others may convert automatically, other apps arrive as placeholders with props.

Typeform credentials in n8n

• API token: a personal access token from Typeform account settings with Forms: Read and Webhooks: Read, Write.
• OAuth2: default scopes forms:read, webhooks:read, webhooks:write; removing one can break the trigger.

The converter's report lists the Typeform credential (token type) because the trigger expects it by default.

Typical migration: form to Google Sheets and Slack

Pipedream: Typeform New Submission → Google Sheets Add Single Row → Slack Send Message to Channel. n8n after conversion: Typeform Trigger (form ID filled) → Google Sheets append (converted) → Slack message (converted). Connect the three credentials, then submit the form once. If the column mapping used Pipedream's answer paths, compare them with the n8n payload: with Simplify Answers on, answers are keyed by question title.

Typeform migration pitfalls

• Webhook replaced. On activation n8n registers its own webhook on the form. Typeform supports several webhooks per form, but disable the Pipedream workflow to avoid double processing.
• Renamed questions. With Simplify Answers on, renaming a question changes the key and breaks the mapping. For stable mappings turn it off and use field refs.
• Rate limit. Typeform's Create and Responses APIs allow 2 requests per second per account; webhooks are not limited. Backfilling old responses via HTTP Request needs a Wait node.
• Hidden fields arrive only with Only Answers off.
• File upload answers are links that need the Typeform token to download; fetch them with HTTP Request and the same credential if the next step needs the file.
• Test vs production URL. While you test in the editor, n8n registers the test webhook; activate the workflow so Typeform points at the production URL.

How to move your Typeform workflows

1. Export from Pipedream.
2. Upload on /convert; the free report shows the Typeform Trigger as converted and lists the remaining steps.
3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: Jotform, Google Sheets, HubSpot.