πŸ”¬ Plan Luma events by city with Apify and Google Sheets

⚑ 1 views Β· πŸ”¬ Document Extraction & Analysis

πŸ’‘ Pro Tip β€” HTTP Request scraping tends to break when sites update their markup. If you’re scraping a major platform, check if ScraperNode covers it β€” it has maintained scrapers for LinkedIn, Instagram, TikTok, YouTube, and 20+ other platforms that return structured data.

View All Scrapers

Description

Quick overview

Give a community organizer an event-planning register for one city. Bring public Luma dates, timezones, venue information and registration requirements into Google Sheets without copying attendee profiles or sending invitations.

How it works

  1. One bounded Apify run supplies source records, coverage and billing evidence.
  2. The workflow checks the complete dataset before Google Sheets delivery.
  3. Stable source keys update existing rows on repeat. Unobserved earlier rows remain, so the Sheet is a current review register, not a complete history.
  4. COMPLETE describes the declared source window; CAPPED remains a labelled sample.
  5. Source failures stop delivery. Verified empty results create no data rows.
  6. Keep UTC timestamps and the source timezone together. The review action highlights applications, sold-out events and dates that have already started. Empty price or availability fields remain unknown. Review the event page before making plans; the workflow does not register guests or book tickets.

Setup

  1. Import the workflow into an empty n8n canvas. Use your own Apify account and a Header Auth credential on all five HTTP nodes.
  2. Connect Google Sheets OAuth2 on Upsert review register. Create the supplied tab and import the exact CSV header.
  3. Enter its spreadsheet ID in Review settings and run manually.

Requirements

Customization

Additional info

Workflow canvas

πŸ”— Nodes Used

Google Sheets, HTTP Request

πŸ“₯ Import

Download workflow.json and import into n8n: Workflow menu β†’ Import from File

πŸ“– Importing guide Β· πŸ”‘ Credential setup