Integrations

Connect Ryven to the tools your team already uses — Slack, GitHub, Jira, and Linear.

Ryven is a control plane — it doesn't replace your tools, it sits between them. Every integration listed here is both a trigger surface (a place to send Ryven work from) and a notification surface (a place Ryven reports back to).

Available integrations

Slack

Mention @ryven in any channel or thread. The primary trigger surface.

GitHub

Trigger from issues, PR reviews, and @ryven mentions in comments.

Jira

Trigger tasks from Jira Cloud issue events and pull ticket context into runs.

Linear

Assign or @mention Ryven on a Linear issue as an agent.

How triggers work

No matter which surface a message comes from, Ryven runs the same decision: is this a new task, a follow-up on an existing one, a question it should just answer, a code review request, or a conflict-resolution ask? You get consistent behavior across Slack, GitHub, Jira, and Linear — the difference is only where you talk to Ryven.

Create a new task → Ryven clones the relevant repo, runs an agent, opens a PR
Reply in an existing thread / session → Ryven continues the same conversation
Ask a question → Ryven answers in-place without touching any code
Request a PR review → Ryven posts an inline review
Ask to resolve conflicts → Ryven rebases and pushes the fix

Setup

All integrations are connected from Settings > Integrations in the dashboard. See Connect integrations for the initial onboarding flow.

You don't need every integration to start. Slack + GitHub + an Anthropic API key is the minimum. Jira and Linear are optional additions you can wire up later.