Mobilizon Events & Groups Extractor

Point at any Mobilizon instance and extract its events and groups over the public Mobilizon GraphQL API (POST {instance}/api). Mobilizon is Framasoft's ActivityPub-federated events + groups platform — the fediverse alternative to Facebook Events / Meetup. One actor reads them all: there is no per-instance scraper, because every instance speaks the same GraphQL schema.

An instance's search returns its local events plus everything it has already federated from other instances, so a large aggregator surfaces a huge shared calendar while a small activist node surfaces its own.

What you get

Four modes, one clean structured row per record:

Mode	What it does	Row
searchEvents	Browse or full-text-search the events directory	one per event
searchGroups	Browse or full-text-search the groups directory	one per group
event	Fetch a single event by its UUID (richer fields)	one event
group	Fetch a single group by its handle	one group

Event fields: uuid, title, url, beginsOn, endsOn, category, status, longEvent, locality / region / country / postalCode / street, organizerUsername / organizerName / organizerUrl, attributedToUsername / attributedToName, tags, and (single-event mode only) description, onlineAddress, phoneAddress, language, local.

Group fields: id, preferredUsername, name, domain, summary, url, membersCount, followersCount, followingCount, type, visibility, and the same address fields.

Every row also carries provenance: _mobilizonUrl, _instanceHost, _mode, _recordType, _page, _total, _rowIndex.

Input

{
  "mobilizonUrl": "https://keskonfai.fr",
  "mode": "searchEvents",
  "search": "",
  "beginsOn": "",
  "maxRecords": 2000,
  "pageSize": 50
}

• mobilizonUrl (required) — instance root; /api is appended automatically.
• mode — searchEvents (default) · searchGroups · event · group.
• search — full-text term for the search modes; empty browses the whole directory.
• beginsOn — ISO date lower bound for events. Left empty, this actor browses the whole archive (past + future); Mobilizon otherwise defaults to future-only.
• uuid — required for mode: "event".
• preferredUsername — required for mode: "group" (e.g. les_amis_vicois).
• maxRecords / pageSize — paging controls (pageSize ≤ 100).

Example instances

https://keskonfai.fr · https://mobilizon.us · https://mobilizon.it · https://mobilizon.extinctionrebellion.fr — plus hundreds more across the fediverse. Any Mobilizon deployment works.

Pricing

Pay per result — you are billed one record per event or group row emitted. No subscription, no minimum.

Your maximum charge is respected. Each row is billed in the same step that writes it. Before every request to the instance the run checks that one more record fits your Maximum cost per run and maxRecords; if it does not, it stops without making the request. If the run is restarted, records already delivered are not written or billed again, even if the instance's event list changed in the meantime.

Notes

• Pagination is page / limit with a reliable total count; the actor stops at maxRecords, at the end of the directory, or when a page yields no new rows.
• Almost every nested field (address, organizer, category) is optional and comes back null for online-only / org-less / imported events — rows are keyed on uuid (events) or preferredUsername (groups).
• If an instance is unreachable, rejects the query, or matches zero records, the run fails fast rather than reporting a fabricated empty success.
• Please keep a descriptive User-Agent and reasonable page sizes — many instances are volunteer / community deployments.