Channels Overview
Channels let people create, monitor, and respond to OpenVibely work from the tools they already use. The web app remains the best place to configure channels, review generated changes, and manage project settings.
What Channels Are For
| Channel | What It Enables |
|---|---|
| GitHub | Connect repositories, import project sources, and open pull requests from reviewed task changes. |
| Slack | Let approved team members create and track work from Slack conversations. |
| Telegram | Control OpenVibely from a mobile bot and receive task responses when enabled. |
| Webhooks | Let external systems create project-scoped tasks from structured events. |
How To Set Them Up
Open Channels from the System section of the app sidebar. Configure one channel at a time, test the connection when the UI offers a test action, and connect each channel to the projects where it should be allowed to create or monitor work.
Shared Concepts
- Channels should be treated as alternate front doors into the same project/task workflows users see in the web app.
- Slack and Telegram support authorized users so only approved people can interact with OpenVibely from chat tools.
- GitHub is both a channel and a repository provider, so it affects project setup and pull request review flows.
- Webhooks are best for trusted automation systems that need to create repeatable task requests.
Recommended Rollout
1. Start with one project and one channel.
2. Add only the users or systems that should be allowed to create work.
3. Run a low-risk task through the channel.
4. Review the task in the web app before merging or opening a pull request.
5. Expand channel usage once the team understands where generated work appears.