Get a weekly AI visibility digest that can say nothing happened

Ask your assistant to call list_automations, then create_automation on the Attensira MCP server with a weekly trigger, a time and an instruction that ignores changes not marked real. Creating it is free; each run spends credits. Run it once with run_automation and an idempotency key, then read get_automation before trusting it unattended.

7 days free · card requiredConnect your assistant

Claudeattensira · attensira.com

Asked: What automations do we already have before I add a weekly digest?

called list_automations

Two, and neither is a weekly digest. The crew's daily plan already runs every morning.

Daily win plan: daily, 06:00; active · last run 4 October, 06:01
Event responder: on 5 event types; a lost prompt or citation, a rival or page change, a new deciding source

The first step of the chain, because two automations doing one job bill twice.

attensira.com workspace, read over the Attensira MCP · 4 Oct 2026

Who does the work

Chief of staff · Would send it on Monday
Researcher · Stored the answer

Which call answers it?

Paste it into any client connected to the Attensira MCP server, or ask the question in your own words and your assistant picks the same call.

The call

{ "tool": "create_automation", "arguments": { "name": "Monday visibility digest", "instruction": "Summarise the last 7 days: workspace mention and citation rates with deltas, the five worst prompts, per-platform split, and any competitor whose rate moved with real:true. Ignore deltas where real is false.", "trigger": "weekly", "timezone": "Europe/London", "run_at_minute": 540 } }

What can’t this tell you?

A weekly cadence over a daily sampling floor means each report rests on at most seven readings per prompt per platform, or three times that on Growth and Business where sampling depth is three. That is thin for week-over-week comparison, and a digest that dutifully reports movement every week is reporting noise.
The digest reports what was measured, not what exists. A platform your plan does not track is never queried, so it comes back null rather than zero, and a report that renders null as 0% invents a failure that did not happen.
Creating an automation is free but every execution it triggers spends credits, on the schedule as well as on a manual run. The cost of a weekly digest is a recurring cost, and nothing in the create call tells you what it will be.

What is the chain behind it?

When one call is not enough, these are the calls that follow, in order, and why each one is there.

Call 01
Call list_automations before you create anything
list_automations takes no parameters and returns every automation in the workspace with its name, instruction, trigger, allowed tools, status, timezone, run_at_minute and last_run_at. Two automations doing the same job bill twice, and this is the one call that stops that happening.
Call 02
Create the automation and write the instruction precisely
create_automation needs a name, an instruction in plain language and a trigger of manual, once, daily or weekly. Creating costs nothing. Name the exact areas and windows you want in the instruction, and say explicitly that deltas where real is false should be ignored, or the digest will report noise as change.
Call 03
Pin when it fires, and narrow what it may call
run_at_minute is minutes past local midnight from 0 to 1439, so 540 is 09:00, and it is read in the IANA timezone you pass rather than UTC. The optional tools array is an allow-list of tool names the automation may use; omit it to allow everything the plan includes.
Call 04
Trigger it once with an idempotency_key, then read the history
run_automation fires it immediately outside its trigger, spends credits and returns a session handle to poll with get_session rather than a finished result. Pass an idempotency_key on every call so a retry does not bill twice. get_automation then returns the full definition with the most recent run inline as latest_run.

What would this week's digest have said?

A digest is three or four numbers with their n, not a dashboard. These are the last seven days on our own workspace: how often answers cited us, overall and on ChatGPT, and how often they named us.

answers that cited attensira.com: 147 of 2,088; n=2,088 answers
ChatGPT answers that cited us: 94 of 1,098; n=1,098 answers
answers that named us: 125 of 2,088; n=2,088 answers

Chief of staff · Would send it on Mondayattensira.com workspace, read over the Attensira MCP on 4 Oct 2026 · ChatGPT and Perplexity · 27 Sep 2026 to 4 Oct 2026

What did it show on our own workspace?

