Track Google Events for a City on a Schedule
John
Re-run a saved Google Events search on a schedule to track new listings. Each run returns event title, date, venue, address, and ticket links with a timestamp.
Input
Output fields
Sign up on Apify or log in
The Google Events | Scrape Google Events for AI Agents Actor is ready to run with the inputs already set for "Track Google Events for a City on a Schedule". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Track Google Events for a City on a Schedule" task
The Google Events | Scrape Google Events for AI Agents Actor will start running based on the input automatically. You can also change all the input fields, like search query and location, to match your specific use case.
Receive the "Track Google Events for a City on a Schedule" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as search timestamp, mode, search query, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Track Google Events for a City on a Schedule" task via API.

Integrate "Track Google Events for a City on a Schedule" into your workflow
Connect "Track Google Events for a City on a Schedule" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay
One item per run with search_timestamp, search_parameters.q, search_parameters.location, search_metadata.events_count and an events list carrying title, when, venue_name and link for Chicago. Compare runs by timestamp, or export JSON, CSV or Excel.
Only q, set to events in Chicago, and location, set to Chicago, Illinois. Change the city text to track another market, and add advanced with date:week or date:next_week when the schedule should only watch the coming days.
Trigger the task's run endpoint on the Apify API, or call it through apify-client for Python or Node, and read the Chicago dataset back as JSON or CSV. Pair that with your own cron if you would rather not use the Console scheduler.
In the Apify Console open Track Google Events for a City on a Schedule, choose Actions, then Schedule, and enter 0 7 * * * for a daily 7 AM run. Each run writes a fresh Chicago dataset, and the Slack integration or a webhook can push new listings on.
Connect Claude or any other MCP client to https://mcp.apify.com/?tools=actors,docs,johnvc/google-events-api---access-google-events-data with your Apify API token, and the agent can start the Chicago search and read the events back in one chat.
The Google Events API lists no free tier. Each run bills a setup fee plus a fee per Chicago event returned, at most ten, so a daily schedule pays one setup fee and up to ten event fees a day. Rates are on the Actor page.
Track Google Events for a City on a Schedule runs unattended on a cron and stacks timestamped Chicago datasets for comparison. Give an AI Agent Live Google Events Data via MCP waits for an agent to ask and answers once, with no schedule.