Gravity Forms can schedule when a form is open, but it has no setting that repeats a submission. The dependable way to make a form “repeat” is to keep one saved entry and resubmit it on a timer. Each run goes through the full Gravity Forms submission, so notifications, add-on feeds and Gravity Flow workflows fire as if someone had clicked Submit. You can build that with WP-Cron and GFAPI::submit_form(), run it from Zapier or Make, or use a plugin such as Recurring Form Submissions, which we build and maintain. This guide walks through each option, the settings that matter, and one worked example.
Plugin settings and behavior below were checked against Recurring Form Submissions 1.5.3 on November 17, 2026.
Key takeaways
- “Repeat this form” usually means one of two things: a submission that should happen again on a schedule (an invoice, a report, an assignment), or a person who should fill something in again on a schedule.
- Both are handled by resubmitting a saved parent entry on a timer. Every run creates a new child entry with its own notifications and feeds.
- If notifications and feeds need to fire, use
GFAPI::submit_form()or the REST API form submissions endpoint.GFAPI::add_entry()stores an entry and skips both. - When a person has to fill something in every week, let the scheduled entry start a Gravity Flow User Input step assigned to them. They get a link to that entry. Nobody is sent a blank form.
- Every WordPress schedule depends on WP-Cron. On production sites, point a real server cron at it.
What clients mean by a repeating form
When clients ask for a form that repeats, they almost never want the same empty form to appear somewhere every Monday. They want something to happen on a schedule, and the form is where the data for it already lives. The requests we see most often from agencies:
- A monthly retainer invoice or statement per client, emailed on the 1st.
- A weekly report entry whose numbers come from other forms through Populate Anything, emailed to the client every Monday morning.
- A monthly inspection assignment per unit that lands in the inspector’s Gravity Flow inbox.
- A yearly membership renewal entry that sends the renewal notification and runs the CRM feed.
In each case one entry holds the stable data: who, what, how much. That entry is the parent. Each scheduled run resubmits it and creates a child entry, which is what your notifications, feeds and workflows act on. The parent stays as it is, so next month starts from the same place.
Option 1: WP-Cron and a GFAPI::submit_form() snippet
If one client needs one form repeated at one interval and you have a developer on hand, custom code is a reasonable answer. The shape of it:
- Store the parent entry ID and the interval, in an option or in entry meta.
- Register a recurring event with
wp_schedule_event(). Core ships hourly, twice daily, daily and weekly intervals. Anything else, such as monthly, needs a custom interval through thecron_schedulesfilter. - In the event callback, load the parent with
GFAPI::get_entry(), map its values to the form’sinput_keys, and pass them toGFAPI::submit_form(). - Check
is_validin the result and log failures somewhere a person will see them.
The call itself is the easy part. The time goes into everything around it. A fixed 30-day interval drifts away from calendar months: a series that starts on January 1 puts its twelfth run on December 27 in a non-leap year. Run times shift by an hour at daylight-saving changes if you schedule in UTC. A series that starts on the 31st needs a rule for February. Multi-input fields such as Name, Address and Checkboxes use keys like input_1_3, and file upload fields need separate handling. And sooner or later someone who isn’t a developer will need to pause one client’s series without touching code.
Option 2: Zapier or Make on a schedule
If the agency already runs client automations in Zapier or Make, a schedule trigger plus an HTTP request to the Gravity Forms REST API (v2) works. Send the request to /wp-json/gf/v2/forms/{form_id}/submissions for a full submission. The /wp-json/gf/v2/entries endpoint creates an entry without the submission process, so notifications and feeds don’t run.
The trade-offs: the values for each run live in the Zap or scenario, not in WordPress, so a change to the client’s rate means editing the automation rather than the entry. Every run counts against the plan’s task or operation allowance. And there is one more account to hold credentials for when a client leaves.
Option 3: Reminder emails that ask people to fill the form again
Some requests really do need a new answer from a person each time, such as a monthly satisfaction survey. Then a recurring email with the form link is the honest fit, sent from the client’s email tool or from a notification-scheduling add-on such as Gravity Wiz’s Notification Scheduler. Gravity Forms dynamic population can pre-fill known fields from the link’s query string, so the person isn’t retyping their name and account number.
The limit: reminders and entries aren’t connected. Nothing tells you who didn’t respond this month, and chasing them is manual.
Option 4: Gravity Flow scheduled steps
Gravity Flow can hold a step until a date or a delay has passed, and it can send reminders to assignees. That handles timing inside one entry’s workflow, for example a follow-up 30 days after an application. It doesn’t create a new entry each month on its own. Paired with a recurring submission, though, it covers the case people most often mean, as the worked example below shows.
Option 5: Recurring Form Submissions
Recurring Form Submissions adds a feed to the form. When an entry is submitted and the feed’s conditional logic matches, that entry becomes the parent of a series. On each scheduled run the plugin resubmits the saved parent entry with GFAPI::submit_form(): Populate Anything fields are populated again, calculations are recomputed, and the result is a full submission with notifications, feeds and Gravity Flow workflows. It never creates a blank form for someone to fill in.
The feed settings, as they appear in version 1.5.3:
- Repeat every and Calendar unit: a whole number from 1 to 1000, and Days, Weeks, Months or Years.
- Run time: Preserve original submission local time, or Specified local time with Specified time (HH:MM) in 24-hour format.
- Timezone (IANA name or UTC offset): runs are calculated in that zone (the site’s timezone by default) and keep their local time across daylight-saving changes.
- Allow Monday through Allow Sunday: if an occurrence falls on a day you haven’t allowed, it moves forward to the next allowed day.
- End condition: Number of successful submissions, End date, or Number from parent form field. The last one reads a Number field on the same form, so each entry can carry its own count.
- Missed runs: Run one missed occurrence, then continue (the default), or Skip missed occurrences and continue at the next future time.
- Consecutive failure limit: how many failures in a row a series tolerates. Leave it blank to inherit the global setting.
Monthly series handle short months: a series anchored on the 31st runs on the last day of February, April, June, September and November.
Version 1.5.0 (September 14, 2026) rebuilt the scheduler and added the Queue, where every series keeps an attempt history: when each attempt was due, when it started and finished, the outcome, the child entry it created, how late it ran and why, and the IDs of any fields that failed validation. From the Queue you can Run Next Submission Now, Retry Failed Submission, Pause, Resume, or Change next submission, with a preview of the next five occurrences.
A series stops when its end condition is met, when you pause it or deactivate its feed, or when you cancel it with Cancel Series, which is a Premium plan action. Trashing or deleting the parent entry also ends its schedules, and restoring the entry doesn’t restart them. You can also attach Gravity Forms notifications to the plugin’s events: a resubmission going through, one failing, and a series finishing.
How the options compare
| Approach | Each run is a full submission | Where the schedule lives | Good fit | Watch for |
|---|---|---|---|---|
| WP-Cron + GFAPI::submit_form() | Yes | Your code | One client, one interval, a developer on hand | Month ends, daylight saving, missed runs, logging |
| Zapier or Make + REST API | Yes, with the submissions endpoint | An external account | Agencies already running client automations there | Task costs, run data outside WordPress |
| Reminder emails | Only when the person submits | Email tool or notification add-on | A genuinely new answer each time | Chasing non-responders by hand |
| Gravity Flow scheduled steps | No new entry on its own | Workflow step settings | Timing inside one entry’s workflow | Doesn’t repeat by itself |
| Recurring Form Submissions | Yes | Feed settings in WordPress | Several series, or non-developers managing them | Cancel Series needs Premium; relies on WP-Cron like the rest |
Worked example: monthly unit inspections
A property-management client has 40 units. Each unit needs an inspection every month by the inspector assigned to it, a sign-off from the property manager, and a report to the owner. Here is how we would build it.
- The form. “Unit inspection” has a Unit drop-down populated by Populate Anything from the client’s units, an Inspector field (a Gravity Flow Assignee field), the checklist fields, a Notes field, and a Number field called Inspections this lease.
- The parents. The office submits one entry per unit, once, filling in Unit, Inspector and Inspections this lease (12). The checklist stays empty, and its fields are optional on the form.
- The recurring feed. Repeat every 1, Calendar unit Months, Run time set to Specified local time at 07:00, Timezone America/Chicago, Allow Saturday and Allow Sunday unchecked, Missed runs on Run one missed occurrence, then continue, and End condition set to Number from parent form field, pointing at Inspections this lease.
- The workflow. In Gravity Flow: a User Input step assigned to the Inspector field with the checklist and Notes editable, then an Approval step for the property manager, then a Notification step that sends the completed report to the owner.
- Each month. On the scheduled day, or the next weekday, each unit’s parent is resubmitted. That creates a child entry, the workflow starts, and the inspector gets an email with a link to that unit’s inspection, already carrying the unit and its details. They complete the checklist in the step, the manager approves, and the owner gets the report.
Two details save a support call later. Keep the inspector’s checklist fields optional on the form: if a field the parent left empty is required, every resubmission fails validation, and the Queue lists those field IDs. And the office watches one screen, the Queue, instead of 40 calendar reminders.
When a person has to fill in the form each week
The pattern above covers it. The recurring entry carries what you already know: who, which account, which week. Its Gravity Flow workflow assigns a User Input step to the person, who gets a link to that entry and fills in this week’s fields. Gravity Flow’s assignee reminders handle the nudging, and the step status shows who hasn’t finished. Without Gravity Flow, use Option 3 and accept that tracking responses is on you.
What breaks scheduled submissions, whichever method you use
- WP-Cron needs traffic. WP-Cron runs when someone loads a page, so on a quiet client site a 07:00 run can wait for the first visitor. Set
DISABLE_WP_CRONin wp-config.php and call wp-cron.php from a server cron every few minutes. Recurring Form Submissions labels late attempts with what the evidence shows (normal polling, a delayed cron dispatch, a busy processing pass), but it still needs cron to run. - Validation. A resubmission is validated like any other submission. Required fields left empty on the parent, and fields with No Duplicates turned on, will fail.
- Feeds that shouldn’t repeat. A user registration or “create contact” feed runs again on every child entry. Give it conditional logic, or keep it on a form that doesn’t repeat.
- Payments. A scheduled resubmission can’t enter card details. For recurring billing, use the subscription feature of your payment add-on.
- Staging copies. Cloning a production site copies its schedules. Pause the series or block outgoing email on staging before cron runs there.
FAQ
Can Gravity Forms create an entry every month without a plugin?
A WP-Cron event that calls GFAPI::submit_form(), or a scheduled request to the REST API submissions endpoint, does it without a plugin. You own the scheduling edge cases.
Do resubmitted entries send notifications?
They do when the resubmission goes through the submission process: GFAPI::submit_form(), the REST submissions endpoint, or Recurring Form Submissions. GFAPI::add_entry() and the REST entries endpoint don’t send them.
Can I change the schedule of a series that’s already running?
In Recurring Form Submissions, change the recurrence in the feed settings and apply the saved schedule to existing series, or use Change next submission in the Queue to move the next run and continue from there.
Where to start
Choose by who will maintain it. A single series on a site you manage closely can live in code. If the client’s team will run the schedules, or you have more than a handful of series across client sites, keep them in feed settings where a non-developer can see, pause and fix them.
If you’d rather not maintain the cron code, see the Recurring Form Submissions plans or start with the documentation. Set up one series on a test form, open the Queue, and watch the first attempt land.
Discuss this post
Questions, corrections or your own approach? Reply in the community thread.