Our own workspace already ran a daily plan and an event responder, but no weekly digest. That is why the chain starts with list_automations: the job you are about to create may already be done, or done differently, by something that bills on every run. A workspace that has been running for a year usually has one nobody remembers creating.

How do I read what comes back?

The digest reports every delta as a change: The instruction did not exclude real:false. A delta with real:false failed a two-proportion z-test at 95%, so there is no change to report in either direction.
A week with no findings: Normal, and the correct output. Most weeks contain no statistically real movement.
Numbers that differ from the dashboard: Check the window. Seven days against a 30-day default is a different slice, not a bug.
A run missing from latest_run and the history: The scheduled run did not execute. Re-run it manually with a fresh idempotency key rather than assuming the week was quiet.

What sits behind the week's numbers?

Rates say how often; answers say what was said. This Perplexity answer from 3 Oct to “why am I not showing up in ChatGPT” credits outside mentions and cites Reddit beside nine vendor posts. An automation can read answers like it every week.

Answer · Perplexityasked 3 Oct 2026

Question: why am I not showing up in ChatGPT

Perplexity answered: If you’re not appearing in ChatGPT, it’s usually because the model has no independent references to you beyond your own site. Ensure you have credible external mentions (publications, reviews, community posts) that AI systems can cite.

Sources cited

1usetidepool.com
2reddit.com
3networksolutions.com
4remwebsolutions.com
5ai-dband.com
6scorivra.com
+4 more

Not namedAttensira is missing from this Perplexity answer.

Researcher · Stored the answerattensira.com stored Perplexity answer, read over the Attensira MCP · 4 Oct 2026 · 10 links

Why should the instruction be allowed to say nothing?

A delta comes back as {value, real}, and real: false means the movement did not clear a two-proportion z-test at 95%: there is no change you can prove, in either direction. An instruction that does not exclude those finds something every week, which is exactly what a digest should not do. A week with no findings is the correct output most weeks; a digest that never produces one is broken.

Why narrow the tools a scheduled job may call?

The optional tools array is an allow-list. Omit it and the automation may use everything your plan includes. A digest has no business calling remove_prompt, and a scheduled job runs when nobody is watching. Name the read tools it needs and nothing else.

When the digest flags something, the manual chain that finds the cause is where you lost ground this week. If it names a rival, read whether they are actually gaining before reacting.

Questions about a scheduled visibility digest

Does creating an automation cost credits?

No. create_automation is free and needs write access: any signed-in connection, or a read-and-write key. Every run it triggers spends credits, whether that run came from the schedule or from a manual run_automation call.

What is the idempotency_key for?

It maps to the Idempotency-Key header upstream, so a retried or duplicated run_automation call does not produce a second billed run. Pass one on every call.

How do I stop the digest reporting movement that is not real?

Say so in the instruction. A delta comes back as value and real, and real:false means the change did not clear a two-proportion z-test at 95%. An instruction that does not exclude those will summarise noise every week.

When exactly does a weekly automation fire?

At run_at_minute minutes past local midnight in the timezone you passed — 540 is 09:00 — with UTC as the default when you pass no timezone. run_at_minute is only meaningful for daily and weekly triggers; manual and once never fire on a clock.

How do I check it actually ran without waiting a week?

Call run_automation once with a fresh idempotency key to trigger it now, then get_automation, which returns the definition with its most recent run inline as latest_run. That is one call rather than two.

Where do these facts come from?

Attensira's MCP tool reference states that creating an automation costs nothing and every run it triggers spends credits.
docs.attensira.com · retrieved 2026-10-04
“Creating costs nothing; each run it triggers does.”
Attensira's MCP tool reference states that run_automation's idempotency_key is sent as the Idempotency-Key header, so a retried call does not bill a second run.
docs.attensira.com · retrieved 2026-10-04
“It maps to the Idempotency-Key header upstream, so a retried or duplicated call does not produce a second billed run.”

Where to go next

Get a weekly digest, including the weeks nothing moved.