Weekly recruiting pipeline digest in Notion

Every Monday at 8am, publish a weekly recruiting pipeline digest to Notion summarizing what happened in Willo over the last 7 days. Recruiters should be able to open one Notion page on Monday morning and immediately know who to chase, who to review, and how the pipeline is trending.

Trigger: cron, weekly, Mondays at 8am in the org's timezone.

Step 1. Pull the pipeline. Call Willo List Interviews to enumerate every active interview (job / position). For each interview, call Willo List Participants and keep participants whose invite or last activity falls in the last 7 days. Paginate until you have them all.

Step 2. Compute headline metrics for the week across all interviews: new invites sent, responses received, candidates currently in Review, Accepted, Rejected, and still awaiting response (invited but no submission). Also build a per-interview breakdown of the same numbers so recruiters can see which roles are moving.

Step 3. Identify the top 3 candidates to review this week. Rank completed responses in the last 7 days by reviewer score if scores exist, otherwise by AI summary sentiment / recency. For each of the top 3, call Willo Get Participant to fetch the AI summary and transcript, and write a one-line takeaway (e.g. "Strong communicator, 6 years of B2B SaaS AE experience, wants to relocate to NYC").

Step 4. Build a stalled list. From the participant data, find candidates who were invited more than 5 days ago and still have not submitted a response. Include their name, the interview they were invited to, and how many days ago the invite went out.

Step 5. Publish to Notion. Call Notion Create a Page as a child of a configurable parent (a "Weekly Recruiting Digest" page or database that the user has shared with the Notion connection). Title the page "Weekly Recruiting Digest, week of {Monday date}". Structure the body as: (a) Headline metrics at the top as a small callout or table, (b) Per-interview breakdown as a table with columns for interview name, new invites, responses, in review, accepted, rejected, awaiting, (c) Top responses to review section with 3 bullet-style entries (candidate name, interview, one-line AI takeaway, link back to Willo if available), (d) Stalled candidates section listing anyone invited > 5 days ago with no response.

Configuration the workflow should expose: the Notion parent page or database ID, the timezone for the 8am cron, and the stalled threshold in days (default 5). Everything else can be inferred from the connections.

Keep the tone of the Notion page factual and scannable, not marketing-y. This is an internal ops artifact, not a candidate-facing document.