Jotform · New submission starts a run the moment someone submits one of your Jotform forms. Each answer comes under a name made from its question — Delivery address is {{ trigger.delivery_address }} — and uploaded files come with the item. It is an instant trigger, and publishing sets it up in Jotform 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 Jotform connection with a Full Access key. See Connect Jotform.

Steps

  1. 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.

  2. Under Jotform, select New submission. It reads Jotform · instant.

  3. In Connection, choose your Jotform connection.

  4. In Form, choose the form — for example Northwind Logistics delivery request. The panel lists its questions and the name each answer will have.

  5. In Form, choose the form — for example Northwind Logistics delivery request. Each form shows how many submissions it has.

  6. Add the steps, then Publish. Bizomate adds a webhook to the form in Jotform.

    The panel reads Waiting for the first event.

Test it with a real submission:

  1. Open the form and submit it.
  2. Within seconds the panel reads Listening — instant, with the last submission.
  3. Within seconds the panel reads Listening — instant, with the last submission — New submission · Northwind Logistics delivery request.
  4. On Output, select Use the last event, then Test run.

What the trigger gives

Write What it is
{{ trigger.delivery_address }} and so on Each answer, under a name made from its question. A name or address question gives its parts too — {{ trigger.full_name.first }}.
{{ trigger.delivery_address }} and so on Each answer, under a name made from its question. A name or address question gives its parts — {{ trigger.full_name.first }}, {{ trigger.delivery_address.city }}. A date or phone number comes as Jotform shows it. Every question has its name, empty when it was not answered.
{{ trigger.id }} The submission's id — for Get a submission and Update a submission.
{{ trigger.formId }}, {{ trigger.formName }} The form.
{{ trigger.submittedAt }} When it was submitted, in UTC.
{{ 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.answers }} Every answer as Jotform sent it: each with its key, question, questionId, type and value.
{{ trigger.answers }} Every answer as Jotform sent it: each with its key, question, questionId, type and value. An upload's value is its address in Jotform.
The files Each upload, as a file with the item.

What happens next

  • Each submission starts one run of the live version, in Production.
  • Uploads come as files, ready for a later step to save or attach. See Pass files between steps.
  • Every publish sets the webhook up again. Changing to another trigger and publishing, or deleting the workflow, removes it from the form.

Good to know

  • Jotform does not sign its webhooks. So before a run starts, Bizomate asks Jotform for the submission with your connection's key, and starts the run only if it exists on the chosen form. A made-up call starts nothing.
  • 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, the name stays as it was, so the step keeps working.
  • One run per submission. If the same submission is delivered again, it does not start a second run.
  • 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, so the step keeps working.
  • Edits to a submission in Jotform do not start a run — only new submissions.
  • Files larger than the limit for files between steps are left out, and the run's output says so.
  • Files Jotform will not hand over are left out. An upload larger than the limit for files between steps, or one on an account that asks for a sign-in to view uploads, does not come with the item; the run still starts, its address stays in answers, and a step that needs the file says it is missing.
  • Runs count in the month's allowance.

If something goes wrong

What you see Why What to do
Not listening — Jotform would not take Bizomate's address: … Fix it, then publish again. The key is Read Access, or was deleted. Make a Full Access key, replace it on Connections, then publish again.
Not listening — "Jotform refused: …" The key is Read Access, or was deleted. Make a Full Access key, replace it on Connections, then publish again.
Not listening — "Jotform did not say which webhook it added. Publish again." Jotform took the address but its answer did not list it. Publish again.
Waiting for the first event stays Nobody has submitted the form, or the webhook was removed in the form's settings. Submit the form, or publish again.