AI visibility moves without anyone deploying anything. An engine changes what it retrieves, a competitor publishes the page that answers your buyer question, and your citation rate falls, with no signal in your analytics, because the click you lost was never made. Alerts are how that becomes visible on the day it happens rather than in next quarter's report. Cituna posts four kinds: visibility drift, when your score moves beyond a normal daily wobble; a competitor overtake, when a rival passes you on prompts you both appear in; AutoSEO articles, when one is waiting for your approval or a destination refuses one; and a weekly digest. Connecting is an Incoming Webhook URL pasted into one field, and any HTTPS endpoint works too if you would rather route through Zapier, Make or n8n.
1. Create an Incoming Webhook in Slack
Go to api.slack.com/apps, click Create New App, choose From scratch, name it Cituna and pick your workspace. In the app, open Incoming Webhooks and switch on Activate Incoming Webhooks.
Click Add New Webhook to Workspace, choose the channel where alerts should land, and click Authorize. A quiet channel your team actually reads beats a busy one they mute.
Slack generates a webhook URL beginning https://hooks.slack.com/services/. Copy it.
2. Paste the URL into Cituna
Open Integrations → Slack, paste the URL, and click Connect. Cituna posts a sample message to confirm the channel before saving anything, so a typo fails immediately rather than silently swallowing every future alert.
3. Choose which alerts you want
After connecting, pick your alert types: visibility drift, competitor overtakes, AutoSEO articles, and the weekly digest. Turning all four on at the start is reasonable. You can quieten the ones that prove noisy for your market once you have a fortnight of signal.
Keep AutoSEO articles on if you review articles in Cituna before publishing. That mode holds every finished article for your approval, and this alert is what tells you one is there. It also covers the failure worth knowing about immediately: a destination that has stopped accepting articles, which is capped at one message a site a day so a connection left broken for a week does not fill your channel.
4. Send a test whenever you want one
Use Send test to post a sample alert to the channel at any time. It is the fastest way to confirm the integration survived a Slack workspace change or a channel archive.
5. Or route to something other than Slack
Any HTTPS webhook works. Generic endpoints receive a flat JSON body, which is enough for Zapier, Make or n8n to branch on: route drift alerts to an on-call channel and the digest to email, for instance.
Troubleshooting
Alerts stopped arriving and nothing changed on my side.
Slack revokes Incoming Webhook URLs when the app is removed or the target channel is archived. Create a new webhook, paste it in again, and use Send test to confirm. Nothing else in your Cituna setup needs touching.
I get too many drift alerts.
Citation rates genuinely wobble day to day, particularly on a small prompt set, because engines re-retrieve constantly. Turn drift off and keep the weekly digest if the daily signal is noisier than it is useful; tracking more prompts also steadies the average.
Can different brands post to different channels?
Not today. The connection is per workspace, so all brands post to the same endpoint. If you need to split them, point Cituna at an automation tool and branch on the brand field in the payload.
Is the webhook URL stored securely?
Yes. It is encrypted at rest and never returned in any API response, the same handling every connector credential gets. Disconnecting removes it entirely.
Drafted with AI assistance from our own research and Search Console data, and reviewed by Rahul A before publishing. Rules and prices change; check the linked official source before you act.