Plan Luma events by city with Apify and Google Sheets

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

• The template is free; Apify usage is paid. The default $1 cap is a maximum, not a quoted price. Repeated results can incur charges again. Only Sheet delivery retries automatically.

Customization

• Start with sf, then use another supported Luma city slug. Choose all, in_person or online events and all, free or paid pricing. Up to 100 events are supported. Keep settings stable and run sequentially to update the same scope. Setup details.

Additional info