Slack app

Crawle in Slack

Crawle monitors your sites continuously and flags what changed since the last crawl: titles, canonicals, meta robots, status codes, redirects, and links. The Slack app delivers those findings to the channel you choose, so a regression reaches the team the day it appears instead of at the next scheduled audit.

Slack channel routing

After authorization Crawle lists the workspace channels. The saved channel is the workspace default; each site can override it.

What Crawle posts

  • Critical incidents in real time, with severity, trigger, affected-URL count, and sample pages.
  • A daily digest for warnings and grouped changes. Related URL-level changes roll into one incident, deduplicated over 24 hours.
  • Crawl-trap notices, site-migration progress, and Google Search status updates.
  • A test notification on demand, so you can confirm the route before the first real incident.

Work from the channel

Incident messages carry the first two responses, so triage does not start with a context switch.

  • Acknowledge or resolve an incident from the message. The action is logged with your Slack display name.
  • View in Crawle opens the incident itself: trigger, severity, affected URLs, and the change history behind it.
  • Crawle reads channel names to build the channel picker and posts in the channels you choose. It does not read channel message history.

How it works

From Slack install to the first routed incident

01

Open Settings, Notifications

Sign in to Crawle as a workspace owner or admin and select Connect on the Slack card.

Settings, Notifications

Slack lives on the Notifications tab of workspace settings. Connect starts Slack's OAuth flow for the workspace you pick.
02

Approve the Slack permissions

Slack lists what the app can view and do, and which Slack workspace it installs into, before anything is granted.

Slack authorization

Slack shows the exact permissions before anything is installed: read channel and conversation info, and post in the channels you choose.
03

Save a channel, then override per site

One default channel carries the whole Crawle workspace. A site with its own client or on-call rota gets its own channel from that site's integration settings.

Slack channel routing

After authorization Crawle lists the workspace channels. The saved channel is the workspace default; each site can override it.

In Slack

What lands in the channel

One message per incident, not one per URL. The message carries the severity colour, the trigger that fired, the affected-URL count, and up to five sample URLs, followed by the Acknowledge, Resolve, and View in Crawle actions. When the same incident reverts, Crawle posts the resolution against it instead of opening a new thread.

After you connect

Slack returns you to Settings, Notifications with the workspace marked Active.

  • Crawle posts nothing until a channel is saved. Pick one, then use Send test to confirm the route.
  • For a private channel, invite the Crawle app to the channel before selecting it.
  • Event filters on the same screen decide which notification types reach Slack.
  • Disconnect Slack from the same card to stop delivery.

What you need

  • A Crawle subscription. The Slack app carries alerts from an existing Crawle workspace; it is not a standalone product.
  • A Crawle workspace owner or admin to connect it, disconnect it, or change the workspace channel. Crawle enforces that on the server, not by hiding the control.
  • Permission to install an app in the target Slack workspace.