TinTinWorkflows
GitHubSign in

Approved articles, delivered as a pull request

Tin adapts an approved article to the format and components your website repository already uses, then opens a pull request and leaves it unmerged. The Markdown original stays in Tin.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp

What the workflow does

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output. The steps below are what this one does, every time.

  1. 01Starts from an approved article run.
  2. 02Reads how your repository formats posts: front matter, components, image paths.
  3. 03Opens a reviewable pull request with the copy preserved.
  4. 04Saves a delivery receipt next to the original Markdown.
ask your agent

Deliver the article I just approved in Tin as a PR against our website repo.

workflow keycontent.deliver
required inputs
source_run_idexpected_repository
optional inputs
retry_run_iddirection
outputUnmerged GitHub PR and content/deliveries/{run_id}.md
needsThe GitHub integration, with the website repository selected.
guardrailNever merges. Approval of an article is not publication.

What every workflow here comes 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 works in that repository every day, so it can review the pull request against your own conventions before you look at it.

All workflows →

Questions

What if I do not use GitHub?

The approved Markdown stays in project Files, and you publish it however you like.

Does Tin rewrite the copy for the site?

No. It adapts the format and preserves the approved copy.

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

Run this once in your terminal. It connects Tin to your agent and opens the sign-in. Then ask your agent to grow your project.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp