What is Slackbot?
Slack uses Slackbot as its general HTTP client when a request does not belong to one of its specialized robots. Slack's robot documentation gives API calls for integrated services and outgoing webhooks configured by a workspace as examples. A hit can therefore be part of a specific Slack integration rather than a visit to public content.
This is not Slack's normal link-unfurling identity. URLs posted in channels are handled by Slackbot-LinkExpanding, while Slack-ImgProxy retrieves posted images. Keeping those clients separate matters when a site wants an integration endpoint to work but does not want Slack to generate previews for ordinary pages.
The recorded full user agent is Slackbot 1.0 (+https://api.slack.com/robots), with Slackbot as the stable token. Slack explicitly says its robots do not honor robots.txt because they act for users and do not follow links. Cloudflare also marks compliance false, despite this file's older metadata field saying true. There is no signature-agent URL or verified IP status in the record, so the user agent is not sufficient authentication for a webhook or API call.
Slackbot's traffic has no documented connection to AI search, citations, or model training. It represents product integrations and user-configured HTTP actions. Counting these requests as AI crawler visits would misstate both their origin and purpose.
