Connection register
What connects today,[1][1] And how far it goes: every entry below carries the edge it stops at (unsigned webhooks, one REST endpoint, a beta MCP server), printed next to the capability, not after it. and how far it goes
Integration pages are usually a wall of logos with every status set to available. This one is labelled by what you can actually switch on, and several entries below say plainly where the edges are.
How to read this page
- Available
- Works today, exactly as described here.
- Limited
- Real, and narrower than the name suggests. The narrowing is spelled out in the entry.
- Beta
- Implemented and not yet something to build a process on.
If something is missing from this page, it does not exist yet. There is no roadmap tier on this list.
01: Alerts and delivery
Getting findings out of CiteTrail
Nobody opens a dashboard daily. These are the paths a finding takes to reach a person or a system that will act on it.
Slack
An incoming webhook posts alerts to a channel you choose: a brand mention dropping, a competitor surging, a run failing, or a Reddit engagement spike.
What you should know
This is not a Slack app: there is no install flow, no bot user, no slash commands and no ability to read anything from your workspace. You paste a webhook URL and we post to it.
Webhooks
Events are delivered to your endpoint, and outbound requests are guarded against SSRF at connect time.
What you should know
Two things are missing and both matter if you are building on this: payloads are not HMAC-signed, so you cannot verify they came from us, and there are no retries, so a failed delivery is a lost delivery.
Reddit mention tracking
We query Reddit's public search endpoint for mentions of your brand, with sentiment labelling and high-engagement alerting.
What you should know
This is not the authenticated Reddit API, it runs on request rather than on a schedule, and its sentiment is keyword-based rather than the model classifier used elsewhere in the product. Treat it as a lead, not a measurement.
02: Programmatic access
Build on top of your own data
Authenticated with API keys, and honest about how much surface is open today. There is no point discovering the boundary after you have started building.
REST API
Read your workspace overview programmatically with an API key, for a dashboard or a warehouse of your own.
What you should know
Exactly one endpoint accepts an API key today: workspace overview. Everything else requires a browser session. If you are planning an integration around this, plan around that one endpoint.
MCP server
JSON-RPC over server-sent events, authenticated with an API key, so an assistant or agent can query your workspace directly.
What you should know
It works. It is pinned to an older revision of the protocol and SSE is the only transport, so it is not yet stable enough to sit underneath something you rely on.
API keys
Keys are created, hashed at rest with SHA-256, and revocable at any time.
What you should know
There is no key-management interface yet, and the key value is shown once at creation. If you lose it, create another and revoke the old one.
03: Measurement
Joining visibility to what actually happened
Both store an encrypted refresh token and the property or site you selected. Neither can write anything back to your Google account.
Google Analytics 4
Connect through Google sign-in and pick a property. Professional and above.
What you should know
Access is read-only, and data refreshes daily over a rolling 28-day window.
Google Search Console
Connect through Google sign-in and pick a verified site. Professional and above.
What you should know
Read-only, refreshed daily, with a two to three day reporting lag on Google's side rather than ours. Branded-query tracking needs your brand aliases set on the brand first, or the queries will not match.
04: attribution
What an integration can and cannot tell you
Connecting GA4 or Search Console does not turn AI-assisted discovery into a click funnel. Most assistants strip the referrer, so a large share of the traffic they influence arrives looking direct.
What you get is four separate columns. Observed traffic arrived with an identifiable assistant referrer. Estimated is modelled influence. Inferred is a correlation. Exposure means your brand appeared in an answer, which is a fact about the answer and not about traffic. We never add those four together.
Read the full attribution definitions05: Questions
Integrations, answered plainly
How do I connect GA4 or Search Console?
From workspace settings, choose the provider and sign in with Google. You then pick the GA4 property or the Search Console site to read from. Access is read-only and refreshes daily.
What exactly do you store from a Google connection?
An encrypted refresh token and the property or site you selected, plus the metrics we read on each refresh. We cannot write to your Google account and do not request write scopes.
Is the Slack integration a Slack app?
No. It is an incoming webhook. There is no install flow, no bot user and no read access to your workspace. If you need a real Slack app, it does not exist yet.
Are webhook payloads signed?
No. Payloads are unsigned and there are no retries. If you need verified, at-least-once delivery, this is not yet suitable for that.
What can I do with the REST API?
Read the workspace overview endpoint with an API key. That is the whole API-key surface today. Everything else needs a session.
Can I depend on the MCP server?
Not yet. It is beta, SSE-only and pinned to an older protocol revision. It will change.
The integration I need is not listed. When is it coming?
If it is not on this page, it does not exist. We do not publish a roadmap tier here, because a planned integration on an integrations page reads as an available one. Tell us what you need on the contact page and we will tell you honestly where it stands.
- The status legend has exactly three states on purpose. A fourth, “planned”, used to exist for GA4 and Search Console before their OAuth flow shipped. It is gone now because everything left on this page is either real today or absent.
Need something on this page to move faster?
Tell us which line is blocking you. It is the most useful thing you can send us.