🎭 Google Events Scraper | API for Claude, ChatGPT & Cursor (MCP)

Scrape Google Events with one API call, concerts, conferences, festivals, sports, theater, and virtual events. Built as a drop-in Google Events API for Claude, ChatGPT, Cursor, and other MCP-ready AI agents, and as a standard pay-per-page scraper for developers.

Pass any Google Events search query and get structured JSON back: event titles, dates, venues, addresses, ticket links (Ticketmaster, Eventbrite, Spotify, and more), venue ratings, map links, and Google's own filter chips. Localize by country and language. Filter by date (today / this week / weekend / month) and event type (virtual). Pay per page, no subscriptions.

---

🤖 Use with Claude, ChatGPT, Cursor & other AI agents (MCP)

This Actor is a first-class tool on the Apify MCP Server. Any MCP-compatible AI agent, Claude (Desktop, Web, Code), ChatGPT (via custom GPT or MCP bridge), Cursor, VS Code, Cline, Windsurf, Kilo Code, Opencode, Glama, can discover and call this Actor in natural language.

What an AI agent does with this:

User: "Find me family-friendly events in Brooklyn this weekend, with ticket links."

Agent → calls search-actors("google events") on the Apify MCP server → picks this Actor → calls it with {"q": "family events brooklyn", "location": "Brooklyn, NY", "advanced": "date:weekend", "max_pages": 2} → returns structured event JSON → summarizes for the user.

Quick setup: Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": ["-y", "@apify/actors-mcp-server"],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_API_TOKEN"
      }
    }
  }
}

Restart Claude Desktop. Then ask Claude something like "Search Google Events for tech meetups in San Francisco next week.", Claude will discover this Actor, ask permission to call it, and return structured results.

Quick setup: Cursor / VS Code / Cline / Windsurf

These editors support dynamic tool discovery, which means after the first call this Actor is registered as a named tool for the rest of the session, subsequent prompts skip the discovery step entirely.

Point your MCP client at:

https://mcp.apify.com

…with header Authorization: Bearer YOUR_APIFY_API_TOKEN. Full setup instructions: Apify MCP integration docs.

Quick setup: ChatGPT (and other static MCP clients)

ChatGPT, Claude Desktop (without dynamic discovery), Gemini CLI, and Amazon Q connect through the same https://mcp.apify.com endpoint and call this Actor via the generic call-actor tool, same result, just no session-level tool registration.

Use cases for AI agents

• 🤖 Event-discovery assistants: "Find me what's happening this weekend near {city}."
• 📅 Calendar copilots: Auto-suggest events that match the user's interests and free slots.
• 🎟️ Ticket-finding agents: "Cheapest tickets for {artist} in {city} this month."
• 🏢 Sales / lead-gen agents: Surface industry conferences and trade shows where prospects gather.
• 📊 Research agents: Aggregate event data across cities for market analysis or trend reports.

---

💡 What this Actor does

A Google Events Scraper that takes a search query and pulls structured event data straight from Google Events, titles, dates, venues, ticket links, addresses, descriptions, venue ratings, map links, and Google's own filter chips, and returns it as clean JSON.

Whether you're powering an AI agent through MCP, building an event-discovery app, monitoring competitor events, or aggregating concert and conference data into a dataset, this scraper handles the platform-side complexity so you don't have to.

✅ SEO benefit: Structured Google Events data lets businesses optimize event listing pages, monitor competition, and create data-rich content that boosts organic visibility.

---

📦 What data you get

Field	Description
🎭 Event details	Title, description, dates, times, and primary link
📅 Date & time	Start dates, full date/time ranges, "when" labels
📍 Location	Multi-line address, venue, map preview image + link
🎫 Ticket links	Sources (Ticketmaster, Eventbrite, Spotify, etc.) with URLs and link types
🏛️ Venue details	Name, rating, review count, link to venue's Google listing
🗺️ Map preview	Static map image URL + clickable Google Maps link
🎯 Hit chips	Filter chips offered by Google Events (date ranges, event types)
🔍 Filters	Additional filter groups for narrowing the search
📊 Search metadata	Total results, pages processed, pagination status

---

⚙️ Key features

✨ Comprehensive data coverage: Every event field Google Events returns: titles, descriptions, dates, locations, tickets, venues.

🔍 Advanced filtering: Filter by date (today, tomorrow, this week, weekend, this month, next month) and event type (virtual). Combine multiple filters in one call.

