Daily personalized Skool invites from your prospect sheet

Build me an agent workflow that drains my Skool community invite queue every weekday morning with personalized outreach instead of a generic mass invite.

Trigger: cron, every weekday (Monday through Friday) at 8:00am America/New_York.

Inputs I will provide when I save the workflow: the Google Sheets spreadsheet ID and the tab/range that holds my prospect list, the name of my Skool group, and the Gmail address I send from. My sheet has these columns in this order: name, email, context (where I met them and why they would like the community), status, and invited_at.

Steps the agent should run on each fire:

1. Use Google Sheets Get Values to read the full prospect tab. Filter the rows down to ones where the status column is exactly "pending" and the email column is non-empty. Stable-sort by sheet row order so the oldest entries get invited first. Take at most the first 25 rows. If there are zero pending rows, do nothing and exit cleanly.

2. For each selected row, draft a short, warm, personal invitation email (about 4 to 7 sentences). It should: greet the person by first name, reference the specific context from the context column (where I met them and why they would like this community), invite them to join my Skool community, and let them know the official Skool invite link will arrive in a separate email right after. Keep the tone like a one to one note from me, not a marketing blast. No emojis, no marketing-style subject lines. Subject line should feel like a personal email.

3. Send that draft via Gmail Send a Message from my address to the prospect's email.

4. Immediately after the Gmail send succeeds, call Skool Invite Member with that prospect's email so the official Skool join link is delivered separately by Skool.

5. Update that row's status column to "invited" and the invited_at column to today's date in ISO format (YYYY-MM-DD). Use Google Sheets to write back to the exact same row. If the platform supports a targeted update, prefer that; otherwise append a new row to a sibling "invite_log" tab with the email, status "invited", and the date, and treat that log as the source of truth for which prospects have already been contacted.

Error handling: if any single prospect fails (bad email, Skool rejects the invite, Gmail rate limit), log the failure and continue with the next row instead of failing the whole batch. Do not mark a row as invited unless the Gmail send succeeded. If the Skool invite fails after the Gmail send, leave the row as pending and add a short note in the context column so I can see it on the next run.

At the end of the run, return a short summary: how many prospects were invited, how many failed and why, and how many pending rows are still in the queue.