TinTinWorkflows
GitHubSign in

One Google Search campaign, built from the assessment and approved by you

Tin turns the campaign shape from your paid ads assessment into one Search campaign in your own Google Ads account. It drafts the exact plan, waits for your approval, and only then creates it.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Google Ads launch
ads.launch
outputA live Google Search campaign, with its plan saved under ads/google in project Files
guardrailHuman review. Nothing reaches Google Ads before you approve the exact plan. Never broad match keywords.
needsA successful paid ads assessment and the Google Ads connection: you enter your customer ID and accept Tin's manager invitation in Google Ads.
required inputsnone
optional inputsassessment_run_id, daily_budget_usd, cpc_ceiling_usd, landing_page_url, campaign_name, notes, max_cost_usd

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. 01Checks the account first: the manager link, billing, a conversion action that records data and the landing page.
  2. 02When conversions are not tracked yet, offers a tracking setup instead, including a pull request that adds the site tag when GitHub is connected.
  3. 03Drafts the plan: ad groups with exact and phrase keywords, headlines and descriptions, sitelinks, negatives, budget and click ceiling.
  4. 04After you approve the exact plan, creates the campaign in one validated request.
ask your agent

Launch the Google Search campaign from our latest Tin ads assessment with a $30 daily budget, and show me the plan first.

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 can check the landing page and the conversion event in the code before the campaign spends a dollar on them.

All workflows →

Questions.

Does Tin hold my Google login?

No. You link your account to Tin's manager account by accepting an invitation inside Google Ads. Tin stores no Google credential of yours.

What if I have no conversion tracking?

That blocks the launch. Tin sets up tracking for your approval instead, and you run the launch again once conversions record.

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