🌍 Localization: Country (gl) and language (hl) parameters localize results to any of 240+ countries and 200+ languages.

📄 Smart pagination: Set max_pages to fetch as many pages as you need, or 0 for unlimited. Pages are billed individually, you pay for what you actually fetch.

🎯 Hit-chips support: Use Google's native filter chips (date:today, event_type:Virtual-Event, etc.) to slice results the same way Google's UI does.

💰 Transparent pay-per-page pricing: $0.02 setup + $0.02 per page. No subscriptions, no minimums.

🛡️ Production-grade reliability: 99.9% success rate on live traffic, comprehensive error handling, schema-validated output.

🤖 MCP-ready: First-class tool on the Apify MCP Server for Claude, ChatGPT, Cursor, and any other MCP-compatible agent.

---

🚀 Getting Started

Pulling your first batch of Google Events data takes about a minute:

1. Click Try for free at the top of this page (or open the Actor in the Apify Console).
2. Enter a search query in q, for example concerts in New York or tech conferences this week. That is the only required field.
3. Optionally set location, gl, hl, the advanced filters, and max_pages, then click Start.
4. Read the results in the Output tab, or export them as JSON, CSV, or Excel.

Prefer code or an AI agent? Call the Actor through the Apify API with the apify-client package, or add it as a tool to Claude, ChatGPT, or Cursor through the Apify MCP server. Both paths are covered in the sections below.

---

📖 Usage examples

Example 1: Basic search (events in New York)

{
  "q": "events in New York",
  "max_pages": 1
}

Example 2: Search with location and localization

{
  "q": "concerts",
  "location": "Austin, Texas, United States",
  "gl": "us",
  "hl": "en",
  "max_pages": 1
}

Example 3: Today's events (single hit chip)

{
  "q": "sports events",
  "location": "Los Angeles, CA",
  "advanced": "date:today",
  "max_pages": 1
}

Example 3b: Today's virtual events (multiple hit chips, comma-separated)

{
  "q": "concerts",
  "advanced": "event_type:Virtual-Event,date:today",
  "max_pages": 1
}

Example 3c: Multiple hit chips as an array

{
  "q": "conferences",
  "advanced": ["date:today", "event_type:Virtual-Event"],
  "max_pages": 1
}

Example 4: Pagination (multiple pages)

{
  "q": "music festivals",
  "location": "California, United States",
  "gl": "us",
  "hl": "en",
  "max_pages": 2
}

Example 5: Comprehensive search (every parameter)

{
  "q": "theater shows",
  "location": "New York, NY",
  "gl": "us",
  "hl": "en",
  "advanced": ["date:month", "event_type:Virtual-Event"],
  "max_pages": 2
}

---

🔍 Input parameters

Parameter	Type	Required	Default	Description
q	string	✅ Yes	None	Search query (e.g., "concerts in New York", "tech conferences this week").
location	string	❌	None	Geographic location to bias results toward (e.g., "Austin, Texas, United States").
gl	string	❌	None	Country code (ISO 3166-1 alpha-2, lowercase). See country table below.
hl	string	❌	None	Language code (ISO 639-1, lowercase). See language table below.
advanced	string or array	❌	None	Hit-chip filters (string, comma-separated string, or array). See hit-chips section below.
max_pages	integer	❌	1	Pages to fetch. 0 = unlimited. Each page billed separately.
output_file	string	❌	auto-generated	Optional JSON filename for local runs (ignored when run on the Apify platform).

---

🌍 Country codes (gl parameter)

The gl parameter accepts ISO 3166-1 alpha-2 country codes (lowercase). Most common:

Code	Country	Code	Country	Code	Country
us	United States	uk / gb	United Kingdom	ca	Canada
au	Australia	de	Germany	fr	France
it	Italy	es	Spain	nl	Netherlands
be	Belgium	at	Austria	ch	Switzerland
se	Sweden	no	Norway	dk	Denmark
fi	Finland	pl	Poland	cz	Czech Republic
ie	Ireland	pt	Portugal	gr	Greece
jp	Japan	kr	South Korea	cn	China
tw	Taiwan	hk	Hong Kong	sg	Singapore
my	Malaysia	th	Thailand	id	Indonesia
ph	Philippines	vn	Vietnam	in	India
nz	New Zealand	za	South Africa	br	Brazil
mx	Mexico	ar	Argentina	cl	Chile
co	Colombia	pe	Peru	ve	Venezuela

240+ country codes are supported. Pick the closest from the dropdown in the input schema.

---

