Skip to content
Primetra
All agents

Agent reference · Agentic browser

n8n workflow

n8n workflow calling your MCP server. We recognise it by the name it gives; anyone can send that name, so it is confirmed only when something else backs it.

Vendor
n8n
Agent type
Agentic browserBrowse and act for a person: open pages, click, fill in forms, check out.
Can be verified by
Can't be verifiedThe vendor publishes nothing a visit can be checked against. A visitor using this name can be named, never proven.
How sure we are
UnverifiedOnly third-party lists mention it. We name it, and never treat it as proven.
Last reviewed
Vendor documentation
github.com (opens in a new tab)

Tokens to look for

User-Agent tokens

No user-agent token is documented: its visits don't name it.

robots.txt tokens

No robots.txt token is documented for it.

Check a visitor claiming to be n8n workflow

We've filled in its token. Paste the full User-Agent from your logs and the address it came from for a real answer.

Paste the full User-Agent header from your logs. A single token such as GPTBot works too.

Optional

IPv4 or IPv6, as your logs show it. Used only for this check and never stored. Without it, a claim can only come back as can't be verified.

What this means for your site

n8n workflow acts for a person: it reads, clicks and fills in forms. Whether it can finish a task on your site is the new conversion rate.

See whether AI agents can find your product, use it and, soon, pay for it.

Run the free agent-readiness check