Alerts do not have to arrive as email. Point your own Slack workspace at your account and a rule firing, credits running low or the daily summary lands where your team already is.
What you need: you have to own the account or be an administrator on it, your plan has to include integrations, and you need permission to add an app in the Slack workspace you want to post into. If your plan does not include it, the card says so and offers a link to billing.
Make an incoming webhook in Slack
An incoming webhook is an address Slack gives you that posts into one conversation. Slack has two ways to make one.
- In Slack, open the app directory and find Incoming WebHooks.
- Add it and choose where the alerts should land.
- Copy the URL. It starts with
https://hooks.slack.com/services/.
If your Slack workspace does not allow that app, build one of your own instead: turn on the incoming webhook permission, choose where it should post, and copy the URL from the same screen. The result is the same address.
Treat that URL as a password. Anyone holding it can post into your Slack workspace.
Connect it
- Open Settings > Notifications and scroll to Slack notifications.
- Paste the URL into Incoming webhook URL.
- Give it a Name. Only your team sees this, and it is what the remove dialog will ask you about later.
- Tick the events it should carry.
- Press Connect.
The Slack notifications card in Settings, with the webhook field, a name and the list of events.
We store the URL encrypted and never show it again, so keep your own copy. The card shows a shortened form of it, which is enough to tell two destinations apart.
What each event posts
- Rule fired. An automation rule matched a review and did what it says. The message names the location, the source and the rule.
- Review handled by hand. Somebody on your team replied to, assigned or archived a review by hand. On a busy account this is the noisiest of them, so it is off unless you tick it.
- Credits running low. Your account crossed the warning level set further up the same screen.
- Daily summary. One message a day with the numbers from the last 24 hours.
An agency account gets six more about its clients: a client provisioned, a client waiting on credits, credits allocated, a price that is not tied to one of your plans, an email address that clashes with another account, and a client who canceled.
Limit it to some locations
If your account holds more than one location, each destination carries a Locations this destination hears about list. Leave every box clear and it hears about all of them, including the ones you add later. Tick a few and it hears about only those, so one destination can belong to one client while another carries everything. Going back the other way is a button rather than an empty list: Send from every location says what it will do before it does it, because clearing the last box would quietly widen the destination to locations you have not added yet.
The review text switch
Include review text is off, and it stays off until you turn it on yourself.
With it off, a message names the location, the source and the rule, and the counts. It never carries a word a reviewer wrote.
With it on, the first 200 characters of the review go with the alert, along with the reviewer's first name and the site it came from. Never their profile link, never their account id, and never more than the number of characters you set. You can move that number anywhere from 40 to 500.
That is the whole of what leaves. Turning the switch on is recorded in Activity with your name against it, so it stays answerable who decided the review text should go to Slack.
Prove it works
Press Send test message on the destination. It posts one small message and shows you what Slack said underneath: accepted, refused with a code, or no answer at all. It is limited to one test every 30 seconds per destination.
Delivery log opens every attempt against that destination, newest first, with the answer, which try it was and how long it took. Attempts are kept for 30 days.
A connected destination showing its name, its redacted address, an Active badge and the Send test message, Delivery log and Remove buttons.
When it stops working
If Slack refuses everything for 24 hours the destination is switched off and the badge turns to Disabled. That usually means the webhook was revoked in Slack, or the place it posted into was archived.
Fix it on the Slack side, then press Reconnect. It starts posting again and keeps its name, its events and its delivery log. If the webhook itself is gone, remove the destination and connect the new URL as a new one: a webhook cannot be swapped underneath a running destination, because the log of one address would end up attached to another.
Remove a destination
Press Remove and confirm. It stops receiving alerts straight away and its delivery log goes with it.
The webhook itself still exists in Slack until you delete it there, so if you are removing a destination because the address leaked, revoke it in Slack as well.