Integrations
Connect the tools your team already runs
Three routes bring work into CodeHerder. One route sends news back out to a tool you run.
Ways in
3 ways work reaches CodeHerder
Pick the one that fits. The connector needs no terminal and no CodeHerder login screen.
The web app and the ch CLI
Your whole team. The web app needs no terminal; ch adds scripting for a developer who wants it.
Create a task, check its status, or read an update, directly in CodeHerder.
Read the full doc →The claude.ai or ChatGPT connector
A product person with an idea. They ask Claude or ChatGPT to file it, with no CodeHerder login screen to learn.
Reads your tasks. It also reads your activity feed and workspace wiki pages. It writes in exactly two ways: it creates a task and it posts a comment.
Read the full doc →Inbound webhooks
A team running its own CI pipeline, monitoring tool, or issue tracker.
An external system sends CodeHerder a signed payload. A rule you write turns it into a comment, a new task, or a merge-outcome report.
Read the full doc →
Ways out
One way news leaves CodeHerder
Point an outbound webhook at your own endpoint, and it carries the event to whatever you run behind it: a Slack channel, a paging tool, a dashboard.
Outbound webhooks
A team that wants its own tools to react to CodeHerder activity, Slack included.
CodeHerder sends a signed payload to your own endpoint each time a chosen event happens.
Read the full doc →
The provider catalog
4 of 6 providers ready to connect today
A GitHub or GitLab connection checks merge-request status only, and only for a workflow stage built to wait on an outside merge. Opening and landing a merge request stays with the device's own gh or glab. Looking for a coding agent instead of a connection? See works with.
Ready to connect
GitHub
AvailableRead-only: it checks whether a linked merge request is open, merged, or closed. It never opens, merges, or writes to your repository.
Read the full doc →GitLab
AvailableRead-only: it checks whether a linked merge request is open, merged, or closed. It never opens, merges, or writes to your repository.
Read the full doc →Slack
AvailableStores the connection today. CodeHerder sends no Slack message through it yet — use an outbound webhook for that.
Read the full doc →PagerDuty
AvailableStores the connection today. CodeHerder raises no PagerDuty alert through it yet — use an outbound webhook for that.
Read the full doc →
Coming soon
Datadog
Coming soonDatadog is coming soon. It is not available to connect yet.
Jira
Coming soonJira is coming soon. It is not available to connect yet.
Bring your tools into the herd.
Connect a provider from Admin → Integrations, or point a webhook at your own endpoint.