Typeform · New response starts a run the moment someone submits one of your Typeform forms. Each answer comes under a name made from its question — Company name is {{ trigger.company_name }} — so later steps never need to know the question's position. It is an instant trigger, and publishing sets it up in Typeform for you — see How instant triggers work.
Who can do this
Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.
Before you start
A Typeform connection whose token has Webhooks — Write. See Connect Typeform.
Steps
Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
Under Typeform, select New response. It reads Typeform · instant. Or type Typeform in Search triggers.
In Connection, choose your Typeform connection — for example Consulace Typeform.
In Form, choose the form — for example Talk to Consulace. The list shows your forms, the most recently changed first.
Add the steps, then Publish. Bizomate adds a webhook to the form in Typeform.
The panel reads Waiting for the first event — Make one happen; it appears here within seconds.
To see the name each answer will have before any response arrives, add a Typeform · Get a form step and run it: each question's key is its name.
Test it with a real response:
- Open the form's public link and fill it in — as Rohan Mehta, rohan@consulace.com, say.
- Within seconds the panel reads Listening — instant, with the last response.
- On Output, select Use the last event, then Test run.
What the trigger gives
| Write | What it is |
|---|---|
{{ trigger.company_name }} and so on |
Each answer, under a name made from its question, as the Form trigger names its fields. Text as text, numbers as numbers, yes or no as true or false, dates as 2026-10-05, a multiple choice as its label, several choices as a list of labels, a payment as Typeform gives it. A question in a question group has its own name, like any other. |
{{ trigger.id }} |
The response's id — for Delete a response. |
{{ trigger.formId }}, {{ trigger.formName }} |
The form. |
{{ trigger.submittedAt }} |
When it was submitted, in UTC — 2026-10-02T09:30:00Z. |
{{ trigger.respondent }} |
The respondent's email: the answer to the form's first email question, or else a hidden field named email. Empty when the form has neither. |
{{ trigger.hidden }} |
The form's hidden fields, by their names — {{ trigger.hidden.source }}. |
{{ trigger.score }} |
The calculated score, when Typeform sends one. |
{{ trigger.answers }} |
Every answer in Typeform's order: each with its key, question, questionId, type and value. |
What happens next
- Each response starts one run of the live version, in Production. The run's label is New response · Talk to Consulace.
- Every response is checked. Each time you publish, Bizomate gives Typeform a new secret of its own making with the webhook, and Typeform signs each response with it. A response without a matching signature is turned away and starts nothing. You never see or type the secret.
- Every publish sets the webhook up again. Changing to another trigger and publishing, or deleting the workflow, removes it from the form. Each workflow has its own webhook, so two workflows can listen to the same form.
Good to know
- Names follow the question until a step uses them. Reword a question before any step uses its answer and the name changes with it. Once a step uses it and you publish, the name stays as it was, tied to the question itself, so the step keeps working.
- New questions appear by themselves. Each response is read against the form as it is now, so a question added later has its name in the next run.
- Partial responses never start a run — only submitted ones.
- File uploads come as files with the item, fetched from Typeform with the connection's token, within the size limit for files between steps. See Pass files between steps. The answer's own name,
{{ trigger.upload_your_brief }}say, holds the file's Typeform link. A file over the limit, or one Typeform would not give, is left out and the run still starts. - Switching off does not remove the webhook. Responses still arrive and show as the last event, but start no runs.
- Runs count in the month's allowance.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Not listening — Typeform would not take Bizomate's address: Typeform refused: …. Check the connection's details on Connections. Fix it, then publish again. | The token has no Webhooks — Write, was deleted, or cannot see the form. | Replace the token on Connections, then publish again. |
| Waiting for the first event stays | Nobody has submitted the form yet, or the webhook was removed in Typeform. | Submit the form, or publish again. |
| An answer is missing from the output | The question was skipped by the respondent, or hidden by the form's logic. | Nothing to do — skipped questions have no answer. |
| A file is missing from the item | It was over the size limit for files between steps, or Typeform would not give it. | Fetch it from its Typeform link in the answer, with a step of your own, or ask for a smaller file. |