Skip to main content
Web Extraction

Facebook Profile Events

Fetch one page of public Facebook page events by URL, including event names, dates, organizer details, places, status flags, and pagination tokens when available.

View details

Inputs

Loading input fields...
Execution Steps

Loading workflow structure...

Loading curated examples...

Overview

Facebook Profile Events fetches one page of public events from a Facebook page URL, including event names, URLs, date labels, start times, organizer details, locations, online, canceled, past, and happening-now flags, and cursor pagination. Use it for local marketing planning, venue research, and campaign timing checks.

Use cases

  • Review upcoming, live, past, or canceled public events tied to a Facebook page.
  • Collect event names, dates, host details, places, city labels, online flags, and event URLs for planning.
  • Use returned cursors to inspect another page of events from the same Facebook page.

Input tips

  • Provide a full HTTPS Facebook page URL.
  • Leave cursor blank to fetch the first events page.
  • Use a returned cursor from a previous result to request another page.
  • Use Facebook Profile first when you need page identity or business-hours context.

Expected output

The AI Tool returns availability status, lookup kind, canonical source URL, requested cursor, normalized events, next cursor, hasMore, optional total and provider counts, skipped items, provider messages, normalization notes, additional recovered fields, and cost metadata. Events can include IDs, names, URLs, canceled, happening-now, online, and past flags, event-kind labels, date/time labels, start timestamps, creator summaries, place names or cities, and recovered fields.

Caveats

  • Each run returns one events page, not a complete calendar history.
  • Events can be changed, canceled, hidden, deleted, or re-ordered after the run.
  • Pages with no public events, no recent events, or an empty cursor page may return no events.
  • Date labels and online or location flags come from returned public data; verify critical timing on the event page.