# Google Events Scraper — Event Listings as JSON (`muhammadafzal/google-events`) Actor

Find public Google Events listings by query and location with dates, venues, ticket links, and source URLs. $0.005 per event returned.

- **URL**: https://apify.com/muhammadafzal/google-events.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (community)
- **Categories:** AI, MCP servers, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 google event records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Google Events Scraper — Event Listings as JSON

Find public event listings from Google Events by topic, location, and date window. The actor returns one normalized dataset item per event with the title, displayed date, machine-readable dates when available, venue, address, organizer, description, image, ticket link, and the Google search URL used for provenance.

This is designed for event-discovery products, calendar assistants, local guides, venue research, travel planning, newsletter automation, and AI agents that need a short list of live events in a named location.

### What it extracts

| Field | Description |
| --- | --- |
| `title` | Public event name |
| `startDate`, `endDate` | ISO 8601 timestamps when the source exposes them; otherwise `null` |
| `dateText` | Human-readable date/time copied from the result card |
| `venue`, `address` | Public venue and locality/address when shown |
| `organizer` | Organizer or promoter when available |
| `description` | Short result context in detailed mode |
| `imageUrl` | Public event image when available |
| `ticketUrl` | External ticket, registration, or event-detail link when found |
| `sourceUrl` | Google Events search URL for provenance |
| `eventId` | Stable hash used to deduplicate results across queries |

Optional fields are always present with `null` when Google does not expose the value. The parser accepts both machine-readable Event JSON-LD and visible Google-style event cards, because Google can expose different fields across query types, locales, and result layouts.

### When to use it

Use this actor when you need public event discovery from Google’s event-results surface:

- Find concerts, festivals, conferences, workshops, sports, comedy, theater, or family events in a city.
- Seed a local-events newsletter or a calendar-review workflow.
- Let an AI agent answer “what is happening this weekend in London?” with structured source links.
- Refresh an event shortlist on a schedule using a small `maxResults` cap.

Do not use it for private Google Calendar data, event-management dashboards, attendee lists, ticket inventory, price guarantees, venue availability, or a complete citywide event database. It reads public search results only; it does not sign in, buy tickets, or bypass CAPTCHA/access controls.

### Input

The default input searches for concerts in New York, NY and stores up to 25 unique event records:

```json
{
  "searchQueries": ["concerts"],
  "location": "New York, NY",
  "dateFilter": "this_weekend",
  "maxResults": 25,
  "responseFormat": "detailed"
}
```

`searchQueries` accepts up to five topics. `location` should be a human-readable city, region, or country, such as `Austin, TX`, `Toronto, Canada`, or `Paris, France`. `dateFilter` is a Google search hint: `any`, `today`, `tomorrow`, `this_weekend`, `this_week`, `next_week`, or `this_month`. It does not replace source-level date validation; inspect `startDate` and `dateText` before making time-sensitive decisions.

`responseFormat` can be `concise` or `detailed`. Concise mode keeps the stable discovery fields but omits descriptions to reduce AI-agent output tokens. Detailed mode retains the short public description and any image URL found in the result. `maxResults` is a total cap across all supplied queries, not a cap per query. Duplicate events are emitted once.

### Output example

```json
{
  "eventId": "evt_7a6f8b",
  "title": "Summer Jazz Festival",
  "startDate": null,
  "endDate": null,
  "dateText": "Sat, Aug 15 · 7–10 PM",
  "venue": "Central Park SummerStage",
  "address": "New York, NY",
  "organizer": null,
  "description": "Outdoor live music with local and touring artists.",
  "imageUrl": null,
  "ticketUrl": "https://tickets.example.com/festival",
  "sourceUrl": "https://www.google.com/search?q=concerts+events+in+New+York%2C+NY",
  "query": "concerts",
  "locationQuery": "New York, NY",
  "dateFilter": "this_weekend",
  "scrapedAt": "2026-08-02T12:00:00.000Z",
  "warnings": []
}
```

The run summary is also saved to the key-value store under `OUTPUT`. It includes the number of records, requested and failed source pages, charge totals, and non-fatal warnings such as an empty result page or Google access-control response.

### Pricing

The primary PPE event is **$0.005 per normalized event record stored**, plus Apify’s actor-start event. With `maxResults: 25`, the maximum event-record charge is $0.125 before normal Apify compute, browser, proxy, or platform usage charges. The actor is designed to be used with both PPE and Apify Pay-Per-Usage; the latter is configured at the actor level in Apify Console rather than in the code manifest.

No event charge is created for an invalid parser candidate, duplicate record, empty result page, failed request, or access-control page. A result is charged only after it passes runtime validation and is stored in the default dataset.

### Reliability and limits

