INTEGRATION · SLACK

Checkredirects.io + Slack

The Slack app is not built yet. This page describes the planned slash-command workflow and monitor-alert delivery so you can flag which pieces matter most. The REST API is usable today.

Use today: route monitor webhooks to Slack via an adapter

Our monitor webhooks post a signed JSON payload with our own schema (event, job_id, has_changes, and so on). Slack incoming webhooks expect a Slack-shaped message body, so a small adapter step is needed in between. Common options: a Zapier or Make step that reads our payload and posts a Slack message, or a short function on your own infrastructure. Native Slack posting is planned; see below.

Planned slash commands (roadmap)

/checkredirects https://example.com
/checkredirects batch https://a.com https://b.com https://c.com
/checkredirects compare https://example.com
/checkredirects usage

Planned workflow (roadmap)

Instant URL inspection. Paste a URL, get the redirect chain and final status code right in Slack.
Batch check. Check multiple URLs at once from a thread.
User-agent comparison. See if a URL redirects differently for Googlebot vs Chrome.
Monitor notifications. Point your monitor's webhook URL at a Slack channel to get alerts when redirects change.
Usage check. See your remaining checks for the month.

Planned setup (roadmap)

Once the app is available, connect with your API key via /checkredirects setup httpnd_your_key. The key will be stored per workspace.