CONTENT CREATION
Turn a published GitHub release into blog, in-app, and email copy
When you publish a GitHub release, this workflow rewrites the raw release notes into three tailored versions — a long-form blog post, a short in-app announcement.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- ActionRewrite notes into blog, in-app, and email draftsOpenAI
- ActionCreate blog post in Notion changelogNotion
- ActionPost in-app announcement to SlackSlack
- OutputDraft customer email in GmailGmail
What it does
The moment you publish a release on GitHub, this workflow grabs the tag, title, and full release-note body and turns one set of engineering notes into three audience-specific drafts. OpenAI rewrites the same changes three ways: a structured blog post with a narrative intro and feature sections, a tight in-app announcement card under 280 characters, and a warm customer email with a clear subject line. The blog post is created as a Notion page, the in-app blurb is posted to a Slack channel for the product team to paste, and the email lands as a Gmail draft ready for review.
When to use it
Use it when shipping is fast but the announcement pipeline lags — engineering merges and tags, then nobody finds time to translate the changelog for non-technical readers. It fits teams that publish formal GitHub releases and want consistent multi-channel copy without writing each version by hand. Drafts, not auto-sends, so a human still approves voice before anything reaches customers.
How it works
- 1A GitHub trigger fires when a release is published, passing the tag, name, and body.
- 2OpenAI receives the release notes and a brand-voice prompt, returning three distinct drafts keyed by channel.
- 3The blog version is written to a new Notion page in your changelog database.
- 4The in-app announcement is posted to a Slack channel for the product team.
- 5The customer email is created as a Gmail draft, left unsent for review.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect GmailRead, draft, send, label.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
Full multi-format snippet pack from one episode
An agent takes a published episode and produces a complete repurposing pack: quote cards, show notes, audiogram scripts, and a thread, organized into a Notion hub page.
Guest recap email draft after episode publish
When an episode publishes, transcribe it, draft a personalized thank-you email to the guest with their best quotes and shareable links, and queue it as a Gmail draft.
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Audiogram script and clip-timestamp builder
From a transcript dropped in Drive, pick three viral-worthy 30-to-60-second segments, write captions and hook text, and post the clip plan to Slack for editors.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
Podcast episode to branded quote cards
When a new episode audio file lands in Drive, transcribe it, pull the five most quotable lines, and generate branded quote-card images ready to post.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.