Custom Form automations can automatically take action when someone submits a form.
This can help your church follow up more consistently, organize people into the right groups or lists, assign tags, start workflows, or add someone to a campaign.
When editing a Custom Form, go to the form’s Automations section.
From there, click Add Automation to create a new automation.
Custom Form automations apply to the Primary Submitter of the form.
The primary submitter is the person connected to the form submission, usually based on the first set of contact information fields when Link submission to Person is enabled.
Because automations apply to the primary submitter, make sure your form is collecting the submitter’s information clearly.
Depending on your account and form settings, Custom Form automations may allow you to:
Automations can also be applied to other individuals created by specific sections of the form.
Use Add to Group when the person who submits the form should be added to a group.
Examples:
When adding someone to a group, you may also be able to choose a classification for that person in the group, such as Member, Supporter, Leader, or another classification used by your church.
Use Add to Workflow when the form submission should begin a follow-up process.
Examples:
Workflows are helpful when the follow-up process includes multiple steps, staff assignments, messages, or manual actions.
Use Assign Tag(s) when you want to mark the person with one or more tags.
Examples:
Tags can help you organize, filter, report, and communicate with people later.
Use Add to Campaign when the person should receive a sequence of communications after submitting the form.
Examples:
Campaigns are useful when the response should trigger a planned sequence of messages.
A form itself can have tags in the form settings. These tags help organize the form.
Automation tags are different. Automation tags are assigned to the person who submits the form.
Tags applied directly to the form do not automatically carry over to the submissions or the person who submitted a form.
For example:
Automations can save time, but they should be used thoughtfully.
Before sharing a form widely:
When someone submits a baptism interest form:
When someone submits a volunteer application:
When someone submits a small group interest form:
Automations run when the form is submitted.
Automations are intended to help with future form submissions. They should be tested before the form is shared publicly.
If you add an automation after people have already submitted the form, the automation may not apply to older submissions unless you manually take action or use another available process.