Plan Luma events by city with Apify and Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Sheets. It also calls api.apify.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Review settings (Edit Fields (Set)): sets 7 fields: citySlug, eventFormat, pricing…
- Validate settings (Code): runs custom JavaScript code
- Run Luma events once (HTTP Request): calls api.apify.com (POST)
- Check run status (Code): runs custom JavaScript code
- Run finished? (If): checks a condition and branches into true / false
- Read authoritative output (HTTP Request): calls an HTTP API
- Wait: waits 5 seconds
- Check output bounds (Code): runs custom JavaScript code
- Read existing run (HTTP Request): calls an HTTP API
- Read dataset metadata (HTTP Request): calls an HTTP API
…plus 5 more steps. See the full node list below.
Services it uses
HTTP calls to: api.apify.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Wait
n8n-nodes-base.wait - Google Sheets
n8n-nodes-base.googleSheets
From the author
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.…