Reference · Tools
Typeform Trigger
Starts workflow when a Typeform form is submitted
The Typeform Trigger fires when a respondent submits the form you nominate, passing the response through with signature verification. A typical build is routing each submission into a CRM with the answers already flattened into usable fields.
- Node type
- Webhook trigger
- Parameters
- 3
- Outputs
- Output
- Credentials
- Typeform
Typeform Trigger
Trigger on Typeform form submission
Overview
Triggers a workflow when a respondent submits a Typeform form. Receives the webhook payload from Typeform containing form response data including answers, field definitions, submission metadata, and respondent details. Supports HMAC SHA-256 signature verification. Can simplify nested answer structures into flat key-value pairs and optionally return only answers or the full payload.
Category: Productivity
Tool Name: typeform_trigger
Version: 1
Appearance: Icon: si-typeform | Color: #262627
Node Type
Trigger — webhook (receives incoming HTTP callbacks)
Input / Output
| Direction | Port(s) |
|---|---|
| Input | None (trigger node) |
| Output | Output |
Credentials
This tool requires Typeform credentials. See the Credentials Guide for setup instructions.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Form ID | string | Yes | — | The ID of the Typeform form to watch for submissions. Find this in your Typeform form URL (e.g., https://yourname.typeform.com/to/FORM_ID). |
| Simplify Answers | boolean | No | true | Whether to convert the answers to key:value pairs (FIELD_TITLE: USER_ANSWER) for easy processing. When enabled, nested answer structures are flattened into simple pairs. |
| Only Answers | boolean | No | true | Whether to return only the answers of the form and not any of the other data (event metadata, form definition, etc.). |
Output Data
Each submission produces one output item. Its shape is decided by Simplify Answers and Only Answers:
| Simplify Answers | Only Answers | Item content |
|---|---|---|
true | true | One key per question, using the question title as the key and the answer as the value |
true | false | The full Typeform payload, with form_response.answers replaced by the simplified title/value map |
false | true | The raw answer objects, keyed by Typeform field ID |
false | false | The raw Typeform payload, unchanged |
These fields are always added on top:
_trigger— alwaystypeform_webhook_timestamp— ISO 8601 timestamp of when the submission was received_webhookEvent— the payload’sevent_type, defaulting toform_response_formId— the Typeform form ID the response belongs to_submissionToken— the response token Typeform assigns to the submission_submittedAt— the submission timestamp reported by Typeform
File upload answers are downloaded and attached to the item as binary properties named file_<fieldId>, and the corresponding answer carries a _binaryRef pointing at that property. Files larger than 50 MB, and downloads that fail, are left as URLs in the answer; the reason is recorded per field under _fileNotes.
A submission that arrives without the expected definition and answers data produces a single item carrying _trigger, _timestamp and an _error message instead of response data.
Because question titles become keys, double braces in a title are rewritten to square brackets so they cannot be mistaken for an expression.
Reference the payload downstream by expression, e.g. {{ $json["What is your email?"] }}.
Usage Examples
- Trigger a workflow when someone submits a feedback form
- Capture Typeform survey responses and store in a spreadsheet
- Start a workflow when a new application is submitted via Typeform
- Collect form data from Typeform and send confirmation emails
Example Configuration
Flat answers keyed by question title — the simplest shape to work with:
{
"type": "typeform_trigger",
"parameters": {
"formId": "AbCdEf12",
"simplifyAnswers": true,
"onlyAnswers": true
}
}
Full payload with simplified answers, when you also need the submission metadata:
{
"type": "typeform_trigger",
"parameters": {
"formId": "AbCdEf12",
"simplifyAnswers": true,
"onlyAnswers": false
}
}
Raw Typeform payload, unchanged:
{
"type": "typeform_trigger",
"parameters": {
"formId": "AbCdEf12",
"simplifyAnswers": false,
"onlyAnswers": false
}
}
Trigger Behavior
- Activation: When the workflow is activated, a webhook endpoint is registered with the service.
- Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
- Payload: The incoming webhook payload is parsed and output as workflow items.
- Verification: Supports signature verification where applicable.
Tips
Connects to Typeform via webhook. When a respondent submits the specified form, Typeform sends the response data to this trigger. Configure the Form ID to watch, and optionally simplify answers into key-value pairs. The trigger verifies webhook signatures using HMAC SHA-256 for security.
Frequently asked questions
Are the payloads verified?
Yes — the trigger verifies webhook signatures using HMAC SHA-256, so a forged POST cannot start your workflow.
How do I get simpler answer data?
Enable the option to simplify answers into key-value pairs, which is far easier to map than Typeform's full nested response structure.
Which form does it watch?
The one whose Form ID you configure — use a separate trigger per form.
Which credential does it need?
A Typeform credential.
Build with the Typeform Trigger node
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Typeform credentials first.
Open BusyBotLast updated . Spotted something wrong? Tell us.