Sources
Works with the tools your teams already use.
GitHub and Slack in a click each, Jira, Confluence and HubSpot close behind. Anything else sends us its work directly, so you are never waiting on us to build an integration.
Connector status
| Source | Status | Authenticated with | What it produces |
|---|---|---|---|
| GitHub App | Available | A per-installation webhook secret | merged · approvals · deploys |
| Signed webhook | Available | Per-org HMAC-SHA256 over the raw body | Whatever you name your events |
| Slack | Available | The same signing scheme, via Slack’s headers | karma, scored but never ranked |
| Jira & Confluence | Available | An RS256 invocation token, verified against Atlassian’s JWKS | tickets_created · tickets_closed · pages_edited |
| HubSpot | Available | HubSpot’s own v3 webhook signature | deals_closed · revenue_closed |
| Salesforce | Coming soon | — | — |
| Linear | Coming soon | — | — |
| Microsoft Teams | Coming soon | — | — |
Whatever you connect, you get a working board on day one, including if your team has never merged a pull request in its life. Slack works in both directions too: it can tell the team when something good happens, in the channel they are already in, once you turn that on. A source marked coming soon is not built yet — send it as a signed webhook in the meantime, and rank on it today.
GitHub
Install it, and the boards are already populated.
Installing the app loads the previous 90 days first, so nobody signs in to an empty leaderboard and concludes it does not work. Run it again any time; nothing is counted twice.
- Merged pull requests, review approvals and deployments
- Bots ignored by default, and configurable, so nobody competes with
vercel[bot] - A deploy is credited to the merge it shipped, not to the machine account that triggered it
- Link a GitHub login to a person later and the work it already sent is re-attributed
Everything else
Never blocked waiting on us.
Work in a tool we have never heard of does not wait a quarter for an integration. Send it yourself, named what your business calls it, deal_won or ticket_resolved, and rank on it today.
- Any team can be measured, not just the one that writes code
- An afternoon’s work for someone who has sent a webhook before
- Signed, so nobody can put fake numbers on your board
The exact scheme, a copy-pasteable example in bash and Node, and the one failure that returns 202 and does nothing are in the docs.
Worth knowing
Three things we will not do
We never write to your systems
No comments on your issues, no labels, no status changes, and nothing appearing in your repositories in our name. We only read what happened, and that is enforced by how the connector is built rather than by a setting.
We never slow your tools down
We answer in milliseconds and do the work afterwards, so nothing we do can make a deploy hang or a webhook time out in someone else’s dashboard.
We never read your content
Not your code, not your messages, not the text of your tickets. We record that something happened and who did it, which is already visible to everyone on your team.
Questions
Before you wire anything up
Do I need the GitHub App, or can I just use the webhook?
Either. The app is one click and backfills history, which is the fastest way to a populated board. The webhook is the right choice when the work you want to measure does not happen in a repository.
What happens if you deliver the same event twice?
It counts once. Retry as often as you like, since nobody’s number gets inflated by a system that delivered twice.
Can you read data back out of Jira or GitHub?
No. Nothing we install can write to your repositories or your issues, which is usually the first question a security reviewer asks and the easiest one to answer here.
How much of Slack works?
Karma coming in and notifications going out, both live. What does not exist yet is Slack’s own surfaces, such as App Home, slash commands and direct messages, so today Slack is a source and a destination rather than somewhere you use the product.
Can we get our data out, or delete it?
Both, and they are built rather than promised. There is a data export, and there is tenant deletion that actually removes the organization rather than flagging it.
How long do you keep raw events?
Your boards keep their full history. The raw payloads behind them expire after thirteen months, which means a year-old leaderboard still works and we are not sitting on records of your work for ever.
Does HubSpot backfill history the way GitHub and Jira do?
Not yet. Closed-won deals count from the day your workflow starts sending; there is no import of deals that closed before you connected. GitHub and Jira both load 90 days of history on connect — HubSpot will get the same treatment, but does not have it today.
What about Salesforce, Linear or Microsoft Teams?
On the way, not yet built. Send the same work through the signed webhook in the meantime — a deal stage change or a Linear issue closing is exactly the shape it is built for — and moving to the native connector later does not lose any history.
Connect one repository. See it inside a minute.
Free for your first 50 people. No card, no sales call.