# Connectors and triage

> Let a model of your choice review findings, and write findings to Supabase or an evidence graph to FalkorDB, from Keryn Web.

Source: https://keryn.dev/docs/guides/connectors/

## Goal

Understand what a connector is and which guide to follow. Connectors are set up under Settings, Connectors in [Keryn Web](https://keryn.dev/docs/guides/web-app/). Nothing is sent until you press Test, Triage or Send, and each call goes only to the address you configured.

## Before you start

- A result in Keryn Web.
- A decision: do you want a model's second opinion on findings, or a place to keep them? The first is [triage](https://keryn.dev/docs/guides/triage/); the second is [export to Supabase and FalkorDB](https://keryn.dev/docs/guides/export-stores/).

## Triage a result

1. Scan something, so there are findings.
2. Under Settings, Connectors, pick a model connector from the [list](https://keryn.dev/docs/reference/connectors/), fill in its fields and press Test. Test sends no finding.
3. Press Triage on the results. A panel names the model, the host and how many findings will go, and has a box for the code excerpts. Nothing is sent until you confirm it.
4. Verdicts arrive as each batch returns and appear next to the findings. Stop at any time; the verdicts so far are kept.

What is sent, how many findings, what the five verdicts mean and what a verdict can and cannot do are on [agentic triage](https://keryn.dev/docs/edges/agentic-triage/). The endpoint, key header and fields of each provider are on its own page under [connectors](https://keryn.dev/docs/reference/connectors/).

![The Connectors tab of Keryn Web settings: models, data stores and issue trackers Keryn may send findings to, each with its own settings; nothing is sent until you press Test or Send.](https://keryn.dev/screens/web-connectors-1280-light.webp)

*Connectors settings. Taken from keryn.app main-DIcUUbkq.js.*

## Write findings to a store

- **Supabase**: findings and verdicts as rows in a table you name. See [Supabase](https://keryn.dev/docs/reference/connectors/supabase/).
- **FalkorDB**: the evidence graph as Cypher statements, through your own relay, or as a script you download and load yourself. See [FalkorDB](https://keryn.dev/docs/reference/connectors/falkordb/).

## When the page cannot reach a provider

The page reaches only the hosts its content security policy lists, and some providers do not answer browser requests. Deploy a [Keryn relay](https://keryn.dev/docs/reference/connectors/relay/) on your own Cloudflare, Vercel, Netlify or Supabase account and point the page at it. The provider key then lives in the relay, not in the tab.

## What you just proved

A connector is the **only edge** by which a finding can leave Keryn Web, and it is a button, not a setting. The page can reach only the hosts its content security policy lists, you configured the destination, and the confirmation panel names it before anything goes. That is the answer to "where do my findings go?": nowhere, until you decide, and then to one place you can read.

## Next

- Review findings with a model: [triage](https://keryn.dev/docs/guides/triage/).
- Keep findings in a store: [export to Supabase and FalkorDB](https://keryn.dev/docs/guides/export-stores/).
- Every connector's fields: [connectors reference](https://keryn.dev/docs/reference/connectors/).
