Eventbrite Event Finder with Venue Geocoordinates: MCP config, n8n workflow and API

{
  "startUrls": [
    {
      "url": "https://www.eventbrite.com/d/united-states/all-events/"
    }
  ],
  "maxItems": 3,
  "organizerMode": false,
  "includeDetails": false,
  "useSitemap": false
}

---
name: eventbrite-event-finder-with-venue-geocoordinates
description: "Omit-empty Eventbrite event records with dates, UTC times, venue address and geocoordinates, images, taxonomy, organizer profile, ticket price and availability, and optional detail fields. Runs the Apify Actor nimbryxo-studio/eventbrite-event-finder-with-venue-geocoordinates. Use when the user needs Eventbrite data with fields such as id, eid, recordType, name, summary, url and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/eventbrite-event-finder-with-venue-geocoordinates"
  store-url: "https://apify.com/nimbryxo-studio/eventbrite-event-finder-with-venue-geocoordinates"
---

# Eventbrite Event Finder with Venue Geocoordinates

Use this skill to fetch Eventbrite data with the Apify Actor `nimbryxo-studio/eventbrite-event-finder-with-venue-geocoordinates` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `startUrls` | array | Eventbrite browse URLs (e.g. https://www.eventbrite.com/d/ny--new-york/all-events/), direct event URLs (/e/...), or organizer URLs (/o/...). Accepts URL strings and {"url": ...} objects. When set, this wins over the filter fields. |
| `maxItems` | integer | Maximum number of unique events to return across all queries. The source caps each query at 1,000 events; above 1,000 the actor splits by date, category, price, and online coverage, or scans the event sitemap when useSitemap is enabled. |
| `organizerMode` | boolean | Add organizer profile metrics and social links from the organizer page. Also implied by organizer URLs in startUrls. Records stay event records. |
| `includeDetails` | boolean | Fetch the event detail page and public event API for description, ticket classes, refunds, age, door time, UTC times, duration, series counts, and the conditional Facebook event ID. Adds one or two requests per event. |
| `useSitemap` | boolean | Only for runs above 1,000. Scan Eventbrite's event sitemaps (about 201,000 event IDs) and hydrate in batches instead of splitting search queries. Filters are applied client-side. Ignored with startUrls or maxItems = 1,000. |

Example `input.json` (the Actor's published prefill):

```json
{
  "startUrls": [
    {
      "url": "https://www.eventbrite.com/d/united-states/all-events/"
    }
  ],
  "maxItems": 3,
  "organizerMode": false,
  "includeDetails": false,
  "useSitemap": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~eventbrite-event-finder-with-venue-geocoordinates/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~eventbrite-event-finder-with-venue-geocoordinates/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `id`, `eid`, `recordType`, `name`, `summary`, `url`, `sourceUrl`, `ticketsUrl`, `startDate`, `startTime`, `endDate`, `endTime`, `timezone`, `startUtc`, `endUtc`, `durationInMinutes`, `isOnline`, `isCancelled`, `isProtected`, `status`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.