n8n: run Attensira on a schedule with nobody at the keyboard
In n8n, add the MCP Client Tool node to an AI Agent workflow, point it at https://mcp.attensira.com/mcp over HTTP Streamable, and store a workspace API key as a Bearer credential. The workflow can then read your AI visibility, check that the crew is working and post the result wherever you want, at 3am with nobody there to sign in.
7 days free · card requiredHow the trial works
Asked: Is the crew working, and is anything blocked?
called get_loop_health days=7
Working. Answers were read and work was produced every day, and the work is waiting on us.
- Answers read on 3 October
- 122
- ChatGPT 61, Perplexity 61, none failed
- Work produced, 3 and 4 October
- 2 pieces
- Waiting for approval
- 10 pieces
- Pull requests opened
- 0
- GitHub is not connected on this workspace
A health check a scheduled workflow can run before anyone is awake.
Who does the work
Outreach · Found the roundup
Researcher · Stored the answer
How do I connect n8n?
Node: MCP Client Tool (inside an AI Agent workflow)
Endpoint: https://mcp.attensira.com/mcp
Transport: HTTP Streamable (not SSE)
Credential: Bearer auth → atn_live_<your key>
Tools: restrict to the reads this workflow needs
What are the limits of an unattended workflow?
- n8n cannot sign in with OAuth here, because nobody is there to approve a browser prompt. A static key never expires until revoked, so one key per workflow is what lets you switch one off.
- The server speaks Streamable HTTP only. A node set to SSE will not connect, whatever the credential.
- Restricting tools bounds what the agent can call, not what the instruction asks for. An agent asked for something its tools cannot do reports a failure rather than finding another way.
- Step 01
Mint a key for this workflow
Under Settings → Your assistant, mint a workspace API key, read-only if the workflow only reads. Name it after the workflow so revoking it later breaks nothing else. The key is shown once; only a hash is stored.
- Step 02
Add the MCP Client Tool node
Inside an AI Agent workflow, add the MCP Client Tool node. Set the endpoint to https://mcp.attensira.com/mcp and the transport to HTTP Streamable. Not SSE, which the server does not offer.
- Step 03
Store the key as a credential
Choose the Bearer or header-auth credential type and put the key there, not in the node. n8n credentials are encrypted at rest and not written into the workflow JSON, so an exported workflow carries no secret.
- Step 04
Restrict the tool list
The node exposes Attensira's tools to the agent. Restrict the list so an unattended run cannot reach credit-spending tools such as run_automation or destructive ones such as remove_prompt.
What does a client-report question read?
An n8n flow that sends a weekly client report is built for “AI visibility reporting tool for client reports”. Its answers cite one roundup in 97 of 108, and us in none: a placement, not a page, is the gap.
| Name | Cited in | Count |
|---|---|---|
| therankmasters.com | 89.8% | 97 |
| agencyscope.ai | 53.7% | 58 |
| semrush.com | 50.9% | 55 |
| ai-search-tools.com | 40.7% | 44 |
| neuralgen.io | 39.8% | 43 |
| attensira.comyou | 0.0% | 0 |
Outreach · Found the roundupattensira.com prompt board, read over the Attensira MCP · · n=108 answersWhat can a scheduled n8n workflow check?
- Run a morning check with nobody present, such as loop health, the week's mention rate or what waits for approval, and send it to Slack, email or a sheet.
- Keep the credential out of the workflow definition, so the workflow can be exported, reviewed or committed safely.
- Bound what an unattended agent may reach by restricting the node's tool list, rather than trusting the instruction alone.
- Call the REST API from an ordinary HTTP node instead, with the same key, when you want a fixed request rather than an agent.
What did the health check show on our own workspace?
Our own workspace reported itself as working, and the one gap it named was real: no pull requests had been opened, because GitHub is not connected there. A morning message that says that in four lines is more use than a dashboard nobody opens.
What would a nightly workflow read?
One stored Perplexity answer to “how to track AI search visibility”, 3 Oct: a prompt set, a cadence and a baseline, sources from Searchable, Ahrefs and Semrush, and no Attensira. A workflow can read answers like this every night and post them where the team looks.
Question: how to track AI search visibility
Perplexity answered: Track AI search visibility by defining a prompt set, selecting AI platforms, and measuring metrics like share of voice, visibility, mentions, sentiment, and citations across engines; use a cadence and baselining to compare over time.
Sources cited
- 1seocrawl.ai
- 2webfx.com
- 3maxaeo.ai
- 4searchable.com
- 5topify.ai
- 6seobility.net
- +4 more
Not namedAttensira is missing from this Perplexity answer.
Researcher · Stored the answerattensira.com stored Perplexity answer, read over the Attensira MCP · · 10 linksWhich workflows are worth scheduling?
- Morning health check.
get_loop_healthfor the last seven days, posted to
a channel. It says working, idle or blocked, and why.
- Monday numbers.
get_analytics area=visibility days=7, with an instruction
to report only changes marked real: true. Most weeks contain none, and a report that says so is doing its job.
- Approval nudge.
list_inbox view=triage, sent to whoever approves, when
anything has waited more than a few days.
Each is a read, and reads are free however often they run. Restrict the node's tool list to exactly these: an unattended agent with every tool can spend credits or delete a prompt because an instruction was ambiguous.
When is the REST API the better node?
When you know exactly which call you want, such as the same visibility read every Monday, an ordinary HTTP Request node against https://api.attensira.com/v1 is simpler to debug. Every REST endpoint has an MCP tool with the same payload, and both take the same key, so a workflow can move between them without a new credential.
Questions about n8n
Why use a key instead of OAuth in n8n?
Does the key end up in my exported workflow?
Which transport should the node use?
Should the key be read-only?
How does work from n8n show up in Attensira?
Does a scheduled read cost credits?
Where do these facts come from?
Attensira's connect documentation instructs n8n users to set the transport to HTTP Streamable and states that the server does not offer SSE.
docs.attensira.com · retrieved
“Set the endpoint to
https://mcp.attensira.com/mcpand the transport to HTTP Streamable — not SSE, which the server does not offer.”Attensira's connect documentation states that n8n credentials are encrypted at rest and are not written into the workflow JSON, so an exported or version-controlled workflow does not carry the key.
docs.attensira.com · retrieved
“n8n credentials are encrypted at rest and are not written into the workflow JSON, so an exported or version-controlled workflow does not carry the key.”
Attensira's connect documentation describes n8n as the case OAuth cannot serve, a workflow firing overnight with nobody to approve a browser prompt.
docs.attensira.com · retrieved
“This is exactly the case OAuth cannot serve: a workflow fires at 3am with nobody to approve a browser prompt.”
Put a morning visibility check on n8n's schedule and stop checking by hand.
7 days free · card requiredHow the trial works
Tell it where you want to be cited.
7 days free · card requiredHow the trial works
attensira.com's own workspace · read 4 Oct 2026 · n=4,518
197/ 4,518 answers4.4%