TinTinWorkflows
GitHubSign in

A PostHog brief you can check, number by number

Tin reads one PostHog project and writes a brief: activation in order, event trends, traffic, error signals and a breakdown the data can support. Every number comes with the query behind it, and team and test traffic can be left out.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Product analytics brief
product.analytics_brief
outputreports/analytics/{run_id}.md
guardrailRead-only, bounded queries in one PostHog project. Nothing is sent outside Tin.
needsThe PostHog connection, with one project selected.
required inputsnone
optional inputsreporting_days, as_of_utc, event_mapping, exclusions, website_hosts, exclude_email_domains, internal_flag_property

What the workflow does.The same steps, every run.

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output.

  1. 01Reads events, properties and definitions from the PostHog project you connected.
  2. 02Orders the activation funnel, using your event meanings when you give them.
  3. 03Measures trends, traffic and error signals over the reporting window, without your team's own traffic.
  4. 04Writes the brief with reproducible evidence, and says so when a run measured nothing.
ask your agent

Set up a weekly PostHog brief for our product, and leave out everyone on our company email domain.

What every workflowcomes with.

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

Your agent knows which events the code fires and what they mean, so it can fill the event mapping instead of leaving the brief to guess.

All workflows →

Questions.

Does it work with self-hosted PostHog?

Not today. It supports PostHog Cloud in the US and EU.

How often can it run?

On demand, daily or weekly.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent.It takes one command.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp