# Mobilizon Events & Groups Extractor (`datamule/mobilizon-events-extractor`) Actor

Point at ANY Mobilizon instance and extract events + groups over its public GraphQL API. Browse or full-text-search the federated events/groups directory, or fetch one event/group by id. One clean row each: title, dates, category, location, organizer, tags, member counts.

- **URL**: https://apify.com/datamule/mobilizon-events-extractor.md
- **Developed by:** [Datamule](https://apify.com/datamule) (community)
- **Categories:** Developer tools, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.35 / 1,000 records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## 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](https://activitypub.rocks/)-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

```json
{
  "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.

### 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.

# Actor input Schema

## `mobilizonUrl` (type: `string`):

Root URL of ANY Mobilizon instance — Framasoft's ActivityPub-federated events + groups platform (the fediverse alternative to Facebook Events / Meetup). Its public GraphQL API is read at POST {url}/api (the /api suffix is added automatically). Examples: https://keskonfai.fr · https://mobilizon.us · https://mobilizon.it · https://mobilizon.extinctionrebellion.fr. An instance's search returns its LOCAL events plus events it has already federated from other instances.

## `mode` (type: `string`):

What to extract. 'searchEvents' = browse / full-text-search the events directory (one row per event). 'searchGroups' = browse / search the groups directory (one row per group). 'event' = fetch a single event by its UUID (richer fields incl. description / online address). 'group' = fetch a single group by its handle.

## `search` (type: `string`):

Optional full-text search term for 'searchEvents' / 'searchGroups' (the GraphQL 'term'). Leave empty to browse the ENTIRE directory. Ignored in single-event / single-group modes.

## `beginsOn` (type: `string`):

Optional ISO-8601 lower bound for event start (e.g. 2026-01-01T00:00:00Z), used in 'searchEvents' mode. IMPORTANT: Mobilizon defaults this to 'now' (future events only) — leave it empty and this actor browses the WHOLE archive (past + future); set a future date to get upcoming-only. Ignored for groups.

## `uuid` (type: `string`):

Required for mode='event' — the event's UUID (the id in its URL, e.g. https://.../events/<uuid>). Ignored in other modes.

## `preferredUsername` (type: `string`):

Required for mode='group' — the group's preferred username / handle (e.g. les\_amis\_vicois, or a federated group@domain.tld). Ignored in other modes.

## `maxRecords` (type: `integer`):

Stop after emitting this many rows (search modes). Page/limit pagination halts early once reached. Each emitted event or group is billed as one record.

## `pageSize` (type: `integer`):

Records requested per GraphQL page (the API 'limit', 1-indexed 'page'). Mobilizon caps this at 100; larger pages = fewer round-trips.

## `userAgent` (type: `string`):

Override the default descriptive User-Agent header. Many Mobilizon instances are volunteer / community deployments — please keep a descriptive agent and reasonable page sizes.

## `timeoutSecs` (type: `integer`):

Per-request timeout in seconds for each GraphQL page fetch.

## Actor input object example

```json
{
  "mobilizonUrl": "https://keskonfai.fr",
  "mode": "searchEvents",
  "maxRecords": 2000,
  "pageSize": 50,
  "timeoutSecs": 60
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "mobilizonUrl": "https://keskonfai.fr"
};

// Run the Actor and wait for it to finish
const run = await client.actor("datamule/mobilizon-events-extractor").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 = { "mobilizonUrl": "https://keskonfai.fr" }

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

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

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

```

## CLI example

```bash
echo '{
  "mobilizonUrl": "https://keskonfai.fr"
}' |
apify call datamule/mobilizon-events-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=datamule/mobilizon-events-extractor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/d0UpVNn2HfMSb4mH3/builds/gg7iSPW7PoNYSUG3T/openapi.json