New on the blog: why AI belongs in the feed →

Recurring Work in Gravity Forms: Four Examples That Run Themselves

A lot of client work repeats on a calendar: a statement every month, an inspection every month, a report every week, a renewal every year. With GravityOps Recurring Form Submissions you save one entry, and the plugin submits that entry again on the schedule you set. Each run is a full Gravity Forms submission, so notifications, feeds and Gravity Flow workflows run exactly as they do when a person submits.

How it works, in one paragraph

Add a Recurring feed to the form and set Repeat every and Calendar unit (days, weeks, months or years), a Run time and, if you want, an End condition. When someone submits the form on your site, that entry becomes the parent of a series. On each run the plugin submits the parent’s values again as a new child entry, linked back to the parent. Update Date Field(s) sets a date field to the run date, and in Dynamic input mode Populate Anything fields are filled again at run time. You manage every series under Recurring Submissions → Queue, where you can run the next submission now, pause, resume or change the next date.

What it does not do: it never creates a blank form for someone to fill in. If you need a person to answer something every week, the child entry starts a Gravity Flow step that sends them a link. That pattern is in two of the examples below.

The four examples

  • Monthly client statements: one entry per retainer client; each month a statement entry is created and emailed, with the hourly rate kept in one Global Variable.
  • Monthly inspection assignments: one entry per property; each month a new entry starts a Gravity Flow User Input step assigned to the inspector, who gets a link to record findings.
  • Weekly client reports: one entry per client; each week Populate Anything pulls the client’s current contact and plan into the new entry, and the report goes out.
  • Yearly membership renewals: one entry per member; each year a renewal record is created and the renewal notice is sent.

Coaches and their clients use the same pattern for weekly check-ins: weekly coaching check-ins in Gravity Forms.

Before you build

  • Start each series by submitting the form on your site. Entries created through GFAPI::submit_form or the REST API don’t start a series, so imports and API calls won’t set off runs by accident.
  • Every run sends the form’s notifications. Check who they go to before you start a weekly series.
  • The plugin’s worker runs on WP-Cron about every 15 minutes, so a 09:00 run starts shortly after 09:00. On a low-traffic site, a real server cron keeps it on time.
  • Cancel Series in the Queue is part of the Premium plan; pausing a series or turning off its feed works on every plan.