Skip to content

Release launch posts published on approval

When you publish a release, it reads the project's code, separates what is built from what is only promised, and writes a launch article plus a post for every channel you turned on. The drafts arrive as one pull request, and merging it publishes each piece once.

MarketingWorks with Claude Code · n8n+1Community example
Build your promptSee requirements

What it does

  • Watches your public repo events for a new release and runs a preflight check for a license, README and demo
  • Reads the code and reports only implemented features as working
  • Writes the article in each language and a piece per channel within its limits
  • Opens a drafts pull request in your blog repo
  • Publishes each channel once after the merge and reads back visits and stars by channel

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Merging the drafts pull request, which publishes everything
  • Replying to comments under the posts

You decide what happens next.

More about this workflow

This setup is for marketers and solo creators who need steady output without losing their voice. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it watches your public repo events for a new release and runs a preflight check for a license, README and demo. Next, it reads the code and reports only implemented features as working. Then it writes the article in each language and a piece per channel within its limits. After that, it opens a drafts pull request in your blog repo. Finally, it publishes each channel once after the merge and reads back visits and stars by channel. It works with your git host, social APIs and email platform, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before merging the drafts pull request, which publishes everything and replying to comments under the posts, and says plainly if a step cannot be undone.

“Each channel is published once, never twice”
Jose Antonio Garrido yeyo11 on GitHub · Oct 24, 2026
Before you startGit host · Social APIs accessScoped permissionsClaude Code or n8n
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

  • Social APIs

    Handles the social apis part of this job. Grant read-only scopes for comments and mentions.

    API required: Yes. Each network needs its own developer app and keys to read comments and mentions.

    No sign-up needed

  • Email platform

    Handles the email platform part of this job. Grant draft access, no send or list export.

    API required: Optional. Your newsletter tool. An API helps, but the agent can also hand you a draft to paste.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Strong general writer at a mid price.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost for first drafts and digests.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

which ones are on and whether each needs approval

your blog's source

voice, languages, logo

2Your prompt

4 of 4 still empty
Fill these in before you run it: [CHANNELS: which ones are on and whether each needs approval] [LAUNCHES REPO: your blog's source] [BRAND FILE: voice, languages, logo] [DEMO ASSET PATH] You are the Release launch posts published on approval agent. When you publish a release, it reads the project's code, separates what is built from what is only promised, and writes a launch article plus a post for every channel you turned on. The drafts arrive as one pull request, and merging it publishes each piece once. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Watches your public repo events for a new release and runs a preflight check for a license, README and demo - Reads the code and reports only implemented features as working - Writes the article in each language and a piece per channel within its limits - Opens a drafts pull request in your blog repo - Publishes each channel once after the merge and reads back visits and stars by channel What you must never do without a yes from a person: - Merging the drafts pull request, which publishes everything - Replying to comments under the posts Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, n8n, Make

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  2. 2Set up Social APIs. Keep it to read-only scopes for comments and mentions.
  3. 3Set up Email platform. Keep it to draft access, no send or list export.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: merging the drafts pull request, which publishes everything, replying to comments under the posts.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Release launch posts published on approval](https://trustcase.dev/badge/release-launch-posts-published-on-approval.svg)](https://trustcase.dev/use-cases/release-launch-posts-published-on-approval)
HTML
<a href="https://trustcase.dev/use-cases/release-launch-posts-published-on-approval"><img src="https://trustcase.dev/badge/release-launch-posts-published-on-approval.svg" alt="Trustcase trust score for Release launch posts published on approval" height="20"></a>

More marketing workflows

Other workflows that use the same tools