Until now, a form's automations fired the same way for everyone who submitted a response, regardless of how they answered. Workflow fields were the one exception, routing people into a workflow based on their field selection. But the right follow-up usually depends on the answer, and a lot of you asked us for exactly that: a campus-specific welcome email for the campus someone picked, a first-time guest date when they check the box, or sending specific training materials for the team they chose.
With today’s release, when you add an automation to a form, you can choose whether it runs for every submission or only for submissions with a particular response. (If you've used conditional automations in Calendar, this will feel familiar.)
How it works
When you add an automation, you'll see a new option for who it applies to:
All submissions: works just like before.
Submissions with a response: pick a field and the response that triggers it.
:quality(80))
You can trigger on the fields where a response is a set choice:
Dropdown and checkbox basic fields
Yes/no, dropdown, and checkbox custom fields
A person's campus selection
From there, every action you already use is available: send an email from a template, add someone to a workflow, update a profile field, add them to a group, or create a task. The difference is that it happens only for the people who answered the way you specified, and it happens the moment they submit, with no waiting on a list to refresh.
Each automation triggers on one response, so to send a different welcome email for each campus, you'd set up one automation per campus. They all can now live on the same form.
We hope this takes some more manual work out of your follow-up. If there are other fields or form responses you'd love to trigger on, or actions you wish you could automate straight from a form, we'd love to hear what's next on your list!
💙 The People Team,
Zane, Usborn, Shawn, Shane, Saryn, Kody, Julia, Gabi, Fred, Dave, and Benson