TinTinWorkflows
GitHubSign in

Cold email automation where you approve every word

Tin snapshots the shortlist recipients you selected and the exact email copy for approval. Then it sends from your mailbox inside your send window, and schedules follow-ups that stop when someone replies.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Email outreach campaign
outreach.email_campaign
outputSent campaign with a durable record in the project
guardrailHuman review. Nothing sends before you approve the recipients and the copy.
needsThe Gmail integration and a shortlist.
required inputssubject, body
optional inputsfollow_up_body, follow_up_delay_days, send_interval_seconds, daily_send_cap, send_window_start, send_window_end, send_timezone
sourcegithub.com/tin-computer/tin →

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. 01Snapshots the selected recipients and the exact subject, body and follow-up.
  2. 02Waits for your approval of that snapshot.
  3. 03Sends at your interval, daily cap, window and timezone.
  4. 04Runs reply-aware follow-up timers, so people who answered are left alone.
ask your agent

Set up a Tin email campaign to the shortlist. Draft the copy, then stop so I can approve it.

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 drafts from what the product really does and what changed this week, not from a template library.

All workflows →

Using something else for this?What it replaces, and what it does not.

Instantly alternativeOutreachlemlist alternativeOutreachApollo alternativeOutreach

Runs well with.Workflows that feed this one, or follow it.

Email outreach shortlistoutreach.email_shortlist

Questions.

Does it handle inbox warm-up or rotate sending domains?

No. It sends paced email from your own connected mailbox. Deliverability and warm-up tooling is planned, not shipped.

What happens when someone replies?

Their follow-up is cancelled. The timers are reply-aware.

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