Skip to content

Integrations

qarunbook stays where each bug is tracked. The tools you connect bring bugs in, send the news out, or bring the fix back. Every integration is on every plan; plans differ only in how much you use.

Where developers fix it

Bugs go where the team already works, and the fix comes back to qarunbook for a retest.

Where bugs are reported

Raise a bug from the conversation or the inbox it started in, and hear back there when it is fixed.

Where errors are caught

Errors your monitoring sees on a live app become bugs, with the details attached.

Everything else

Thousands of other apps, without code.

Where you connect them

In qarunbook, open the app, choose Configure, then the Integrations tab. Each tool is a tile; choose one to connect it to that app. You need to be an admin of the app. A tile shows Connected once it is set up.

Integrations carry bugs, not your test plan. None of them create checks or sections — those come from qarunbook itself, the AI import, MCP (Claude Code, Codex, Cursor) or the API. A bug raised on a check carries that check's section, steps and expected result wherever it goes.

Something unclear or missing? Write to hello@qarunbook.com.