Monitor AI citations from n8n

What it does today

Every Monday it reads our signals endpoint for the domain you configure and compares the result with what it saw last week. If the set of engines citing you changed, or the 0–100 visibility score moved, it posts a Slack message naming which engines cite you and when that was measured. If nothing changed, it stays quiet.

It reports what we have already measured. If a domain has never been audited, the workflow says so rather than reporting a zero — a domain we have not measured and a domain no engine cites are different answers, and the endpoint keeps them apart.

Install

1. Run the free audit for your domain once. TriRank only reports domains it has measured, and that first run is what seeds the reading this workflow watches.
2. Import the template into n8n, open the configure step and set your domain.
3. Add a Slack credential, pick a channel, and activate the workflow. State is only recorded on scheduled runs, so a manual test click does not establish a baseline.

The README that ships with the template carries the full install notes, the message semantics and the credential rules. It travels with the workflow, so it is the copy you will have open while importing.

What it costs you

Nothing, at this frequency. The signals endpoint is read-only and rate-limited by caller: 60 reads a day without a key, 200 with a key on a free account, 1000 on a paid one. One weekly run uses one read.

Add the key as an n8n Header Auth credential rather than typing it into the node — n8n's template rules forbid hardcoded keys, and so do ours. A rejected key does not fail the run: it falls back to anonymous and the message says so once.

API documentation