Slack Triggers

Slack is one of the primary trigger sources for Ryven. Mention @ryven in any channel where the bot is installed, and Ryven picks up the signal, resolves context from linked issues and threads, and dispatches an agent to ship the fix.

Basic trigger

@ryven Add a /health endpoint that returns { status: "ok", timestamp: Date.now() }

Ryven replies in the thread and starts working.

With a GitHub issue

Include a GitHub issue URL for richer context:

@ryven Fix https://github.com/acme/api/issues/123

Ryven reads the issue title, body, and comments, and uses them as context. The target repo is auto-detected from the URL.

Specifying a repository

If your workspace has multiple repos connected, you can specify which one:

@ryven in api-server, add input validation to the signup endpoint

If Ryven can't determine the repo, it replies asking you to pick from the connected repositories.

Thread conversations

Ryven keeps all communication in a single Slack thread — the one started by your @ryven mention. You'll see updates for:

• Task started (with repo name)
• PR opened (with link)
• CI fix attempts (with failure summary)
• Final result (success with PR link, or failure with error)

Follow-up messages

You can reply in the thread to provide more context or follow-up instructions. Ryven maintains the conversation context across messages.

Who can trigger tasks

Only workspace members can trigger tasks. If someone who isn't a member mentions @ryven, they'll see a message explaining they need to be invited. An access request is created for workspace admins to review.

Quick reference