Integrations
Send Qualflare events to GitHub, GitLab, Jira, Linear, Notion, Slack, Microsoft Teams, Discord and PagerDuty, and set up webhooks for each project.
Last updated
Qualflare integrations send project events to the tools your team already uses: they file issues in GitHub, GitLab, Jira or Linear, create Notion pages, post to Slack, Microsoft Teams or Discord, or open PagerDuty incidents, and each project has one configuration per integration.
Integrations only send data out. A new defect becomes an issue where your engineers already work, and a failed test run posts a message without anyone copying a status by hand. The only thing that comes back is the link to an issue filed for a defect, which the defect shows under Linked issues. Status changes in the other tool don't sync back to Qualflare.
Integrations by category
The Integrations page in the workspace sidebar groups integrations in the tabs All, CI/CD, Notifications and Testing.
| Integration | Tab | What it does |
|---|---|---|
| GitHub | CI/CD | Files GitHub issues in a repository you choose |
| GitLab | CI/CD | Files GitLab issues in a GitLab.com project you choose |
| Slack | Notifications | Posts messages to a Slack channel |
| Microsoft Teams | Notifications | Posts cards to a Microsoft Teams channel |
| Discord | Notifications | Posts messages to a Discord channel |
| PagerDuty | Notifications | Opens and resolves PagerDuty incidents |
| Jira | Testing | Files Jira issues through the Qualflare app for Jira |
| Linear | Testing | Files Linear issues for a team you choose |
| Notion | Testing | Creates pages in a Notion database you choose |
The CI/CD tab holds the GitHub and GitLab issue integrations. To upload test results from a pipeline, see CI/CD integration.
Webhooks aren't on the Integrations page: set them up per project, in Project Settings → Webhooks.
Each integration offers a different set of events: see Integration events.
How integrations work
Qualflare uses a two-level integration model:
- Workspace-level install — Connect an external service once for the whole workspace (authentication, OAuth)
- Project-level binding — Configure which project connects to which repo, channel, or board
Every delivery attempt is listed under Recent deliveries on the project's Integrations page.
Install an integration
Editor+ · workspace (requires the Editor role or higher in the workspace)- In the workspace sidebar, open Integrations
- Find the integration you want to install and click Install
- Finish the connection:
- Slack, GitHub, GitLab, Linear, Notion, Discord and PagerDuty: approve access on the provider's site, and you are sent back to Qualflare
- Jira: get a pairing code, as described in Jira Integration
- Microsoft Teams: enter a channel Name and the Webhook URL of a Teams Workflows webhook (see Microsoft Teams)
- The integration is on once installed. Disable and Enable on its card pause and resume it. Like Remove, they work only for the person who installed it or a workspace Maintainer or Owner
Configure a project
Editor+ · project (requires the Editor role or higher in the project)- In the project sidebar, open Integrations. Only integrations that are installed and enabled in the workspace appear
- Click Configure on the integration (Edit once it is set up)
- Select the target (for example a repository, channel or team) and at least one event
- Click Save
Each project has one configuration per integration. Recent deliveries, below the cards, shows each delivery's outcome and why it failed.
Remove an integration
Removing an integration deletes every project's configuration for it. To use it again, install it and set up each project from scratch.
On the integration's card in Workspace → Integrations, click the trash icon, then Remove. Only the person who installed it, or a workspace Maintainer or Owner, can remove it.
Related
- Guides: GitHub · GitLab · Jira · Slack · Create, triage and close defects
- Reference: Integration events · Webhooks · Project Settings · Core concepts
- CLI/API: CI/CD integration
- Changelog: What's new in Qualflare: September 2026
Rotate the CI access token
Replace an expiring Qualflare access token in CI with no failed uploads: create the new token, update the CI secret, run the pipeline, then revoke the old one.
Integration events
Every event Qualflare integrations send: what triggers it, which integrations offer it, the message each one posts, and how to read Recent deliveries.