Ingest Linear issues, comments, projects, and cycles into CortexDB.

Linear Connector

Captures Linear issue activity from one or more teams as CortexDB experiences. Linear webhooks for real-time; GraphQL polling as a fallback.

Info

Two ways to run this connector:

  • Run it yourself (Free + paid) — pip install 'cortexdb-connectors[linear]' then cortexdb-sync sync linear. The connector reads your token from ~/.cortexdb/state.json (written by cortexdb init) or from env vars.
  • Managed sync (Starter and up) — CortexDB runs the connector as a worker on its infrastructure. Configure it once from your dashboard; CortexDB handles webhook registration, retries, backfill, and idempotency.

1. Prepare credentials in Linear

Linear → Settings → API → Personal API keys → Create. Copy the key (lin_api_…).

2. Configure in your CortexDB dashboard

  1. Sign in at cortexdb.ai/login.
  2. Settings → Connectors → Add Connector → Linear.
  3. Paste the API key.
  4. Pick the teams to sync (comma-separated keys, e.g. ENG, DESIGN).
  5. Set the scope template. Default: org:<your-org>/source:linear/team:{team_key}.
  6. Pick sync mode: Real-time (webhook) or Polling.
  7. Click Start sync.

What gets written

EventModalityNotes
Issue created/updateddocumentTitle + description
Commentconversationrole=user; preceded_by links to issue
State changeobservationOld + new state as a triple
Cycle / Project eventsobservationCycle start, project status

idempotency_key shape: lin:<team>-<issue_number>:<event_id>.

Run it yourself

If you'd rather host the connector yourself instead of using CortexDB's managed worker, every connector ships in the cortexdb-connectors PyPI package:

pip install 'cortexdb-connectors[linear]'

# Step 1: get a CortexDB token + actor (one-time, free tier)
pip install cortexdb-cli
cortexdb init

# Step 2: supply the connector's third-party credentials
export LINEAR_API_KEY=...                # required

# Step 3: one-shot sync, or `watch` for a poll loop
cortexdb-sync sync linear
cortexdb-sync watch linear --interval 60

cortexdb-sync reads your CortexDB token + actor from ~/.cortexdb/state.json automatically. Cursor state is persisted in ~/.cortexdb/connectors-state.json, so re-running picks up where the last cycle left off.

See also