Bot intelligence record
Slackbot
Usually allowSlackbot is a webhook callback from Slack used for webhook delivery, payment notifications, service callbacks; it appears in server logs as `Slackbot`.
User-Agent Pattern
SlackSlackbot
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Slackbot
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Slackbot is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Record Details
Structured data- Operator
- Slack
- Family
- Slack
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Official Documented
- Confidence
- High
- Last verified
- 2026-06-23
- Last checked
- 2026-06-23
- Source type
- Official
- Verification
- Verify Slackbot by matching `Slackbot` to Slack evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- Slackbot has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
Notes
- Slackbot is a webhook callback from Slack used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Its primary user-agent pattern is
Slackbot; related patterns includeSlack service bot; Slackbot 1.0; a representative HTTP user-agent isSlackbot 1.0 (+https://api.slack.com/robots). - Slackbot is verified with High confidence. The identity type is Official Documented, and the evidence basis is official operator documentation.
- Slackbot is marked as not reliably governed by robots.txt directives; use server-side rules if the traffic should be restricted.
- Slackbot can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify Slackbot by matching `Slackbot` to Slack evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Slackbot traffic is primarily detected by the `Slackbot` user-agent pattern; related patterns include `Slack service bot; Slackbot 1.0`; a representative HTTP user-agent is `Slackbot 1.0 (+https://api.slack.com/robots)`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Slack infrastructure before trusting the traffic.
- Slackbot is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Slackbot has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, identify related datacenter activity, and create allow, block, rate-limit, or log rules across connected sites.