By · Founder, Stacktree · Last updated
workflow

Have your agent tell you each morning who opened what you sent.

A scheduled prompt that asks Stacktree every morning what happened since the last check and posts one report in your chat: which pages were opened, who opened them through the link you made for them, what comments, approvals and change requests came in, and which pages nobody has opened yet. It uses one read call, whats_new, so nothing on your account changes and nobody is contacted.

Get started free

No card · 3 pages free · about a minute

How do I get a daily report of who opened the links I sent?

Connect your agent to Stacktree, then schedule a prompt that calls whats_new each morning and posts what happened since the last check. Opens through a link you made for one person come back with that person's name, comments come back quoted, and approvals, change requests and pages nobody has opened yet are listed too. Names and open counts need Solo ($19 a month); the rest works on every plan.

Why a scheduled read

Grok Bot routines, Claude scheduled tasks and ChatGPT scheduled tasks all run a saved prompt on a timer and put the result where you read it. Stacktree can also push each open as it happens: a webhook under Settings, Webhooks fires on a page's first open, on each named link's first open (Solo and up) and on a page still unopened 1, 24 or 72 hours after publishing, and it is set up the same way as the client comments workflow. A morning read does a different job: one summary of who opened what and what they said, once a day, which is enough to know who to follow up with before the day starts. Every call the report makes exists today, and none of them writes anything.

Typical flow

  1. Once: connect Stacktree to the agent at https://api.stacktr.ee/mcp and sign in.
  2. When you send a page, give each person their own link with their name on it, so their opens come back under that name.
  3. Paste the prompt for your agent (below) and let it set the schedule.
  4. Each morning it calls whats_new, passing the checked_at from its last run as since, or nothing, which means the last 24 hours.
  5. One report lands in your chat, grouped by page, or one line saying nothing changed.

A report reads like this:

Acme Q3 report
  Megan Hanning opened it (2 people have in the last 30 days).
  New comment: "Can we split paid social by platform?"
  Tom Reid approved it.

Globex proposal
  Dana Whitfield has not opened it yet.

What the agent reads

  • whats_new returns what happened on your pages since the time it is given, newest first, for up to seven days: opens, new comments and notes, approvals and change requests, form responses, a reader's own AI reading a page, and pages nobody has opened an hour after they went up. Each item has said, one sentence the agent can pass on as it stands, and next, the tool that follows it up. The answer also carries checked_at: passed back as since on the next run, nothing repeats. It reads only, and it leaves the unread count in your dashboard as it was.
  • The longer read. whats_new is served by the connector at https://api.stacktr.ee/mcp, not by the stdio package (npx stacktree-mcp). There, three calls do the same job: list_sites for every page (opened on every plan, and on Solo and up unique_viewers and last_viewed_at), list_share_links for each named link's opens and last_opened_at, and list_feedback for the words of each comment.
  • No account. A page published with no account has no connector to ask. Its claim_token reads its own activity: GET /sites/{id}/activity with Authorization: Claim <claim_token> says whether it was opened and when, its open comments, when it expires, and a one-line summary.

Viewer numbers cover the last 30 days, and Stacktree leaves out crawlers and email link scanners when it counts an open, so a mail filter checking the link does not read as your client opening it.

A share link opens without the page's passcode. If the reader should still type the passcode, give them a ?to= link instead, which is what whos_it_for returns: it keeps the passcode or email gate in front of the page and still records their name.

Which plan the report needs

Comments, approvals and change requests, and pages nobody has opened yet come back on every plan, Free included. Names and open counts are viewer numbers, which start on Solo at $19 a month. On Free, whats_new says that someone opened a page, with no name and no count. Studio, at $79 a month, adds time on page and scroll depth per person over REST; the prompts here do not use them.

The prompts, one per agent

Each prompt asks for the same report. Change the time, and keep the sentence that starts "Only read": it is what stops a scheduled agent from doing more than reading. Stacktree's sign-in asks to read your pages and to publish and change them, because the same connection publishes from chat; the prompts only use calls that read.

Grok Bot

Connect once. Grok Bot adds custom MCP connectors when you ask in chat; send it this:

Add Stacktree as a custom MCP connector for my account: a remote HTTPS server at https://api.stacktr.ee/mcp that signs in with OAuth, so leave the HTTP headers empty.

Approve the card it shows, choose Authorize, then Allow on Stacktree's sign-in page. The card then shows Stacktree as added. Connectors are account-wide, so every bot on the account can use it.

One snag: the Grok Bot desktop app finishes the sign-in at http://localhost:8787/callback. If another program is using port 8787 (Cloudflare's wrangler dev does by default), the sign-in ends on a "not found" page. Stop that program, then reload the tab or choose Reopen on the card.

Then ask the bot that should own the job for a page that refreshes each morning:

Make a page called Client pages, shared with only me. Fill it from Stacktree's whats_new tool, passing the checked_at from the last run as since (leave since out the first time). Group by page: who opened it, by name where Stacktree gives one, each new comment quoted, approvals and change requests, and pages nobody has opened yet. If nothing happened, say only: Nothing new since yesterday. Only read from Stacktree: never publish, update, resolve, revoke or send anything. If Stacktree is unavailable, say so on the page instead of using old data. Update this every morning.

Grok Bot pages, and a routine that refreshes one when you say "Update this every…", arrived on 21 October 2026. We have made Grok Bot pages, but we have not watched a routine refresh one, so check the page after its first morning. To get the report in the chat instead, ask for a routine: "Every day at 8:00 AM, post in this conversation" with the same instructions. Routines use the time zone in Grok Bot's settings and keep running with your laptop closed. Use Test run once before you rely on it.

Claude

Add the connector under Customize > Connectors, then Add custom connector, with the URL https://api.stacktr.ee/mcp, and sign in (step by step). Scheduled tasks are on Claude's paid plans. In a chat, describe the task and how often it runs:

Every day at 8 AM, check my Stacktree pages with the Stacktree connector's whats_new tool and report what happened in the last 24 hours. Group by page: who opened it, by name where Stacktree gives one, each new comment quoted, approvals and change requests, and pages nobody has opened yet. If nothing happened, reply only: Nothing new since yesterday. Only read: never publish, update, resolve, revoke or send anything.

Claude proposes a name, schedule and instructions; choose Schedule. Each run is its own session under Scheduled, and runs happen in the cloud while your computer is asleep. Each run starts fresh, so the prompt asks for the last 24 hours rather than passing since. We have not tested Stacktree in Claude Duet.

ChatGPT

ChatGPT creates a scheduled task when you ask for one in a chat, and tells you about each run by push or email, set under Settings > Notifications. Reaching Stacktree is the open question. Stacktree is not in ChatGPT's app directory yet, so you add https://api.stacktr.ee/mcp as a custom app in developer mode, which OpenAI documents for Business, Enterprise and Edu workspaces, and for Pro with read and fetch tools only. That is enough here, because the report only reads.

Every day at 8 AM, use the Stacktree app's whats_new tool to check my pages and report what happened in the last 24 hours. Group by page: who opened it, by name where Stacktree gives one, each new comment quoted, approvals and change requests, and pages nobody has opened yet. If nothing happened, reply only: Nothing new since yesterday. Only read: never publish, update, resolve, revoke or send anything.

OpenAI's tasks article says a task can use apps that are available to your account. It does not say whether that includes a developer-mode app, so run the prompt once by hand, then check that the first scheduled run reached Stacktree.

Poke

Add Stacktree as a Poke integration with the prefilled link, which signs in with OAuth. Then text Poke:

Every morning at 8, use Stacktree's whats_new tool and text me what happened on my pages in the last 24 hours: who opened what, by name where Stacktree gives one, new comments quoted, approvals and change requests, and pages nobody has opened yet. If nothing happened, text: Nothing new since yesterday. Only read: never publish, update, resolve, revoke or send anything.

Untested: we have not run Stacktree in Poke, and we have not checked that Poke repeats a request like this on a schedule. Look for the first morning's message before you rely on it.

OpenClaw and Hermes

Both agents can run a job on a schedule, and both can run curl. With a Stacktree API key from app.stacktr.ee/api-keys in STACKTREE_API_KEY, one request is the whole check:

curl -sS -X POST https://api.stacktr.ee/mcp \
  -H "Authorization: Bearer $STACKTREE_API_KEY" \
  -H 'accept: application/json, text/event-stream' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whats_new","arguments":{"since":"LAST_CHECKED_AT"}}}'

A page published with no account is read with its own token instead:

curl -sS https://api.stacktr.ee/sites/PAGE_ID/activity \
  -H "Authorization: Claim CLAIM_TOKEN"

Then ask the agent to schedule it:

Every morning at 8, run the Stacktree check-in. Call Stacktree's whats_new tool with curl (a JSON-RPC tools/call POST to https://api.stacktr.ee/mcp with Authorization: Bearer $STACKTREE_API_KEY), passing the checked_at you saved last time as since (leave it out the first time), save the new checked_at, and send me each item's said line, grouped by page. For each page you published with no account, read its activity with its claim token and send me its summary. If nothing happened, send: Nothing new since yesterday. Only read: never publish, update, delete or send anything else.

