Weekly cold email infrastructure health digest in Slack

Every Monday at 8am Eastern Time, run a cold email infrastructure health digest for my Primeforge workspace and post it to a Slack channel I pick.

Trigger: cron, weekly Monday 08:00 America/New_York.

Data gathering (Primeforge):

1. Call List Workspaces and match on the workspace name I configure (store the name as an input at setup time).

2. For that workspace, call List Setups to enumerate every setup and its platform (google vs microsoft).

3. Call List Workspace Mailboxes once to get every live mailbox in the workspace, including any with a scheduled deletion date.

4. For each setup, call List Setup Domains, then for every domain returned call Get Domain DNS Records so you have the full DNS picture.

Summary rules. Build the digest around these checks:

- Total live mailbox counts, split by platform (Google Workspace vs Microsoft 365).

- Setups with zero domains attached, listed by setup name.

- Domains whose DNS records look incomplete. Specifically flag any domain missing SPF (a TXT record starting with v=spf1), DKIM, or DMARC (a TXT record on _dmarc starting with v=DMARC1). Group findings by domain.

- Mailboxes scheduled for deletion. Call out how many grace-period days remain before deletion is final, and remind the reader that scheduling can be reversed until then.

- Optional week-over-week note: if you can find your previous Monday message in the same channel, compare mailbox and domain totals and mention the delta (+3 mailboxes, -1 domain). If you cannot find one, skip this section rather than fabricate.

Posting (Slack Bot):

Use the Slack Bot Send a Message operation to post to the channel I choose. Format the digest with Block Kit blocks (header, section blocks, and dividers) so it renders as a clean scannable digest, not one long paragraph. Do not @channel unless I explicitly ask for it.

End the message with a Follow-ups section: 3 to 5 concrete, action-oriented items derived from the checks above. Examples: 'Add DKIM to sales.acme.io', 'Attach a domain to Setup Beta before it goes into rotation', 'Cancel scheduled deletion on 4 mailboxes if they are still needed (2 days of grace remaining)'.

Tone: concise, action-oriented, no filler. This is a Monday morning ops digest for an agency lead, not a marketing email. Avoid hedging language; if the data is clean, say so in one line and keep the follow-ups list short.

Inputs to expose at setup: Primeforge workspace name, Slack channel ID (or name), and the cron schedule.