Where the answers go
Alerts, digests and reports leave through one of four channels, two read surfaces hand the same figures to your own tools, and Search Console brings your search traffic in. This page says which of those work today and which do not — in both directions, so you can tell before you buy.
Working today · 7
S
Slack
LIVEAlerts and the weekly digest posted to a channel, through an incoming webhook you paste in.
E
Email
LIVEAny rule, any recipient — and scheduled reports with their CSVs attached.
W
Webhooks
LIVEEvery alert as signed JSON, with the secret shown once so you can verify it.
A
Actions board
LIVEA rule can open a brief in the app instead of sending anything — the default for most people.
R
REST API
LIVEFive read-only endpoints under /api/v1 — visibility, prompts, citations, actions and demand — behind a key you create in Settings.
M
MCP server
LIVEAsk your visibility data a question from the assistant you already work in. The same five endpoints as tools, over JSON-RPC at /api/mcp.
Google Search Console
LIVEConnect a property and its clicks, impressions and queries sync in on a trailing window, so search traffic sits beside what the engines say.
Not built yet
Zapier
NOT BUILTNo Zapier app yet. A Zap can already catch the signed webhook above, which is how to wire one today.
Looker Studio
NOT BUILTNot built. The read API and your Search Console figures are both there to build one on; the connector itself is later work.
H
HubSpot and Salesforce
NOT BUILTNot built. Leads captured on your site can already reach a webhook; a native CRM sync is later work.
Need one that is not here? Tell us which, and what it would have to do.Request an integration→
An alert is only useful where you already look