Slack integration
Slack is on the map, not in the product yet.
Pipeline events arrive in your Slack channel: drafts ready, posts published, indexing verified, rankings won.
How it works
The Slack integration installs as a Slack app through OAuth, and the install returns an incoming webhook URL tied to one channel you pick during the flow. From then on, the pipeline posts there when a draft is ready for review, when a piece publishes, when index verification confirms a page is in Google, and when a page wins a meaningful ranking improvement.
In the loop, Slack is how the pipeline stays visible without anyone polling a dashboard. Review requests reach the people who approve content, publish and verification notices close the loop on each piece, and ranking wins surface the compounding results. Messages are formatted with Block Kit and link straight back to the relevant page in SearchHandled, so a notification is one click from the action it asks for.
Best forTeams who live in Slack and want the content pipeline to report in rather than wait to be checked.
Setup, step by step
- Click Connect on the Slack card, which starts the Slack app install.
- Sign in to your workspace and approve the app.
- Pick the channel the webhook should post to, which is part of Slack's install flow.
- Choose which event types you want, from draft-ready through ranking wins.
- Send the test notification to confirm messages land in the chosen channel.
Best practices
Pick a channel the deciders read
Draft-ready notifications only shorten review cycles if approvers see them. A focused content channel beats a busy general one, and beats a graveyard channel nobody opens.
Install again for a second channel
One webhook posts to one channel by design. If reviews belong in one channel and ranking wins in another, run the install once per channel and split event types between them.
Tune event types to the audience
Not every channel wants every event. Many teams send draft-ready notices to the editors and keep publish confirmations and ranking wins for a wider channel, which the per-connection event settings support.
Treat the webhook URL as a secret
Anyone holding the URL can post to your channel. We store it encrypted and never display it after setup, and if it leaks elsewhere, Slack revokes leaked webhook URLs and a reinstall issues a fresh one.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
One webhook posts to one channel
The incoming webhook from an app install is bound to a single channel, so one connection cannot fan events out across several channels.
How we handle itInstall the app once per channel you want. Each connection carries its own event-type settings, so different channels can receive different slices of the pipeline.
docs.slack.dev
Leaked webhook URLs get revoked
If a webhook URL is exposed publicly, Slack revokes it, and notifications stop until a new webhook is issued.
How we handle itWe keep the URL encrypted and out of sight after setup. If a revocation ever happens, the connector reports the webhook as dead and a quick reinstall restores notifications.
docs.slack.dev
Block Kit payload limits
Slack caps message payload sizes and block counts, so an over-detailed notification can be rejected.
How we handle itOur messages are built compact by design, a short summary with a link back to the full detail in SearchHandled, so they sit far below the limits.
docs.slack.dev
Questions teams ask
- Can different events go to different channels?
Yes, by installing the app once per channel. Each install creates its own webhook and its own event-type selection, so reviews can go to editors while wins go to a wider room.
- Can we act on a notification from inside Slack?
Each message links directly to the relevant item in SearchHandled, so approving a draft is one click away. The actions themselves happen in SearchHandled, where the full context lives.
- What if we do not use Slack?
The email digest covers the same events on a daily or weekly rhythm, and Zapier can route pipeline events to other chat tools your team uses.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Slack matters moves it up the rollout.