Apps › Productivity

Jotform automation with Bizomate

Jotform collects orders, requests and applications, files included. Bizomate starts a workflow the moment a submission arrives, with each answer as a named field made from its question and every upload as a file the next step can save or send. It can update the submission as the work moves on. Every run leaves a record of what it did.

Start free See the templates

On every plan, Free included.

At a glance

Label	Value
Plans	Every plan
Connect	An API key and your Jotform region
Starts runs	Instantly
Kind	Connected app · Productivity

What can start a workflow

New submission
When someone submits a Jotform form

Each answer arrives as a named field made from its question; uploads come as files. A submission that already started a run does not start another. Set up with Jotform when you publish.

What a workflow can do with it

Find submissions
A form's submissions, newest first, since a date and with an answer you give

Since a date, and with the answer you give to one question; up to 1,000, newest first.

Get a submission
One submission, with its answers named and its uploads as files

Its answers named and its uploads as files.

Update a submission
Changes the answers you name on one submission

Changes only the answers you name; the rest keep theirs.

How you connect it

In Jotform, select your profile picture › Settings › API › Create New Key, with Permissions set to Full Access — a Read Access key cannot add the trigger's webhook or update a submission. Paste it into Bizomate under API key, and choose the Region: Standard for jotform.com, EU for eu.jotform.com. Bizomate tests the key before saving, and Test answers "Reached {your username} · Jotform", or "· Jotform EU".

Publishing a workflow with New submission adds a webhook to the form in Jotform, and unpublishing removes it. Jotform does not sign its webhooks, so Bizomate fetches each submission from Jotform with your key before a run starts; a call naming a submission the form does not have starts nothing.

The key is encrypted before it is saved, used only when a step runs, a trigger is set up or a test calls Jotform, and never shown again — not to you, your colleagues or Bizomate support. It belongs to one workspace, the Code step cannot read it, and revoking the connection wipes it at once.

In the help centre: Connect Jotform, Start a workflow from a Jotform submission, Find, get or update Jotform submissions and Pass files between steps.

Questions about Jotform

How do the answers arrive in the workflow?

Each answer arrives as a named field, made from its question, so the next step uses Delivery address or Order number rather than a position in a list. A file someone uploads comes as a file the next step can attach to an email or save.

Why does the key need Full Access?

The trigger adds a webhook to your form, and Update a submission changes answers; Jotform allows both only with a Full Access key. A Read Access key can find and read submissions, but publishing a workflow with the trigger fails with it.

How does Bizomate know a submission is real?

Jotform does not sign the calls it sends, so Bizomate does not take the call's word for it: it asks Jotform for the submission with your key, and starts a run only if that submission is on the form you chose.

Can a workflow mark a submission as handled?

Yes. Update a submission changes the answers you name — a Status question set to Paid, say — and leaves the rest as they were.

Templates with Jotform

OperationsFree

Jotform submissions into Airtable

Every Jotform submission is added to an Airtable table, one field for each answer.

Jotform → Airtable BBy Bizomate