Weekly WPForms digest in email and Slack

Every Monday at 9am in my local timezone, run an agent that produces a weekly digest of WPForms activity across the forms I care about, then emails it to me and posts a shorter version to a Slack channel.

Trigger: cron, every Monday at 9am.

Inputs the agent should accept as configuration: the list of WPForms form IDs to include, the Gmail recipient address (or addresses) for the full digest, and the Slack channel for the short team version.

Steps the agent should follow each run:

1. For each configured form ID, use WPForms List Form Entries to pull all submissions from the last seven days. Page through if needed so nothing is missed.

2. Also pull the seven days before that (days 8 to 14 back) for each form so you can compute a week-over-week change.

3. Analyze the entries. For each form, calculate total submissions this week, the percent change versus last week, and the top recurring themes you see in the field values. Themes typically include campaign or UTM sources, product interest, plan or pricing intent, and support topics, but adapt to whatever fields the form actually has.

4. Identify notable individual entries that look high value. Default signals: business email domains, senior job titles, larger company size, mentions of specific products or competitors, or explicit requests like demo or pricing. Pick the top three to five across all forms.

5. Flag anomalies. Call out sudden spikes in volume on any form, unusual drops, suspicious clusters like many submissions from the same IP or domain in a short window, gibberish in name or message fields, or other patterns that look like spam or bot traffic.

6. Compose the digest. Write a short narrative summary at the top (two to four sentences) covering the headline numbers and the most interesting takeaway. Below that, use bullets organized by form: volume and week-over-week change, top themes, the high value entries, and any anomalies. Keep it scannable.

7. Use Gmail Send a Message to email the full digest to the configured recipient. Subject line should include the date range, for example: WPForms weekly digest, May 12 to May 18. Body is the full digest in clean HTML or plain text.

8. Use Slack Send a Message to post a shorter team version in the configured channel. The Slack version should fit in roughly 10 to 15 lines: the narrative summary, one line per form with volume and week-over-week change, and any anomalies that need attention. Skip the long entry breakdown since the email already has it.

If a form had zero submissions in the last seven days, still include it in the digest with a zero count so quiet forms do not silently fall out of view. If WPForms returns an error for a specific form ID, note it in the digest rather than failing the whole run.

Tone: concise, practical, focused on what someone running growth or operations actually needs to act on this week.