When ValiqAI finds a problem, it shows the Sentry errors that fired on that page while the scan was running: the issue, how many times, and a link straight to it in Sentry. A form that never submits often has a TypeError right next to it.
Only errors on the scanned site during the scan count (a minute before to two after), grouped by issue, worst first. ValiqAI only reads, with an internal integration token you create in your own Sentry organization.
How it works
- A scan runs. ValiqAI clicks through your flows; your app reports its errors to Sentry as usual.
- ValiqAI asks Sentry. Which error events hit the scanned site in that window, by page and issue, in one query.
- Each problem shows them. The Sentry issues from the problem’s page, linked, right in the problem panel.
Set up
In ValiqAI, open Integrations › Sentry in your workspace.
- In Sentry, create an internal integration (Settings › Developer Settings › Custom Integrations) with Organization: Read and Issue & Event: Read.
- Paste its token here and pick your region (or your self-hosted address).
- Pick the organization.
Plan
Sentry is on the Teams plan (Teams and Enterprise). A connection made before a plan change keeps working.
With AI tools
With the ValiqAI MCP server added to your AI coding tool, you can ask:
- “Which Sentry errors fired during the last ValiqAI scan of staging, and on which problems?”
- “Scan the sign-up flow with ValiqAI and show me the Sentry issue behind each blocker.”