ThreadPage
Start writing

All 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.

Start writing

Free in your browser. No account needed to start.

See the thread

At a glance

For
Data analysts and anyone who answers questions with queries.
You keep
An Analytics requests folder with a thread per question.
Nothing to set up
  • The question, your query and its result, added as notes.
  • With Pro, connected tools can add questions or results when you configure them.
The moment
In March the same question comes back. A search for #signups finds the October thread: the query, the table, the chart and the reason.
Plan
Free Start free in this browser. Plus adds Sync across your own devices. Optional connections and hosting shared threads need Pro with Sync.

Before

Lena asks in Slack why trial sign-ups dropped. You write the query, paste a chart into the channel and answer in three lines. In March the board asks the same question about a different week, and the query lives in a notebook you can’t find, under a name like untitled-14.

Why a thread, not the chat and a notebook

  1. The query sits with its answer

    The SQL in a code block, the table it returned, the chart and the decision, in one thread per question.

  2. Keep the result with the query

    Paste the query and add its result table to the same thread. With Pro, a connected coding agent can add them when you ask.

  3. Found again in March

    Tag the thread’s notes, and Search finds the query by its words, months later.

A thread, over time Example

Your workspace starts empty.

Analytics requests

Why did trial sign-ups drop in week 41?

Done

  1. Mon 12 Oct

    1. The question, copied into a thread for the request.

      You10:15

      Why did trial sign-ups drop last week? The board meets on Thursday.

    2. The query in a code block, kept beside its result.

      You11:40

      Daily trial sign-ups since 28 September:

      SELECT date_trunc('day', created_at) AS day,
       count(*) FILTER (WHERE plan = 'trial') AS trials
FROM signups
WHERE created_at >= '2026-09-28'
GROUP BY 1 ORDER BY 1;

    3. The result and what it shows.

      You11:52

      DayTrials
      5 Oct412
      6 Oct398
      7 Oct151
      8 Oct162

      The drop starts on 7 October. Did anything ship that day?

    4. Waiting on the web team, and the note says why. Waiting

      You12:05

      Sent Lena the chart. Asked the web team whether the form changed on 7 October.

  2. Tue 13 Oct

    1. You09:30

      Lena confirmed with the web team: the new form hid the trial option on phones. Fixed this morning.

    2. The answer, tagged, for the next time someone asks. Done

      You09:45

      Answer: the form change on 7 October hid the trial on phones. Fixed on 13 October. #signups

If you like, let it file itself.

None of this is needed to start. It takes a few minutes once, and needs Pro.

Script or API

  • Questions from Slack

    A message that mentions your Slack app becomes a note in Requests. Start a thread for each question from there.

    Set it up

    AutomationAdd notes from another appSlack messages

    1. Create a Slack app, subscribe it to the app_mention event only, install it in your workspace and invite it to the channels you use.
    2. In Settings → Connections → Automations, choose Connect an automation → Add notes from another app. Name it Slack, choose Requests and Slack messages, and add the app’s signing secret.
    3. Paste the URL as the app’s Request URL in Event Subscriptions.

  • The query, filed by your agent

    Claude Code or Codex adds the query and its result as a note in the request’s thread.

    Set it up

    Coding agentRead and addSelected folders and threads: Analytics requests

    1. Connect Claude Code or Codex in Settings → Connections → Coding agents (see Coding agents help). After it connects, open it in Settings → Connections, choose Manage access → Selected folders and threads → Analytics requests.
    2. When the query works, ask: Add this query and its result table to the thread about trial sign-ups.

  • Ask what was answered

    In a thread only you see, write to @GPT or @Claude. It searches your past requests and answers with a note, on your own API key.

    Set it up

    AI modelYour OpenAI or Anthropic 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 @GPT and your question, then choose Send.

Limits

  • ThreadPage doesn’t connect to your database: a query and its result are what you or your agent add.
  • Charts arrive as images, and tables have no formulas: compute in your notebook or database.
  • @GPT needs an API key from OpenAI, 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 and credentials out of them.

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

Start with one thread.

Start writing

Free in your browser. No account needed to start.

More 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.

    Pro a script and @Claude

  • A research report you’ll need again

    ChatGPT or Claude can save a report alongside your own notes. Keep the decisions and follow-ups with it, then ask a connected model about the thread when you need to.

    Pro connected apps; your key for @ replies
All use cases