API
Connectors
Inbound integrations that ingest into MemHQ without you writing a worker.
Connectors
Connectors are managed inbound integrations: MemHQ pulls (or accepts push from) a third-party source and writes the result into a project as episodes. You configure the destination project, user/group mapping, and optional filters; the connector does the rest.
Coming soon — full guide. Below is the planned catalog.
Planned connector catalog
| Source | Direction | Status |
|---|---|---|
| Slack | Push (Events API) | Beta |
| Linear | Push (webhooks) | Beta |
| Notion | Pull (incremental sync) | Planned |
| Google Drive | Pull (changes API) | Planned |
| GitHub | Push (webhooks) | Planned |
| Generic webhook | Push (any source) | Available now — see Webhooks |
How a connector maps to memory
Each connector defines:
- Identity mapping — how an upstream actor (a Slack user, a Linear
assignee) becomes a MemHQ
user_idand/orgroup_id. - Episode shape — how the upstream payload is translated into the
messagesarray on/v1/memhq/add. - Filters — channel allowlists, event-type filters, content redaction rules.
You configure all of this from the dashboard's Connectors panel; no worker code on your side.
Until then
If you need ingestion from a source we don't have a managed connector
for, point that source at a generic webhook and write
a thin handler that calls /v1/memhq/add.