🌐 Language codes (hl parameter)

The hl parameter accepts ISO 639-1 language codes (lowercase). Most common:

Code	Language	Code	Language	Code	Language
en	English	es	Spanish	fr	French
de	German	it	Italian	pt	Portuguese
ru	Russian	ja	Japanese	ko	Korean
zh	Chinese	zh-cn	Chinese (Simplified)	zh-tw	Chinese (Traditional)
ar	Arabic	hi	Hindi	th	Thai
vi	Vietnamese	id	Indonesian	ms	Malay
tl	Filipino	nl	Dutch	pl	Polish
tr	Turkish	cs	Czech	sv	Swedish
da	Danish	fi	Finnish	no	Norwegian
hu	Hungarian	ro	Romanian	bg	Bulgarian

200+ language codes are supported. Pick the closest from the dropdown.

---

🎯 Advanced filters (hit chips)

The advanced parameter accepts Google Events hit-chips, the filter pills you see at the top of the events results UI. Pass a single token, a comma-separated string, or an array.

Date filters

Token	Meaning
date:today	Events happening today
date:tomorrow	Events happening tomorrow
date:week	Events this week
date:weekend	Events this weekend
date:next_week	Events next week
date:month	Events this month
date:next_month	Events next month

⚠️ The token for "this month" is date:month, not date:thismonth. Using the wrong token causes the run to exit gracefully at start (before any charge) with a clear error.

Event-type filter

Token	Meaning
event_type:Virtual-Event	Virtual / online events only

Combining filters

{ "advanced": "event_type:Virtual-Event,date:today" }
{ "advanced": ["date:weekend", "event_type:Virtual-Event"] }

---

📊 Output format

One dataset item is pushed per page of results, so a 3-page run produces 3 dataset items. Each item has the same shape:

{
  "search_parameters": {
    "q": "events in New York",
    "location": null,
    "gl": null,
    "hl": null,
    "advanced": null,
    "max_pages": 1,
    "applied_hit_chips": null
  },
  "search_metadata": {
    "total_results": 10,
    "events_count": 10,
    "hit_chips_count": 0,
    "filters_count": 0,
    "pages_processed": 1,
    "max_pages_set": 1,
    "pagination_limit_reached": true
  },
  "search_timestamp": "2026-05-11T10:30:00.123456",
  "page_number": 1,
  "events": [
    {
      "title": "Funk Tribu",
      "date": {
        "start_date": "Nov 14",
        "when": "Fri, Nov 14, 10 PM – Sat, Nov 15, 1 AM"
      },
      "address": [
        "Avant Gardner, 140 Stewart Ave",
        "Brooklyn, NY"
      ],
      "link": "https://open.spotify.com/concert/5FXK8DRwn1wnBPbdW6r7hb",
      "event_location_map": {
        "image": "https://www.google.com/maps/vt/data=...",
        "link": "https://www.google.com/maps/place/..."
      },
      "description": "Find tickets for Funk Tribu at Park Slope Brooklyn Warehouse in New York City on 11/14/2025 at 10:00 PM",
      "ticket_info": [
        { "source": "Spotify.com", "link": "https://open.spotify.com/concert/...", "link_type": "tickets" },
        { "source": "Ticketmaster.com", "link": "https://ticketmaster.com/...", "link_type": "tickets" }
      ],
      "venue": {
        "name": "Avant Gardner",
        "rating": 4.1,
        "reviews": 4378,
        "link": "https://www.google.com/search?q=Avant+Gardner&..."
      }
    }
  ],
  "hit_chips": [],
  "filters": []
}

Top-level fields

• search_parameters - The exact input that produced this page.
• search_metadata - Counts and pagination status for the run.
• search_timestamp - ISO 8601 timestamp when this page was fetched.
• page_number - 1-indexed page number.
• events - Array of event objects on this page (see below).
• hit_chips - Available filter chips (typically only on page 1).
• filters - Secondary filter groups (typically only on page 1).

Event fields

• title - Event display title.
• date.start_date / date.when, Short date label and full date/time range.
• address - Array of address lines.
• link - Primary event landing link.
• event_location_map - Map preview image URL + Google Maps link.
• description - Free-text event description.
• ticket_info - Array of ticket-provider links with source name and link type.
• venue - Venue name, rating, review count, and Google listing link.

---

💸 Pricing

This Actor uses Apify's pay-per-event model:

Event	Price	When charged
Setup	$0.02	Once per run, at start
Page processed	$0.02	Per page of results successfully fetched and stored