Hermes can also use the connector directly (hermes mcp add stacktree --url https://api.stacktr.ee/mcp --auth oauth), and then the prompt for any MCP client below works as it is. On 21 October 2026 a Hermes Agent signed in that way and called whats_new, which answered. We have not run either agent's scheduler with these prompts yet.

Any MCP client

Point the client at https://api.stacktr.ee/mcp. It signs in with OAuth; a client that cannot can send an API key from app.stacktr.ee/api-keys as Authorization: Bearer stk_live_…. Run this from whatever starts your agent on a timer:

Check my Stacktree pages with whats_new, passing the checked_at from your last run as since (leave it out the first time), and save the new checked_at. Report what happened, grouped by page: who opened it, by name where Stacktree gives one, each new comment quoted, approvals and change requests, and pages nobody has opened yet. If nothing happened, reply only: Nothing new since the last check. Only read: never publish, update, resolve, revoke or send anything.

Without an agent: the REST calls

Each MCP call is a REST route, so a cron job can build the same report with an API key:

curl -H "Authorization: Bearer $STACKTREE_KEY" https://api.stacktr.ee/sites
curl -H "Authorization: Bearer $STACKTREE_KEY" https://api.stacktr.ee/sites/SITE_ID/recipients
curl -H "Authorization: Bearer $STACKTREE_KEY" https://api.stacktr.ee/sites/SITE_ID/feedback

GET /sites is list_sites, GET /sites/{id}/share-tokens is list_share_links and GET /sites/{id}/feedback is list_feedback. For names, GET /sites/{id}/recipients goes further than any MCP call: it rolls up opens per person from share links and from ?to= links, with opens, first_seen and last_seen for each, and viewers, where a figure above 1 means the link was passed on. It also returns sent_to, the people you said the page was for, on every plan, which is how a script can list who has not opened it yet. On Studio and Firm each person also carries active_seconds and max_scroll. The schemas are in the spec at api.stacktr.ee/openapi.json.

What we tested

On 2 October 2026 we connected a Grok Bot to Stacktree with the message above. After Allow on Stacktree's sign-in page the bot reported the connector ready, published a test page and made a named link for it. Asked for a read-only version of the earlier three-call report, it called list_sites and then list_share_links on each opened page, and listed the opened pages with their open comment counts. On 21 October 2026 a Hermes Agent called whats_new over the connector. We have not yet watched any of these prompts fire on a schedule, in Grok Bot, Claude, ChatGPT, Poke, OpenClaw or Hermes, so read your first report next to the page screens in your dashboard, and tell us if they disagree.

FAQ

Frequent questions

How does the report know who opened a page? +
From links with a name on them. When you say who a page is for (the whos_it_for tool, or the dashboard's send box), that person gets a ?to=Name link, and a share link made with create_share_link carries the name you give it. Opens through either come back from whats_new under that name, and a named person who has not opened theirs comes back as not opened yet. Opens through the plain page link are counted but not named.
Which Stacktree plan does the report need? +
Solo, at $19 a month, for the whole report. Names and open counts are viewer numbers, and those start on Solo: on Free, whats_new says someone opened a page, with no name and no count. Comments, approvals and change requests, and pages nobody has opened yet come back on every plan, Free included. Studio, at $79 a month, adds time on page and scroll depth per person, which the REST recipients call returns and these prompts do not use.
Can the scheduled agent change or send anything? +
The prompts keep it to calls that only read (whats_new, or the activity read for a page published with no account), and tell it never to publish, update, resolve, revoke or send. The connection itself can do more: Stacktree's sign-in asks to read your pages and to publish and change them, because the same connector publishes from chat. If your agent can ask before write actions, leave that on.
Does Stacktree not already tell me when someone opens a page? +
By email, yes: when a page is first opened, the first time each named person opens it on Solo and up, and in a daily email when your pages have had activity. Webhooks cover opens too. Under Settings, Webhooks, Stacktree can call your URL, or post to a Slack or Discord channel, the moment a page is first opened, the first time each named link is opened (Solo and up), and when nobody has opened a page 1, 24 or 72 hours after you published it. The same webhooks carry client comments, set up as in send client comments to Slack, Linear or GitHub. This prompt does a different job: one read each morning that puts the opens and the comments together in the chat you already use, where you can ask a follow-up question.
Keep reading

Related guides

References

Sources and further reading

Give each person their own link, then let your agent read the opens.

Comments, approvals and unopened pages work on every plan. Names and open counts start on Solo at $19 a month.

Sign up free →