Monday morning AI visibility digest for outbound prospecting

Build me an agent workflow that runs every Monday at 9am ET and produces a GEO buying-signal digest for our outbound SDR team. The unique angle is Nexuscale's AI search visibility score: when a target account's visibility on ChatGPT, Perplexity, and Gemini drops week over week, that is a real pain point our reps can open a cold outreach with.

Trigger: cron, every Monday at 9:00 America/New_York.

Inputs the workflow should expose as configuration:

1) The Google Sheets spreadsheet id and tab name for the target-account watchlist. Expected columns: domain, previous_geo_score, last_checked_at. 2) The Slack channel id (or name) where the digest should be posted. 3) An optional meaningful_move_threshold in points, default 10, that decides which accounts land in Pitch this week versus Watch.

Steps the agent should follow:

Step 1. Use Google Sheets Get Values to read the entire watchlist range (all rows including headers). Parse each row into { domain, previous_geo_score, last_checked_at, rowIndex }. Skip blank rows. If previous_geo_score is missing or not a number, treat previous as null (first-time run for that account).

Step 2. For each domain, call Nexuscale Check AI Visibility (GEO) to fetch the current score across ChatGPT, Perplexity, and Gemini. Handle failures gracefully: on 404 or missing data, keep the account in the list with a note that no score was returned this week; on 429, back off and retry; on 402 (credits exhausted), stop, post a short Slack notice explaining the quota is out, and finish. Do the calls sequentially or in small batches so we do not burst-fail the Nexuscale API.

Step 3. Compute the week-over-week delta for each account: delta = current_geo_score - previous_geo_score. First-time accounts (previous is null) get delta = 0 and are treated as neutral this week. Classify each account: drop of >= threshold points goes to Pitch this week, gain of >= threshold points goes to Watch, everything in between is Neutral and does not appear in the digest.

Step 4. Use Google Sheets Update Values to write each account's fresh score and today's date back into the previous_geo_score and last_checked_at columns for the correct row. Use the rowIndex captured in step 1 so the write is targeted, not a full sheet overwrite.

Step 5. For every account that landed in Pitch this week or Watch, draft a single-line suggested opener that references the specific visibility gap. Pitch this week openers should acknowledge that the account is showing up less often in AI answers and offer a concrete reason to talk. Watch openers should note the competitor angle for internal awareness, not for sending to the prospect. Keep each opener under 25 words, no em dashes, no generic phrasing, no fake stats.

Step 6. Use Slack Send a Message to post the digest to the configured channel. Format: a short header line naming the week, then a Pitch this week section listing accounts ordered by biggest drop first (domain, current score, delta, one-line opener), then a Watch section listing accounts ordered by biggest gain first (same fields). If either section is empty, say so in one line rather than omitting the heading. Cap each section at 10 accounts and mention how many additional accounts were flagged but not shown.

Design goals for the agent's system prompt: optimize the digest for an SDR to work top-down on Monday morning. The reader should be able to pick the top three accounts to call in under a minute. Do not dump raw numbers. Do not include Neutral accounts. Do not restate the methodology in the message. Keep the tone crisp and specific to the account.