Bot intelligence record
Slackbot
Usually allowUse the Slackbot identifier to separate Slack webhook or service callback traffic from normal visitor requests in server logs.
- Operator
- Slack
- Family
- Slack
- Type
- Webhook
- Source type
- Official
- Last checked
- 2026-05-20
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.
Webhook notifications, callbacks, payment events, or service-to-service integration requests.
Record Details
Structured data- Operator
- Slack
- Family
- Slack
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Official Documented
- Confidence
- High
- Last verified
- 2026-04-01
- Last checked
- 2026-05-20
- Source type
- Official
- Verification
- Compare the observed user-agent against the documented Slackbot pattern. Where available, confirm with operator documentation, published IP ranges, reverse DNS, signed-agent metadata, or published operator documentation, reverse DNS, published IP ranges, signatures, or other trust signals.
- Spoofing risk
- User-agent strings for Slackbot can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.
Notes
Slackbot is listed in the Botcrawl directory as a webhook callback service from Slack. The primary identifier for log review is Slackbot.
Identification
- User-agent pattern:
Slackbot - Family: Slack
- Type: Webhook
- Kind: Webhook
Common use
Webhook notifications, callbacks, payment events, or service-to-service integration requests.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.
Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: Yes.
Evidence and Source
- Compare the observed user-agent against the documented Slackbot pattern. Where available, confirm with operator documentation, published IP ranges, reverse DNS, signed-agent metadata, or published operator documentation, reverse DNS, published IP ranges, signatures, or other trust signals.
- Match `Slackbot` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Webhook notifications, callbacks, payment events, or service-to-service integration requests.
- User-agent strings for Slackbot can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.