Weekly stale deal rescue with per-owner Slack shortlists

Build me an agent workflow that runs every Monday at 9am ET (cron trigger, weekday and time parameterized) and performs a stale-deal rescue across every open pipeline in my General Input CRM workspace. The goal is rescue, not noise: every recommendation must be a real, specific next move, not a generic follow-up reminder.

Step 1. Inventory. Use General Input CRM List Pipelines to enumerate every pipeline. For each pipeline, call Get Pipeline Board to load all open cards in board order. Skip any pipelines the user has excluded via a configured scope parameter.

Step 2. Identify stale cards. Treat a card as stale when it has been sitting in its current stage longer than a stale threshold (default 14 days, parameterized) and has no recent note or touchpoint within the same window. Always skip cards whose status is already won or lost, and skip cards owned by inactive members (cross-check against List Members).

Step 3. Deep read each stale card. For every candidate, call Get Card to pull full detail: owner, contacts, notes, expected close, amount, and recent timeline. Identify the primary contact and grab their email.

Step 4. Check Gmail for fresh activity. Use Gmail List Messages with a search query that filters on the primary contact's email address scoped to the last 21 days (e.g. from: or to: that address, newer_than:21d). If there are matching messages, use Get a Thread on the most relevant thread to read context. The point is to distinguish a card that is quietly progressing in email from one that is truly cold.

Step 5. Decide a specific recommendation. Based on the card state and email signal, pick exactly one of: re-engage with a fresh angle (and say what the angle is, grounded in the card or recent thread), escalate to the owner's manager, mark cold, or close lost. The recommendation must be concrete enough that a rep could act on it without thinking.

Step 6. Write it back to the card. For each stale card, use General Input CRM Create Task to file a follow-up task on the card with the suggested action as the title and a sensible due date (within 3 business days), and use Create Note to append a note that captures the reasoning, the email signal you found (or did not find), and any reference to recent thread context.

Step 7. DM each owner their shortlist in Slack. Group the stale cards by owner. For each owner, look up their Slack user by email (Slack Bot Look Up User by Email), Open a Conversation to get the DM channel, then Send a Message containing a ranked shortlist of their top stale deals (default cap 5, parameterized) sorted by deal value and time-in-stage. Each line should show the deal name, the one-line recommendation, and a direct deep link to the card. Owners with no stale cards get no DM.

Parameters I should be able to tune at setup and per run: the weekday and local time, the stale threshold in days (default 14), the email activity lookback window in days (default 21), the per-owner shortlist cap (default 5), and an optional include/exclude list of pipelines so RevOps can scope cadence per pipeline.

Hard rules: never DM an owner about a card that is already won or lost; never DM inactive members; never produce a recommendation that boils down to 'follow up' with no specifics; always include the deep link to each card in the Slack message so the rep can act in one click.