ThreadPage
Start writing

All use cases

A morning metrics report your script writes

At 06:00 your script adds the night’s numbers as a table with a chart. When one looks wrong, the team explains it right under the note, and the explanation stays with the number.

Start free trial

14 days of Pro. No card needed. Ends automatically. Choose to continue with Pro for $99.99 a year ($8.33 a month). See monthly pricing

Start writing
See plansSee the thread

At a glance

For
Data engineers and analysts with a nightly job, and the team that reads its numbers.
You keep
A Metrics folder with a Daily metrics thread, shared with the team at Can add notes.
Files itself
  • Every morning, a note from your script: the metrics table and a chart.
  • The team’s explanations, under the number they explain.
The moment
On Monday @Claude reads last week’s notes and says what moved besides the outage: paid conversions down 4%, sign-ups flat.
Plan
Pro The owner needs Pro with Sync for this script and shared-thread workflow. People can join a shared thread on Free or Plus with the access the owner grants.

Before

The nightly job writes its numbers to a table nobody opens. When a number jumps, three people investigate it in three places, and the explanation lives in a chat thread. Two months later the same spike shows up, and nobody remembers it was the payment provider.

Why a thread, not a dashboard and a chat

  1. The number and its reason

    Ken explains the spike in the next note, and the reason stays with the number.

  2. Two calls

    At the end of the job, one call adds a note with a Markdown table; another uploads the chart.

  3. A model reads the week

    Write to @Claude on your own key, or let Claude Code or Codex read the thread while you debug the job.

A thread, over time Example

Your workspace starts empty.

Metrics

Daily metrics

ActiveSharedKen

  1. Mon 26 Oct

    1. Every morning, the night’s numbers as a table.

      via Metrics script06:02

      Daily metrics · 25 October

      MetricYesterdayA week before
      Sign-ups1,2041,169
      Paid conversions6162
      Checkout errors1412

  2. Tue 27 Oct

    1. A number that looks wrong.

      via Metrics script06:02

      Daily metrics · 26 October

      MetricYesterdayA week before
      Sign-ups1,1871,150
      Paid conversions5860
      Checkout errors21213

    2. The explanation, right under it.

      Ken08:40New

      The 212 errors are the payment provider’s outage, 01:00 to 03:00. Their status page confirms it.

  3. Mon 2 Nov

    1. On Monday, one question on your own Anthropic key.

      You09:15

      To @ClaudeReplied in 1 min

      @Claude compare last week’s notes with the week before. Anything besides the outage?

    2. Its answer is a note the team reads too.

      From @Claude09:16

      Besides the outage on 26 October, paid conversions are down 4% on the week. Sign-ups are flat.

It files itself. You read.

Your tools write into the threads you choose, with only the access you give them.

Script or API

  • The night’s numbers, from your script

    Two calls at the end of your job: one uploads the chart, one adds the note with a Markdown table.

    Set it up

    AutomationAdd onlyDaily metrics

    1. In Settings → Connections → Automations, choose Connect an automation → Script or API with Add only for the Daily metrics thread: it can add notes there and can’t read or change any.
    2. At the end of the job, upload the chart as an image and add a note whose Markdown holds the table and the image. Notes in the developer reference shows both calls.

  • Ask about the week

    Write to @Claude or @GPT in the thread. It reads the week’s notes and answers with a note, on your own API key.

    Set it up

    AI modelYour Anthropic or OpenAI API keyPro with Sync

    1. In Settings → Connections, open AI models, choose Claude or GPT, paste an API key from Anthropic or OpenAI and choose Connect. AI models need Pro with Sync turned on.
    2. In the thread, write @Claude and your question, then choose Send. In a thread you share, choose Allow here the first time.

Also

Debugging the job? Claude Code or Codex can read the thread when you connect it with access to Metrics (see Coding agents help), and tell you when a number last moved like this.

Limits

  • Charts arrive as images your script makes: there are no live charts or dashboards.
  • Tables have no formulas: your script computes the numbers.
  • @Claude needs an API key from Anthropic, and the provider bills the key for every answer. In a thread you share, it answers only after you choose Allow here.
  • Notes aren’t end-to-end encrypted: keep customer data out of the report.

Claude, GPT, Claude Code, Codex, Anthropic, and OpenAI are the names of their owners. ThreadPage is independent and not affiliated with or endorsed by them.

Start with one thread.

Start free trial

14 days of Pro. No card needed. Ends automatically. Choose to continue with Pro for $99.99 a year ($8.33 a month). See monthly pricing

Start writing
See plans

More use cases

  • Every ad hoc request, with its query and answer

    The question, the SQL in a code block, the table and the chart, and what was decided. When the same question comes back in March, Search finds the query.

    Free nothing to set up

  • A lab notebook your script fills in

    Every run arrives with its parameters, table and plot. Your chapters link to the run behind each claim.

    Pro results from a script
All use cases