Set up date-based reminders for yourself, or scheduled actions that run on a submission without bothering anyone.
Reminders
Reminders notify you on a date you choose — they fire on the day, not at a set time. They're personal — only you see your own. To add one, open a submission, click the gear icon, and pick Reminders.
Fill in a date and a short message. By default the reminder runs once. Switch to Recurring if you want it to repeat, and pick how often (every day, week, month, or year) and when it should stop.
If you have a phone number on file, you can also have it text you, not just email you.
Pulling a date from your form
Instead of typing a date, you can have the reminder use a date that's already on the submission. On the When field, switch from Date to Form data and pick the form field you want.
Once you do, the reminder follows that field. If the date on the submission gets updated later, the reminder shifts to match — no need to come back and edit it.
The same option exists for the end date of a recurring reminder ("Ends On") and for how many times it should run ("Occurrences").
Use Case: Set a reminder on the Renewal Date field. If the renewal is pushed back, the reminder moves with it automatically.
A reminder bound to a field fires on that field's date. If you want a schedule offset from a date — three days before a renewal, a week after an onboarding — that's the Create Reminder trigger's territory; see Setting up an automation below.
Optionally run something else
A reminder can also fire one of your form's triggers when it goes off — for example, sending a custom email or sharing the submission. Pick one in the Trigger field when you're setting up the reminder, or leave it empty.
Paused reminders
If a reminder is pulling a date or number from your form and that field becomes empty or unreadable, the reminder pauses itself instead of firing wrong. Paused reminders show up in their own section in the Reminders modal with a short explanation.
Click Resume to try again once you've fixed the field, or Delete to remove the reminder.
Automations
Automations are scheduled actions tied to a submission instead of a person. There's no recipient and no message — they just run a task on a schedule. The most common example is generating a monthly invoice from a customer record.
To see what's running on a submission, click the gear icon → Automations. From there you can delete any of them, or resume one that has paused itself. (Pausing isn't manual — an automation pauses on its own when the form data it depends on becomes unreadable, the same way reminders do.)
You don't add automations from this modal. They're created automatically by a form trigger — see the next section for how to set that up.
One lifecycle rule to know: denying a submission deletes its automations, so a denied customer record stops invoicing itself. Approval does not — automations keep running on approved submissions until their schedule ends or someone deletes them.
Use Case: A new customer signs up. Every month after that, an automation creates an invoice from their record until their contract ends.
Setting up an automation
Automations come from the Create Reminder trigger when its Type is set to "Run a trigger on schedule."
- Open the form in the flow editor and add a Create Reminder trigger.
- Set Type to Run a trigger on schedule. The user, message, and SMS fields hide automatically.
- Pick the date the schedule should start from (usually a date field on the form) and how far before or after that date the first run should happen.
- Set the frequency and when it should stop. Automations are always recurring — the One Time choice belongs to personal reminders.
- Under Run Trigger After Reminder, pick which existing trigger should fire each time (for example, a "Create Invoice" trigger you've already set up on the form).
- Save.
After that, each submission that reaches the trigger gets an automation with the schedule you configured — provided the date field the schedule is built on has a value. A submission with that field empty is skipped rather than scheduled wrong.