An n8n alternative when the job is marketing, not plumbing
n8n is a general automation builder: you design the workflow. Tin ships the marketing workflows already built and tested, and your coding agent runs them with the context it already has.
codex mcp add tin --url https://app.tin.computer/mcpWhat Tin does in place of n8n
n8n is a source-available workflow automation platform with a visual node editor, hundreds of integrations and self-hosting.
| the job | how Tin does it | workflow |
|---|---|---|
| A hand-built SEO content pipeline | Audit, keywords, plan and draft in one workflow. | organic.traffic_system → |
| A hand-built outreach flow | Approved campaign with reply-aware follow-ups. | outreach.email_campaign → |
| Scheduled reporting | A weekly brief from real project activity. | project.weekly_brief → |
| Anything else | An isolated one-off task with a transcript. | project.task → |
What Tin does not replace
Tin is not a clone. Here is where each one fits.
n8n still does this better
- General-purpose automation between arbitrary apps.
- A visual node editor. Tin workflows are code and prompts in a repository.
Choose Tin when
You want marketing outcomes and would rather not design, debug and maintain the graph.
Stay with n8n when
You are automating operations across many apps and want to build it yourself.
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
Tin connects to Claude Code, Codex or Cursor over MCP. That agent has your repository open and knows your product, customers and voice, so it fills the inputs and reviews the output. You never brief a new tool from zero.
All workflows →The workflows behind this page
Each one is a folder in the repo. Open a page for its steps, inputs and output.
Questions
Can I build my own workflows in Tin?
Yes. A workflow is plain Python, Python with managed model calls, or an agent procedure, packaged with a manifest of typed inputs and outputs. You can contribute it back with a pull request.
Is Tin a node-based builder?
No, deliberately. Workflows are bounded jobs with declared inputs and outputs, which is what makes them testable.
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.