Examples:

• 1 page: $0.02 setup + $0.02 page = $0.04
• 5 pages: $0.02 setup + $0.10 pages = $0.12
• 20 pages: $0.02 setup + $0.40 pages = $0.42

A pre-run funds check makes sure you can afford the maximum possible cost of the run before any work begins. If you don't have enough budget, the Actor exits gracefully with a friendly message before any charge.

---

🎯 Use cases

• 🤖 AI agents (MCP): Plug into Claude, ChatGPT, Cursor and let the agent discover & call this tool natively.
• 📅 Event-discovery apps: Build event-aggregation platforms with up-to-date Google Events data.
• 📊 Market research: Analyze event trends, popularity, and venue saturation across cities.
• 🏢 Competitive analysis: Monitor competitors' event listings, ticket availability, and pricing.
• 🎫 Ticket-comparison tools: Pull multi-source ticket links (Ticketmaster, Eventbrite, Spotify, etc.) for every event.
• 📈 Lead generation: Identify trade shows and conferences where target customers will be.
• ✍️ Content creation: Generate event-round-up articles for local-events SEO content.
• 🌐 Virtual-event discovery: Filter on event_type:Virtual-Event to find online-only events.
• 📡 Google Events tracking: Re-run saved searches on a schedule to track new listings, venue changes, and sold-out status across a city over time.

---

🔌 Integrations: Automate Google Events Tracking

A single search answers one question. The real value of this Google Events API comes from running it repeatedly, watching a city's calendar week over week, catching newly listed concerts and conferences, and feeding live event data into the tools you already use. Thanks to the native Apify platform integrations, you can wire this Actor into your stack in minutes, with no servers or cron jobs of your own.

Tasks + Schedules: register a recurring events run

The core pattern for Google Events tracking is one saved task per search, one schedule across all of them.

1. Create a task. A saved task is this Actor plus a saved input, so give each search you care about its own named task, for example "SF tech conferences" with q: "tech conferences", location: "San Francisco, CA", and advanced: "date:month". Click Create empty task on the Actor page, fill in the input, and save.
2. Attach a schedule. Open Schedules in the Apify Console, create a schedule with a standard cron expression, and add your tasks to it. Useful examples: 0 7 * * * (every morning at 7 AM), 0 */6 * * * (every 6 hours), 0 9 * * 1 (Mondays at 9 AM). One schedule can trigger many tasks, so a single "daily events check" can monitor every city and query you have saved.
3. Review the history. Each run appends new pages of results, each stamped with a search_timestamp, to the task's dataset, giving you an event history you can export as JSON, CSV, or Excel at any time.

See it working end to end in the featured task Find concerts and festivals in Austin this weekend.

n8n: build an event-alert workflow

This Actor also ships as a dedicated n8n community node, n8n-nodes-google-events-api (see the n8n integration section near the end of this README), so you do not need raw HTTP requests. In n8n: Settings, Community Nodes, install n8n-nodes-google-events-api, then use it in any workflow (it also works as an AI Agent tool).

A typical event-alert workflow looks like this:

1. Schedule Trigger: run every morning at 7 AM.
2. Google Events node: search your query, for example concerts in your city.
3. Filter node: keep only events matching your criteria (a date range, a venue, a keyword).
4. Slack or email node: send yourself the title, date, venue, and ticket link when a new event appears.

Make and Zapier

Prefer Make or Zapier? Both have native Apify integrations, Apify on Make and Apify on Zapier, with "Run Actor" and "Get Dataset Items" actions. The same event-alert pattern applies: trigger on a schedule, run this Actor, filter on what matters, then notify or store the results.

Supabase: store an event history in your own database

Tracking events over time means storing them somewhere queryable. Supabase (hosted Postgres) is a good fit, and there are two easy paths:

• No code: in n8n, connect the Google Events node to the built-in Supabase node to insert a row per event after each scheduled run.
• A few lines of Python: run the Actor and bulk-insert the flat event rows into an events table.

from apify_client import ApifyClient
from supabase import create_client

apify = ApifyClient("YOUR_APIFY_TOKEN")
supabase = create_client("https://YOUR_PROJECT.supabase.co", "YOUR_SERVICE_ROLE_KEY")

run = apify.actor("johnvc/google-events-api---access-google-events-data").call(
    run_input={
        "q": "concerts",
        "location": "Austin, Texas, United States",
        "gl": "us",
        "hl": "en",
        "max_pages": 2,
    }
)

