Home/Platform/Open-Source AI Agents That Run Your Marketing

Marketing work that gets done every week

For teams exploring open-source AI agents, Tin supplies scheduled marketing workflows with memory and keeps each run's work as files in git. Our team sets up the system on your repository and data, adapts the jobs to your company and runs the weekly work.

Book a call

Schedule marketing from the coding agent
System view
Tin's System view: scheduled and available workflows for a project

What are open-source AI agents?

An AI agent uses a model to carry out a task in steps, calling tools as it works. Open source means the code is published under a licence that lets a team read, run and change it. When you choose an open source AI assistant, look at the jobs it is built to handle. For recurring marketing, those jobs need access to the company's data and a record of earlier work.

OpenHands serves software development; Flowise and Dify offer visual builders for agent apps. n8n combines automation with agent steps and supports self-hosting; Open WebUI provides a self-hosted chat interface. Tin supplies an open-source marketing system for coding agents, with the marketing jobs already written. For marketing, ask what it can do on the first run and whether the jobs that repeat keep a schedule and memory.

Writing each marketing job from scratch takes engineering time

Choosing a general agent framework leaves a marketing job to write: the instructions it follows, the accounts it reads and the checks on its output.

  • Job design consumes engineering time. Someone defines the steps, data inputs and checks that make a useful marketing draft.
  • Output needs continued tuning. Each recurring job needs attention to keep its instructions producing work the company can use.
  • Connections add maintenance work. The job needs access to Search Console, Google Ads, PostHog or the mailbox it works from.

Tin supplies written marketing workflows with these parts, used on our own products.

Each job keeps its schedule and its memory

Save a recurring job with its inputs. Tin handles when it runs and keeps the files it produces for later jobs to read.

Schedule the recurring work

A saved workflow includes the inputs and schedule for its job. Tin handles timers and retries around the run, so the job can repeat from that setup. Open the Week view to see how research, writing and measurement fit into the company's marketing week.

Set the next scheduled run
Week view
A week of a growth system in Tin: research, writing, checks, paid ads, email, review and measurement, day by day

Keep earlier work in memory

Research, reports and the project wiki stay in git as plain files. Project memory makes that context available to later runs. A job can read what came before, and the people working on the project can inspect those same files and their history.

Read the context behind each job
Project files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Feed the next week's work

Every Sunday, what moved becomes next week's plan. The weekly brief brings the response to the previous work into the project. The next planning run reads that brief when deciding which research, drafts and campaigns should follow.

Plan from the previous week's work
Week view
A week of a growth system in Tin: research, writing, checks, paid ads, email, review and measurement, day by day

Review what the job produced

A draft waits for the owner as a pull request or a one-click publish. The Decision card puts that choice beside the work produced. Read the draft against the project's research and earlier work. The available actions include publishing, opening a pull request or leaving it for later.

Run jobs from the agent

Tin is an MCP server available to Claude Code, Codex and Cursor. The coding agent reads the repository and fills the marketing job's inputs from that context. With the product code open, ask the agent to use Tin for the next audit, research task or draft.

Connect the agent to marketing jobs
Agent connection
Tin's System view: scheduled and available workflows for a project

Tin ships workflows for the jobs marketing repeats

Find organic opportunities

Run technical SEO and AI visibility audits, then prepare a keyword plan. Browse organic workflows

Write from company context

Draft articles in the owner's voice and refresh pages already in the project. Browse content workflows

Work through outreach

Prepare mailbox shortlists, paced email campaigns and replies to relevant community threads. Browse outreach workflows

Prepare listings and placements

Work on marketplace listings, awesome lists and newsletter placements for the company. Browse listing workflows

Read the weekly evidence

Read weekly briefs, PostHog analytics briefs and competitor watch before choosing the next tasks. Browse measurement workflows

  • Claude Code
  • Codex
  • Cursor
  • GitHub
  • Google Search Console
  • Google Workspace
  • PostHog
  • X

Founders, small teams or Tin's people run it

Use the coding agent already open on your project, share that project in the browser, or have our people run its marketing jobs.

Add marketing jobs to Codex
Hosted connection
Tin's System view: scheduled and available workflows for a project

Connect as a founder

Add the hosted Tin server to Codex, then ask the agent to run a marketing job for your product.

codex mcp add tin --url https://app.tin.computer/mcp
Open the team's research and drafts
Shared project files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Share the team project

Open the same projects at app.tin.computer, with the research and drafts in git available for the team to read.

Hand over the repeating work
Weekly marketing
A week of a growth system in Tin: research, writing, checks, paid ads, email, review and measurement, day by day

Have Tin run it

Our people connect the company's repo and data, adapt the workflows and take on the recurring marketing jobs.

You can read, fork and change every workflow

Read the code

Every workflow is text in the repo.

Run it on your machine

Your keys, your data, your schedule.

Change a workflow

Edit the file and send it back.

Keep the licensed source

Open source, Apache 2.0.

Talk to Tin

Let's discuss the recurring marketing work your engineers would like us to handle. We can set up Tin, adapt the jobs to your company and keep improving them. Your company keeps the code.

Book a call

FAQ

Do I need to write code to use it?

You can ask a coding agent to run Tin's jobs and open the same projects in the browser at app.tin.computer. The agent uses your repository to fill the job's inputs. Our people can also take on the setup and run the recurring marketing work for the company.

Can we add our own marketing jobs?

Yes. Bring your own skills. One command turns them into workflows. Add the existing marketing jobs your team has already developed for its buyers, keeping their instructions in the repository. They sit alongside jobs for research, drafts, outreach and measurement.

What happens when a scheduled run fails?

Tin handles retries around scheduled runs. The workflow keeps its saved inputs and schedule, while files already produced remain in the project repository. The team can read those files while investigating the failure, using the saved work to understand what happened and what to change.

How is it different from prompting a coding agent?

Tin adds the recurring job's data, schedule and project memory to the coding agent. It connects the mailbox and repository, keeps reports and drafts as files, and supplies the review steps around production. When the next draft or brief is due, its run reads the work already saved in the project.

Let Tin's team run your scheduled marketing jobs

Talk to the founders and engineers who would set up and run the system for your company. We can discuss the jobs that repeat in your marketing week and which ones to schedule first.

Book a call