What is Make.com?
Make.com is a workflow automation platform. The traffic covered here comes from a connector that fetches data from endpoints chosen by Make customers, so a request is usually one step in a configured scenario rather than an autonomous web-indexing crawl.
Make's HTTP integration can request a URL, download a file, retrieve headers, or call an API with supported authentication. The scenario owner selects the target and decides what happens to the response in later modules. A website may therefore see a one-off fetch, a scheduled request, or repeated calls driven by another event in the workflow.
This connector has no documented role in general AI search or model training. A Make scenario can send fetched data to many kinds of downstream modules, including an AI service if the customer configures one, but the Make.com request itself does not disclose that destination. Blocking this token is not a general AI-training opt-out and does not affect search indexing.
Cloudflare's bot directory records two user-agent values: make.com and Make.com/production. The stable token is make.com. Matching should account for capitalization and the /production suffix instead of expecting one exact string.
Cloudflare's bot directory lists no signature-agent URL, and the facts record has no verified IP status. A user-agent match can help find Make requests in logs but does not prove who owns the scenario. Expected integrations should authenticate with their normal API key, OAuth, client certificate, or other endpoint credential.
The bot metadata records robots.txt behavior as unknown, while Cloudflare's bot directory marks followsRobotsTxt as false. Many Make calls target APIs or webhook-style endpoints rather than pages discovered by crawling, which also makes robots.txt a poor enforcement boundary for this traffic.
