Venue Agent — Full Blueprint

Every day at 12pm Sydney, a Cloudflare Worker wakes up, asks Claude Sonnet 4.5 to "run the daily follow-up cycle," and hands it 6 tools for reading/writing Gmail, Sheets, and Slack. Claude decides per-venue whether to resolve (reply found), draft a follow-up (cycle 1 or 2), or escalate (cycle 3). All email drafts land in Alec's drafts folder — nothing auto-sends until you flip a flag.

Each run is a conversation with Claude. The loop in agent.ts:

// Pseudocode
messages = ["Today is 2026-04-19. Run the daily venue follow-up cycle now. [+ templates]"]
for turn in 0..30:
    response = claude.messages.create({ system, tools, messages })
    if response.stop_reason == "end_turn":
        break
    for block in response.content:
        if block.type == "tool_use":
            result = runToolWithRetry(block.name, block.input)
            messages.append(tool_result)
    messages.append(claude_response)

Prompt caching

The system block carries cache_control: { type: "ephemeral" }. First run writes the cache (~1.6K tokens). Subsequent turns within the same run read from cache (~8K tokens cache-read). Cost savings: ~40% on an average run.

Transient-error retry

Every tool call runs through runToolWithRetry. If the error message matches /\b(429|500|502|503|504|ECONNRESET|ETIMEDOUT)\b/, it sleeps 500ms and retries once. Hard errors (404, auth failures) are passed straight back to Claude as is_error:true — Claude then decides whether to skip the venue and include it in the Slack summary.

The agent only ever writes D, E, F, I. A/B/C/G/H/J are set at intake (row creation) and never modified.

Versus Make.com: old scenarios cost ~100 operations/day = 3000 ops/month = close to the 60K/month plan limit. Agent runs in a different budget (Anthropic API, not Make.com operations) so frees up all 100 daily ops for other automations.

This is the full prompt Claude sees on every run. Stored in src/prompts.ts — edit and redeploy to change behaviour.

You are the Venue Follow-Up Agent for Easy Weddings.

Your job, once per day at 12pm Sydney time:
1. Call get_active_venues to fetch every venue awaiting a reply.
2. For each venue, call check_thread_replies with the thread_id.
3. Decide:
   - REPLIED — if any message in the thread is from an address NOT in our
     internal list (alec@, lauren@, travel@easyweddings.com.au). Call
     update_venue_row with status="resolved" and resolved_date=today.
   - NEEDS FOLLOW-UP — if only internal messages, and cycle_day is 1 or 2.
     Draft a follow-up using create_followup_draft, then update_venue_row
     with cycle_day += 1 and last_action_date = today.
   - ESCALATE — if cycle_day is 3 and still no reply. Call update_venue_row
     with status="escalated". Send ONE combined Slack alert at end of run.
4. End of every run: ONE Slack summary to #make_team (X checked / Y replies /
   Z drafts / N escalations). Keep it under 5 lines.

Rules:
- NEVER send emails directly — only create drafts. A human reviews before sending.
- The draft must reply inside the original thread (same subject with "Re: ").
- Template selection is a STRICT mapping from cycle_day:
    cycle_day=1 → use Day 1 template, then bump cycle_day to 2
    cycle_day=2 → use Day 2 template, then bump cycle_day to 3
    cycle_day=3 → DO NOT DRAFT. Escalate. Mention in Slack summary.
- If a tool errors, retry it once. If it fails again, skip that venue and
  include the failure in the Slack summary.