Eventbrite Lead Automation

About

A three-stage n8n automation stack built for outbound lead generation from Eventbrite events. Stage one runs on a schedule: read target cities from Google Sheets, filter rows not yet processed, loop each city, build a search URL, call an Apify actor to scrape events, append results to an Event_scrap sheet, count events, update the source row status, and wait between iterations to respect rate limits. Stage two reads unscored events from the sheet, filters to unscored rows only, and loops each event through a Claude Haiku 4.5 qualification node with a structured Qualification Schema output parser, then writes scores and qualification results back to the sheet. Stage three splits into two pipelines shown in the workflow canvas: an enrichment chain that every four hours reads unprocessed leads, extracts Eventbrite event IDs, calls Claude with web search to find organizer contact details, parses the response, verifies emails through MillionVerifier when found, and updates the sheet with enriched data; and an outreach chain that every twelve hours reads contacts, filters valid unsent emails, removes duplicates, caps sends at 35 per day, loops with wait delays, sends via Gmail, and marks each row as sent in Google Sheets. The full system runs without manual handoffs. Sheets act as the pipeline state layer between scrape, qualify, enrich, verify, and send.

Key features

• Apify Eventbrite scraping pipeline

  Scheduled workflow reads cities from Google Sheets, loops each location, builds search URLs, runs an Apify actor, appends scraped events to Event_scrap, counts results, and marks source rows done with wait delays between runs.

• Claude AI event qualification

  Second workflow reads unscored events, filters pending rows, and qualifies each event through Claude Haiku 4.5 with a structured Qualification Schema — scores and results write back to the sheet per loop.

• AI lead enrichment & email verify

  Enrichment pipeline runs every four hours: extract Eventbrite IDs, call Claude with web search for organizer contacts, parse responses, verify found emails via MillionVerifier, and update the lead sheet with health status.

• Gmail outreach with send caps

  Outreach pipeline runs every twelve hours: filter valid unsent contacts, dedupe, limit to 35 emails per day, wait between sends, dispatch through Gmail, and mark each row as successfully sent in Google Sheets.

• Google Sheets as pipeline state

  Sheets track city scrape status, raw events, qualification scores, enriched contact fields, email verification results, and sent flags — connecting all three workflows without a separate database.

• Multi-service orchestration in n8n

  Single canvas coordinates Apify, Anthropic Claude, MillionVerifier, Gmail, and Google Sheets with filters, loops, IF branches, code nodes, and scheduled triggers.

Tech stack

• n8n
• Apify
• Claude AI
• Google Sheets
• Gmail
• MillionVerifier
• JavaScript
• Automation