A bug report only helps if someone sees it. Integrations push new reports into the tool your team already has open.
Available integrations
Integrations need a Pro or Ultra plan, and both include all eight: Telegram, GitHub Issues, Slack, Discord, GitHub Actions, Jira, Asana and Freshdesk.
The plan that counts is the project owner's. On Free, new reports still reach the team as in-app notifications and by email.
Setting one up
Open your project, go to Integrations, choose a provider, and supply its credentials. Each provider needs something different — a bot token and chat ID for Telegram, a webhook URL for Slack and Discord, a repository and token for GitHub.
Multiple integrations can run at once. Posting to a Slack channel and opening a GitHub issue for the same report is a normal setup.
Choosing well
Telegram — fastest notifications, best when one or two people triage. Ideal for solo developers and small teams who want a bug to buzz their phone.
Slack / Discord — best for teams that live in a chat channel. Give bugs their own channel; a report in #general is a report nobody reads.
GitHub Issues — best when your bug workflow already runs on GitHub and you want reports to become issues automatically.
GitHub Actions — for triggering a workflow when a report arrives. Useful for custom automation: your own labeling, routing, or on-call paging.
Jira / Asana — for teams whose planning happens there and where a bug must appear as a ticket in the same backlog as everything else.
Freshdesk — for support-led teams, where a bug report is also a customer conversation.
Integrations versus webhooks
Integrations are prebuilt connections to specific tools. Webhooks are a signed HTTP POST to any URL you control.
Use an integration when a supported tool covers your need. Use a webhook when you want custom logic — routing by severity, enriching from your own database, or posting somewhere with no prebuilt integration.
They are not exclusive. Running a Slack integration for visibility alongside a webhook for automation is a common pattern.
Troubleshooting
Nothing arrives. Verify the credentials are still valid — bot tokens get revoked and webhook URLs get rotated. Reconnecting the integration is usually enough.
A provider shows a Pro badge and no Configure button. The project's owner is on Free, and every integration needs Pro or Ultra. Only the owner can upgrade.
An integration shows Paused. Someone switched it off, or the project's owner is now on Free — after a downgrade or while a subscription is paused, integrations stop delivering. They resume when the owner upgrades; until then the owner or an admin can still disconnect them.
Reports stopped arriving partway through the month. The project may have reached its monthly report limit. At the limit the widget refuses new reports, so there is nothing for an integration to send until the count resets at 00:00 UTC on the 1st. The project's Settings page shows the count.
See also
Sending reports to your own systems with webhooks
Working with tasks and the board