Google’s public result markup is dynamic and can vary by location, language, query, and time. The actor uses Apify’s US residential proxy pool, a single Playwright session at low concurrency, waits for the rendered page, blocks nonessential image/font/media requests, and retries failed pages. It detects common CAPTCHA/unusual-traffic pages and returns a terminal warning instead of silently claiming that no events exist.

For repeat use, keep queries focused, use a modest `maxResults`, and respect the default request delay. A proxy does not guarantee access and should not be treated as a method to evade access controls.

Machine-readable `startDate` and `endDate` values are only returned when exposed by the source. For many visible event cards, `dateText` is the strongest available date signal. Always verify the ticket or organizer page before purchasing, publishing a schedule, or making a safety, travel, or financial decision.

### API and MCP use

Through Apify’s standard actor API, pass the JSON input shown above and read the default dataset after the run completes. The schema is intentionally narrow for hosted MCP discovery: an agent should choose this actor for public event listings, not for calendars or ticketing operations. The tool surface returns one flat event record per item and gives the agent a source URL and cost cap it can reason about.

JavaScript example:

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('YOUR_USERNAME/google-events').call({
  searchQueries: ['technology conferences'],
  location: 'Berlin, Germany',
  dateFilter: 'next_week',
  maxResults: 20,
  responseFormat: 'concise'
});
console.log(run.defaultDatasetId);
```

Python example:

```python
from apify_client import ApifyClient

client = ApifyClient(token="YOUR_APIFY_TOKEN")
run = client.actor("YOUR_USERNAME/google-events").call(run_input={
    "searchQueries": ["technology conferences"],
    "location": "Berlin, Germany",
    "dateFilter": "next_week",
    "maxResults": 20,
    "responseFormat": "concise",
})
print(run["defaultDatasetId"])
```

### Legal and responsible use

This actor accesses public search-result pages. You are responsible for complying with Google’s terms, applicable law, source-site terms, rate limits, privacy requirements, and the rules governing any downstream event outreach or publication. This independent actor is not affiliated with or endorsed by Google. Treat event dates, ticket links, prices, availability, and organizer claims as source data that require verification.

# Actor input Schema

## `searchQueries` (type: `array`):

Use this when you want event listings matching one or more topics, such as 'live jazz' or 'technology conference'. Enter one query per line; defaults to 'concerts'. This is not a Google Maps place search or a URL list.

## `location` (type: `string`):

Use this to localize event results to a city, region, or country, for example 'New York, NY' or 'London, UK'. Defaults to New York, NY. This is not a venue URL or a latitude/longitude pair.

## `dateFilter` (type: `string`):

Use this to bias Google Events toward a time window such as today, this weekend, or next week. Choose any for the broad upcoming-events view. This is a search hint, not a guaranteed date constraint on every result.

## `maxResults` (type: `integer`):

Use this to cap the total number of unique event records stored across all queries. Enter 1–100; defaults to 25. The cap also limits the $0.005-per-event PPE charge. This is not a page-count setting.

## `responseFormat` (type: `string`):

Use concise for smaller AI-agent records or detailed for descriptions, images, and richer source context. Choose concise or detailed; detailed is the default. This changes output richness, not the number of events or source searches.

## `requestDelayMs` (type: `integer`):

Use this to pace multiple Google result-page requests. Enter 1000–10000 milliseconds; defaults to 2000. This is not a page timeout and does not bypass Google's access controls.

## Actor input object example

```json
{
  "searchQueries": [
    "concerts"
  ],
  "location": "New York, NY",
  "dateFilter": "this_weekend",
  "maxResults": 25,
  "responseFormat": "detailed",
  "requestDelayMs": 2000
}
```

# Actor output Schema

## `events` (type: `string`):

One normalized event listing per dataset item.

## `summary` (type: `string`):

Counts, warnings, source pages, and charged event totals.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQueries": [
        "concerts"
    ],
    "location": "New York, NY",
    "dateFilter": "any",
    "maxResults": 25,
    "responseFormat": "detailed",
    "requestDelayMs": 2000
};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammadafzal/google-events").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchQueries": ["concerts"],
    "location": "New York, NY",
    "dateFilter": "any",
    "maxResults": 25,
    "responseFormat": "detailed",
    "requestDelayMs": 2000,
}

# Run the Actor and wait for it to finish
run = client.actor("muhammadafzal/google-events").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQueries": [
    "concerts"
  ],
  "location": "New York, NY",
  "dateFilter": "any",
  "maxResults": 25,
  "responseFormat": "detailed",
  "requestDelayMs": 2000
}' |
apify call muhammadafzal/google-events --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muhammadafzal/google-events"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/miechn0hBeHYhia2x/builds/ZvpLWFwAceqly356F/openapi.json