Build a form with a workflow

Every response runs a workflow you draw next to the form: conditions, routes and waits, then email, Sheets, Slack, Notion or a webhook.

  • Visual builder, no code
  • Test runs before you publish
  • Run history for every response
Start free with emailContinue with Google

Free forever, no card. Approvals, reminders for unfinished forms and emailing respondents from the built-in sender are part of Pro: $29/month, or $25 billed yearly.

The client intake workflow from the example below, in the editor. Click to enlarge.
  1. Build the form, or start from a template.
  2. Add steps under the trigger: an email, a sheet, a Slack post, a condition or route on any answer.
  3. Test it against sample answers, then publish. Every response runs it, with its own run history.

What starts it

Form submitted: every response the form accepts runs the workflow once, with all the answers available to every step. Or Form abandoned (Pro): the workflow starts when someone fills in part of the form and stops, so you can remind them.

What it decides

Logic steps read the answers and shape the path:

  • Condition: a yes/no test on any answer (“total over 500”, “country is not NL”, “verified is No”), with a branch for each outcome.
  • Route: several branches, each with its own rule, and one default for everything else. Regions to regional teams, product lines to owners.
  • Wait: pause for a set time before the next step. A reminder two days later, a follow-up a week after.
  • Approval (Pro): hand the submission to a person. Reminders while they sit on it, a backup approver when they still do, and send back for changes, which mails the respondent a link to fix their answers and runs the workflow again from there.

What it does

Action steps carry the answers out of the form:

  • Email your team, an approver or the respondent, with any answer piped into the subject and body. To respondents through your own Gmail, Outlook or SMTP on Free, or the built-in sender on Pro.
  • Your tools: send the response to a spreadsheet, Notion or Airtable, post to a chat channel, text a phone, or call any URL with a webhook you shape yourself. Connect each once for the team; every workflow can then use it.

How it behaves

  • Visual builder. The workflow is a diagram: trigger at the top, steps and branches below. What you see is what runs.
  • Test runs. Run the workflow against sample answers before anyone submits, and see each step’s result.
  • Run history. Every submission has its run: which steps ran, which branch it took and where it’s waiting.
  • Published versions. Editing never touches a live workflow. Runs that started finish on the version they started on.
  • Failures don’t disappear. A failed step shows why, and you can retry it once it’s fixed.

A client intake form, end to end

A new-client form with the client’s details and what they need.

  1. Email the client a confirmation, with their name and the service they picked filled in.
  2. Send the response to the team’s spreadsheet.
  3. Route on the service: web projects to one channel, design to another.
  4. Condition on the budget: over a threshold, email the sales lead straight away.

Four steps, no code, and the whole path visible on one screen.

Good for

Anything where a submission is the start of work rather than the end of it: intake and onboarding, quote and purchase requests, registrations that need a confirmation, support requests that must reach the right person, and any form whose answers currently get copied somewhere else by hand.

Build your workflow free