for page in apify.dataset(run["defaultDatasetId"]).iterate_items():
    rows = [
        {
            "title": event["title"],
            "event_when": event.get("date", {}).get("when"),
            "address": ", ".join(event.get("address", [])),
            "venue": event.get("venue", {}).get("name"),
            "link": event.get("link"),
            "searched_at": page["search_timestamp"],
        }
        for event in page.get("events", [])
    ]
    if rows:
        supabase.table("events").insert(rows).execute()

Run this on a schedule (or trigger it from a webhook, below) and you have a growing event database ready for dashboards, a city-events app, or trend analysis.

MCP and AI agents

Apify exposes this Actor through the Apify MCP server, so MCP-compatible AI assistants, Claude, Cursor, and others, can run live Google Events searches as a tool and answer questions like "what family-friendly events are on in Brooklyn this weekend?" with real data. That is what turns this into a Google Events AI agent rather than a one-off script. If you drive it from Claude Code (free trial), the same MCP endpoint applies. See the Use with Claude, ChatGPT, Cursor & other AI agents (MCP) section near the top for one-click client setup.

Webhooks: connect anything else

For custom setups, attach an Apify webhook to the ACTOR.RUN.SUCCEEDED event. Every time a scheduled run finishes, Apify POSTs the run details (including the dataset ID) to your endpoint, your server, an n8n or Make webhook trigger, or a serverless function, which can then fetch the results and do anything with them: update a Google Sheet, refresh a dashboard, or post the night's events to a channel.

---

🔗 Related Tools

Building an event-discovery or event-and-travel workflow? These related tools from the same collection pair well with this Google Events API:

• Google Maps Places API: enrich the venues that show up in your event data with full business details, ratings, phone numbers, and opening hours.
• Google Flights API: find and track flight prices for the cities where events are happening, so an "attend this conference" plan includes getting there.
• Google Hotels Search Scraper: pull hotel availability and pricing near an event venue to round out an event-and-travel dataset.

Newer alternatives such as the Google Events Scraper by scrapier exist, but at the time of writing it has only a couple of users, no rating, an empty Store description, and a duplicated pay-per-result pricing setup. This Actor is actively maintained, rated 5 stars, documents every output field, and validates its JSON against a schema on every run.

---

❓ FAQ

How do I get started?

Provide a q (search query). That is the only required parameter. Run the Actor and it returns structured JSON.

Is q required?

Yes. Everything else is optional.

Can I filter results by date?

Yes, use advanced with date:today, date:week, date:weekend, date:month, date:next_week, date:next_month, etc. See the hit-chips section above.

How do I search for virtual events only?

Pass "advanced": "event_type:Virtual-Event". Combine with a date filter for today's virtual events: "event_type:Virtual-Event,date:today".

Can I use multiple filters at once?

Yes, as a comma-separated string ("date:today,event_type:Virtual-Event") or as an array (["date:today", "event_type:Virtual-Event"]).

How does pagination work?

Set max_pages to the number of pages you want. 0 means unlimited (fetch all available pages). Each page is billed separately.

Can I search in different countries and languages?

Yes, gl (country code) and hl (language code). 240+ countries and 200+ languages are supported.

What format does the scraper return?

Structured JSON. Each page of results is pushed as a separate dataset item. Results can be exported as JSON, CSV, Excel, or accessed via Apify's API.

Does this work with AI agents through MCP?

Yes, see the Use with Claude, ChatGPT, Cursor & other AI agents (MCP) section near the top. MCP-compatible clients can discover and call this Actor natively.

How do I use the location parameter?

Pass a human-readable location string: "Austin, Texas, United States", "London, England, United Kingdom", "New York, NY".

What if my search returns no results?

search_metadata.events_count is 0 and events is an empty array. The Actor still completes successfully, you are only charged the setup fee in that case.

Can I schedule this Google Events Scraper?

Yes, and this is where the Actor earns its keep. Any run can be automated on a schedule. Create a saved task with your query and filters, then attach a schedule from the Actor's Actions, then Schedule menu. Useful cron expressions: 0 7 * * * (daily at 7 AM), 0 */6 * * * (every six hours), 0 9 * * 1 (Mondays at 9 AM). One schedule can trigger many tasks at once, so a single "daily events check" can watch every city and query you have saved. See the Integrations section above for the full monitoring recipe.

Should I use an API or a web scraper for Google Events?

