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
LIVE
Alerts and the weekly digest posted to a channel, through an incoming webhook you paste in.
E
Email
LIVE
Any rule, any recipient — and scheduled reports with their CSVs attached.
W
Webhooks
LIVE
Every alert as signed JSON, with the secret shown once so you can verify it.
A
Actions board
LIVE
A rule can open a brief in the app instead of sending anything — the default for most people.
R
REST API
LIVE
Five read-only endpoints under /api/v1 — visibility, prompts, citations, actions and demand — behind a key you create in Settings.
M
MCP server
LIVE
Ask 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
LIVE
Connect 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 BUILT
No Zapier app yet. A Zap can already catch the signed webhook above, which is how to wire one today.
Looker Studio
NOT BUILT
Not 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 BUILT
Not 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