Statewave Connectors feed real-world events into Statewave so agents can remember projects, customers, communities, docs, tickets, emails, and workflows — not just live chat transcripts.
A connector is a small, focused package that reads from one source, normalizes its events into the Statewave episode schema, and lets the CLI or your own code ingest them. Statewave compiles those episodes into durable memories per subject, and serves compact context to your agents on demand.
Status: the v0.1 connector matrix is fully shipped, plus two polish waves (v0.5.x, v0.6.0), the Tier 2 push-receiver wave (v0.7.0–v0.11.0), and the Tier 3 operator/cloud productization wave (v0.12.0–v0.17.0) — TOML config file (multi-instance), hosted runner (
statewave-connectors run), persistent state adapters (file / Postgres / Redis), built-in OIDC verification for Gmail Pub/Sub, auth-gated Prometheus/metrics, and deployment recipes (Docker / Compose / Helm / Fly / Railway). All packages — GitHub, Markdown, MCP, Slack (pull + Events-API webhook + DM/MPIM dispatch), n8n, Zapier helper, Discord, Zendesk (pull + webhook receiver), Intercom (pull + webhook receiver), Freshdesk (pull + webhook receiver), Notion, Gmail (pull + Cloud Pub/Sub push receiver), Jira (preview; pull + Events webhook receiver + opt-in transitions/sprint; Cloud verified, Server/Data Center implemented + unit-tested with live validation pending), and database (preview; PostgreSQL / MySQL / MariaDB / MSSQL; rows + opt-in schema-metadata mode) — are on npm with provenance attestation.statewave-connectors listen <connector>is the unified push-receiver daemon;statewave-connectors runis the hosted runner for long-running connectors. Long-running daemon shapes (Slack Socket Mode, Discord Gateway, Gmail service-account auth) are still queued. See the roadmap for the full release timeline.
Connect Statewave memory to any MCP-compatible client — coding assistants, agent loops, custom tools. Vendor-neutral by design. → MCP server
Turn issues, pull requests, reviews, releases, and discussions into repo memory. → GitHub connector
Turn local docs, ADRs, RFCs, and decision notes into project memory — the team's actual reasoning, not a re-derivation of it. → Markdown connector
Turn channel and thread history into team memory under team:<team_id>. Pull mode (Web API + bot token + --channels allowlist) and an Events-API webhook receiver (statewave-connectors listen slack) that ingests messages, replies, reactions, and pins in real time, with opt-in DMs and group DMs (subjects dm:<user> / mpim:<channel>). slack.message.posted, slack.thread.replied, slack.dm.*, slack.mpim.*. → @statewavedev/connectors-slack README
Turn workflow executions, failures, and per-node errors into workflow memory under workflow:<id>. Pull-mode against the n8n REST API; API-key auth. n8n.workflow.executed, n8n.workflow.failed, n8n.node.errored. → @statewavedev/connectors-n8n README
Push-mode helper rather than a sync connector — Zapier deliberately doesn't expose a public API for enumerating other zaps' run history. The package ships formatZapToEpisode() for users who want to receive Zap webhooks server-side, plus integration docs for the no-code "POST straight to /v1/episodes/batch" path. → @statewavedev/connectors-zapier README
Turn server channel + thread history into community memory under community:<guild_id>. Bot-token auth; required --guild + --channels. discord.message.posted, discord.thread.replied. → @statewavedev/connectors-discord README
Turn tickets + public replies + internal notes into customer memory under customer:<org_or_requester_id>. Pull mode (API token + OAuth bearer auth, --brands / --statuses allowlists, Incremental Tickets Export delta sync via --cursor / --use-incremental) plus a webhook receiver (statewave-connectors listen zendesk) with HMAC-SHA256 signature verification, replay-window protection, and support for both trigger-driven and event-driven payloads. zendesk.ticket.created, zendesk.ticket.solved, zendesk.comment.posted, zendesk.comment.internal_note. → @statewavedev/connectors-zendesk README
Turn conversations + replies + admin notes into customer memory under customer:<company_or_contact_id>. Pull mode (bearer auth — personal-access or OAuth, US/EU/AU regions, --tags / --teams allowlists) plus a webhook receiver (statewave-connectors listen intercom) that verifies Intercom's X-Hub-Signature HMAC-SHA1 and dispatches all five conversation.* notification topics. intercom.conversation.created, intercom.conversation.closed, intercom.conversation.replied, intercom.conversation.note_added. → @statewavedev/connectors-intercom README
Turn tickets + public replies + private notes into customer memory under customer:<company_or_requester_id>. Pull mode (API key Basic auth, native updated_since server-side --since filter, status-code normalization) plus a webhook receiver (statewave-connectors listen freshdesk) that verifies a configurable shared-secret header set on the Freshdesk Automation step. freshdesk.ticket.created, freshdesk.ticket.resolved, freshdesk.conversation.posted, freshdesk.conversation.internal_note. → @statewavedev/connectors-freshdesk README
Turn pages, optional body content, and (opt-in) page-level discussion comments into decision memory under workspace:notion (or any operator-supplied subject). Bearer auth; pinned to Notion-Version: 2022-06-28; --databases allowlist for database-scoped pulls. notion.page.created, notion.page.updated, notion.comment.posted. → @statewavedev/connectors-notion README
Turn messages matching a required Gmail search query into relationship memory under relationship:<other_email>. Pull mode (OAuth 2.0 refresh-token flow, History API delta sync via --cursor, --label-ids server-side filter, MIME body extraction text/plain → text/html → snippet) plus a Cloud Pub/Sub push receiver (statewave-connectors listen gmail) — Gmail's users.watch publishes a { emailAddress, historyId } pointer to a Pub/Sub topic; the receiver walks the History API from a persistent per-mailbox cursor and emits the same episode kinds the pull connector does. gmail.message.received, gmail.message.sent. → @statewavedev/connectors-gmail README
Turn Jira issues and (opt-in) comments into project memory under project:<KEY>. API-token auth, project allowlist, no-email user fields (displayName / username / accountId), ADF / plain-text → text, redaction. Pull mode plus a webhook receiver (statewave-connectors listen jira) that verifies Jira admin webhooks' X-Hub-Signature HMAC-SHA256 in real time. Opt-in status transitions (--include transitions → jira.issue.transition, also emitted by the webhook) and opt-in sprint context (--sprint-field). Jira Cloud (REST v3) is exercised end-to-end; Jira Server / Data Center (--deployment server, REST v2, PAT/Basic auth) is implemented and unit-tested, but live validation against an on-prem instance is still pending. jira.issue.created, jira.issue.resolved, jira.comment.created, jira.issue.transition. → @statewavedev/connectors-jira README
Ingest selected external rows from a relational database into Statewave memory. One package, four dialects — PostgreSQL, MySQL, MariaDB, MSSQL. Read-only, allowlisted table or operator SELECT, selected columns, required --max-rows, ${ENV} secrets, no schema-wide data dump, no mutation queries, no binary ingestion. An opt-in schema-metadata mode (--mode schema --tables <allowlist>) ingests catalog metadata — columns, primary key, indexes — for an explicit table allowlist and never reads data rows or crawls the instance (database.schema). This is a source connector, not a Statewave storage backend — Statewave's own storage remains PostgreSQL + pgvector. database.row, database.schema. All four dialects — PostgreSQL, MySQL, MariaDB, and MSSQL — are live-verified (MSSQL has no per-session read-only flag, so use a least-privilege read-only login). → @statewavedev/connectors-database README
Connectors are developed as a monorepo but published as separate, independent packages. You install only what you need.
npm install @statewavedev/connectors-github
npm install @statewavedev/connectors-markdown
npm install @statewavedev/connectors-slack
npm install @statewavedev/connectors-n8n
npm install @statewavedev/connectors-zapier
npm install @statewavedev/mcp-serverA convenience meta-package @statewavedev/connectors re-exports the official connectors for the rare case where you want them all at once. It is not required for normal usage and not the recommended install path.
You never need to install Slack, n8n, or Zapier to use the GitHub connector. Each connector pulls only the credentials and dependencies it actually uses.
- New here? Quickstart →
- Want the model? Concepts: episode, subject, kind →
- Picking subjects? Subject strategy →
- Worried about data? Privacy & redaction →
- Building a new connector? See contributing in the connectors repo.
- Subject Design — the deep architectural treatment of subjects in Statewave
- API v1 Contract — the underlying ingest and context APIs that connectors call
- Architecture Overview — how episodes become memory becomes context