There is no official public Google Events API, so your options are an unofficial API endpoint or a web scraper. This Actor is both in one: call it like a clean API you run yourself, or use it as a no-code web scraper from the Apify Console, with no quotas or API keys to manage. Either way it reads the public event listings that appear in Google Search and returns the same structured event data.

Can I integrate this Google Events Scraper with other apps?

Yes. The Actor connects to almost any cloud service through Apify integrations: Make, Zapier, Slack, Google Drive, and more. For anything custom, attach a webhook on the ACTOR.RUN.SUCCEEDED event. See the Integrations section above for ready-to-use recipes.

Can I use Google Events data with the API?

Yes. The Apify API gives you programmatic access to run the Actor, schedule it, and fetch datasets, and the apify-client package is available for both Node.js and Python. Grab your endpoints from the Actor's API tab.

Can I use this Google Events API through an MCP server?

Yes. The Actor can be added as a tool to any MCP client (Claude, Cursor, and others) through the hosted Apify MCP server. Point your client at https://mcp.apify.com/?tools=actors,docs,johnvc/google-events-api---access-google-events-data. If you are driving it from Claude Code (free trial), the same endpoint applies. Full setup: Apify MCP docs.

How can I track other Google and events data sources?

Pair this Actor with complementary tools from the same collection. Use the Google Maps Places API to enrich event venues, the Google Flights API to track travel to those events, and the Google Hotels Search Scraper for nearby lodging. See the Related Tools section above for how they fit together.

What can an AI agent do with this Google Events API?

An AI agent that supports MCP can discover this Actor, call it with a natural-language request like "family-friendly events in Brooklyn this weekend", and get back structured JSON it can summarize, filter, or store. That is what makes it a practical building block for a Google Events AI assistant, a calendar copilot, or an event-discovery bot.

Can I use this for market research?

Yes. Aggregating events across cities and dates is a common market research use: track how many concerts, conferences, or festivals appear in a metro over time, which venues host the most, and how ticket sources compare. Run it on a schedule and store each run to build the history.

Is it legal to scrape Google Events?

Scraping publicly available data is generally permitted, though you are responsible for how you use the data you collect. Apify has a plain-English overview of the legality of web scraping. This Actor only reads public Google Events results.

How much does it cost?

Pricing is pay-per-page: a small setup fee per run plus a small fee per page of results fetched. See the Pricing section above for exact figures and worked examples. There are no subscriptions or minimums.

---

📝 Technical notes

• Results are sorted by Google Events' default relevance ordering.
• The q parameter is required and must be non-empty.
• Invalid hit-chip tokens are caught at run start, before any charges are applied, the Actor exits gracefully with a clear error message.
• Each page is pushed as its own dataset item, so per-page billing matches actual deliverables exactly.
• All output is JSON-serialized and schema-validated before being pushed.
• Pagination stops automatically once Google Events has no more results, even if max_pages is higher.
• location, gl, and hl are optional but recommended for sharper localization.
• Ticket info includes links from multiple sources (Ticketmaster, Eventbrite, Spotify, AXS, SeatGeek, and more) when available.
• Venue rating and review counts are included when Google has them for that venue.

---

🚀 Ready to scrape Google Events?

Whether you're wiring this up as an MCP tool for Claude, ChatGPT, or Cursor, or pulling event data directly through Apify's API, you'll have clean, structured Google Events results in minutes. Click Try for free to run your first search.

Python + MCP example: Apify-Google-Events-API on GitHub

Made with ❤️

---

n8n integration

Available as an n8n community node, n8n-nodes-google-events-api. In n8n: Settings, Community Nodes, install n8n-nodes-google-events-api, then use it in any workflow (it also works as an AI Agent tool).

---

Featured Tasks

Ready-to-run examples that show this API solving a specific problem. Each opens its own setup so you can run it on your account in one click.

• Find concerts and festivals in Austin this weekend - weekend-filtered live events with dates, venues, and ticket links.
• Track tech conferences in San Francisco - upcoming conferences with venues and registration links for event marketers.
• Aggregate local sports events for a city app - one run returns a city's games with dates, venues, and ticket links as JSON.

---

📚 Guides and Tutorials

In-depth walkthroughs for this API, published on Medium.

Google Events API for AI Agents: Live Concerts, Conferences and Tickets via MCP

A walkthrough of using the Google Events API with AI agents over MCP, centered on the search "google events api" and live concert, conference, and ticket data. It covers what the API returns and how to wire it into an assistant like Claude or ChatGPT. Published July 2026.

---

Last Updated: 2026.07.11