Google Events API for AI Agents

Search Google Events by keyword, location, and an upcoming-date filter. This regular Apify Actor is designed for AI agents, calendar assistants, event-research workflows, and developers that need a bounded JSON response rather than browser automation.

Use it when you need structured upcoming event results such as conferences, concerts, festivals, classes, sports, or local meetups. It returns one normalized dataset row per event with its title, source description, dates, venue, Google Maps link, event page, and available ticket or information links.

This focused discovery surface works for public upcoming Google Events. Ticket purchasing, private calendars, availability confirmation, and historical archives belong in their dedicated organizer, calendar, or ticketing workflows. Results are drawn from Google Events through SerpApi at collection time, so Google controls availability and field completeness.

Why agents use this Actor

• One focused action: find Google Events for a query and location.
• Agent-safe inputs: one query, one location selector, one date-window enum, and a hard result cap.
• Stable, flat fields: eventTitle, startAt, venueName, eventUrl, googleMapsUrl, and ticketLinks.
• Honest terminal state: every run writes OUTPUT and RUN_SUMMARY with COMPLETE, PARTIAL, VALID_EMPTY, INVALID_INPUT, UPSTREAM_FAILED, or CONFIG_ERROR.

Best fit and workflow routing

Choose this Actor for a focused event-discovery step: an agent starts with a subject, a city, and an upcoming date window, then receives source-linked event records it can compare, shortlist, schedule, or pass to a calendar or research workflow. Pair it with your calendar, CRM, or venue-enrichment step after the event shortlist is ready; this Actor is designed as a focused standalone workflow for collecting the Google Events discovery layer.

Workflow story: from query to shortlist

An event-research assistant starts with “AI conferences in New York next month.” It sends that scope as eventQuery, locationName, and dateRange, then reads the default dataset after collection completes. Next, it compares startAt, venueName, and ticketLinks, confirms the selected organizers on their source pages, and exports the resulting shortlist to the user’s itinerary or outreach plan.

Focused standalone workflow

This Actor is designed as a focused standalone workflow when an agent needs the Google Events discovery layer before calendar, CRM, venue, or organizer-specific steps.

Input

{
  "eventQuery": "AI conferences",
  "locationName": "New York,New York,United States",
  "dateRange": "next_month",
  "languageCode": "en",
  "maxResults": 10,
  "countryCode": "us"
}

Set locationName to a city-level value such as London, England, United Kingdom, and use countryCode to set Google’s two-letter country context such as gb. The health-safe default is New York, New York, United States.

Output

Each dataset item has a compact, agent-readable shape:

{
  "eventTitle": "AI Summit New York",
  "startAt": "2026-09-12T09:00:00",
  "endAt": "2026-09-12T17:00:00",
  "displayedDates": "Fri, Sep 12, 9 AM – 5 PM",
  "venueName": "Javits Center",
  "venueAddress": "429 11th Ave, New York, NY",
  "eventUrl": "https://example.com/event",
  "googleMapsUrl": "https://www.google.com/maps/place/...",
  "ticketLinks": [{ "title": "Ticket source", "label": "TICKETS", "url": "https://example.com/tickets", "domain": "example.com" }],
  "searchQuery": "AI conferences",
  "location": "New York,New York,United States",
  "dateRange": "next_month",
  "provider": "serpapi_google_events",
  "source": "Google Events via SerpApi"
}

Nullable fields are deliberate: an absent description, end time, image, venue, or ticket source is returned as null or an empty ticketLinks array rather than invented.

Field	How an agent uses it
eventTitle, startAt, endAt	Compare the event identity and timing.
venueName, venueAddress, googleMapsUrl	Route the user to the location and travel context.
eventUrl, ticketLinks	Confirm details with an organizer or ticket source.
source, collectedAt, providerCostUsd	Preserve provenance, freshness, and request-cost context.

Pricing

This Actor uses Pay per event plus platform usage. The event prices are predictable before an agent calls it:

Event	Price
Actor start	$0.00005
Completed Google Events search	$0.10
Persisted event row	$0.005

A ten-event response therefore has event charges of $0.15005, plus Apify platform usage. A valid empty response still has one completed-search charge because the provider search was completed; malformed input and missing credentials produce no event rows. The live Pricing tab is the current source of truth for event prices and Pay per event plus platform usage configuration. RUN_SUMMARY preserves the provider search ID, output counts, and terminal outcome for auditability.

API and MCP use

Run the Actor through the Apify API, then read the default dataset and terminal records. Replace the actor ID with the one shown in your Apify Console after deployment.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/google-events-api').call({
  eventQuery: 'startup events',
  locationName: 'Austin,Texas,United States',
  dateRange: 'weekend',
  maxResults: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Agent prompt: “Find up to 10 startup events in Austin this weekend. Use the Google Events API Actor with dateRange: \"weekend\"; return the title, start time, venue, and the first ticket link when present. Read the resulting dataset and OUTPUT record, preserve source and collectedAt, and treat VALID_EMPTY as a completed search with no matching Google Events rows.”

Best results, freshness, and workflow guidance

The Actor calls SerpApi’s regular Google search surface and reads its Google Events result block for the selected query, location, language, and country. dateRange adds a natural-language date hint such as “this weekend” to the source query. Google and the provider can vary or omit events, descriptions, times, source pages, ticket links, and venue details; this Actor preserves that uncertainty instead of filling gaps.

Use a specific subject plus a city-level location for the strongest match between user intent and the Google Events source. Confirm event details, access, pricing, availability, and cancellation policies with the organizer before taking downstream action. RUN_SUMMARY provides result counts, warnings, and terminal diagnostics; VALID_EMPTY represents a completed search whose query and targeting had no matching rows.

Builder's note

I designed this Actor around SerpApi’s regular Google result surface, which currently exposes the event-result block, instead of a browser scraper because agents need a bounded, source-labeled response with transparent request cost. My goal is to preserve the useful event, venue, maps, and ticket-source fields while making missing upstream fields explicit, so a downstream agent can make a grounded decision.

Legal and responsible use

Use this Actor only for lawful purposes and in line with the applicable terms, privacy rules, and provider account agreement. Verify event details, accessibility, pricing, availability, and cancellation policies with the event organizer before acting on them.