Connectors

Plug in the work.
Elk reads the rest.

Every connector is a sensor. Raw activity becomes a feed, to-dos, and status you can trust.

Start a pilot See GitHub live

Three signals.
One growing catalog.

GitHub is live today. The rest is being wired in, pilot by pilot.

Collaboration signal
Gh GitHubLivePRs woven in; merges close items. Cl Claude CodeLiveAgent sessions captured as they happen.
Sl SlackComing soonChannels distilled into signal, not scroll-back.
Gm Google MeetComing soonMeetings become decisions and to-dos.
Ji JiraComing soonTickets feed status, without the ceremony.
Li LinearComing soonIssues and cycles, read in place.
Cu ClickUpComing soonTasks and docs join the weave.
Cr CursorComing soonAgent edits, attributed to their runs.
Cx CodexComing soonAgent runs tracked next to the humans.
Infra signal
Dd DatadogComing soonAlerts tied to the work that caused them.
Se SentryComing soonErrors tied to the PRs that shipped them.
Aw AWSComing soonCost and change signals from your accounts.
Gc GCPComing soonDeploys, incidents, and budgets in one feed.
Product signal
Mx MixpanelComing soonUsage shifts surface as product signal.
Am AmplitudeComing soonFunnels and retention, read for you.
Cr CRMComing soonPipeline movement beside the work driving it.
Live

GitHub, woven in.

Ship a PR. Watch the List update itself.

PRs, reviews, and merges land in your team's themes: the same live threads everything else flows into.

Activity becomes evidence
Everything lands in the right theme, linked back to the source.
PRs close their own to-dos
Closes elk:<item> in a PR body resolves the List item on merge.
Agents are first-class
Agent-authored PRs are tracked next to human ones.
elk · theme · invite flow
Gh
GitHubconnectorjust now
PR #212 merged: Rate-limit the invite endpoint. 2 reviews, 6 commits.
Invite flow Closes elk:a7b6…
ElkAIjust now
Checked off with PR #212 as provenance. Nothing re-woven into the feed: a finished item isn't fresh news.
List item done: Rate-limit the invite endpoint
elk · the List
Rate-limit the invite endpoint Ask Elk: "hand this to GitHub"
Issue #48 opened: Rate-limit the invite endpoint origin: elk
Gh
GitHubconnectorjust now
Comment posted: latest guidance from the List item, so the thread carries current intent.
Two-way

It writes back.

Most integrations only read. This one answers.

A decision made in Elk becomes work where your engineers and agents already live.

A List item becomes an issue
Ask Elk to push an item out and the connector opens the issue. An origin marker keeps the two tied.
Guidance follows the work
Already linked? The next push lands as a comment, not a duplicate issue.
Every write is attributed
Elk marks what it authored and recognizes its own echo coming back.

Connected to everything.
Not drowning in it.

A firehose is not a signal.

Elk fences each feed by what people actually act on, and every fence is a per-repo switch.

Raw GitHub events
Before fencing
51%was push traffic
Pushes, fenced off51%
Everything else49%
Half of a real feed was push rollups nobody acted on.
What reaches you
Defaults, per repo
Pull requests & mergeson
Reviews & review requestson
Pushesoff
Commentsoff
Turn pushes back on for the repo where they matter.
Routed to a person
Not just logged
1to-do
A review request becomes the reviewer's to-do: owned, on their List.
Unmapped reviewersignal only

Don't see your stack?

The catalog grows with every pilot. Tell us what you run.
Start a pilot