CONTENT CREATION
Send tier-aware release emails based on which plan a feature ships to
On a published release, reads a plan-tier tag in the notes, generates email copy tailored to that audience, and routes the announcement only to customers on the matching plan tier.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- LogicRead plan-tier marker and select segment
- ActionGenerate tier-tailored email copyOpenAI
- OutputSend email to matching plan tierGmail
What it does
Not every release matters to every customer, and this workflow makes sure the right segment hears about it. When a GitHub release publishes, it parses a plan-tier marker in the notes (for example "tier: pro" or "tier: all"). A logic step uses that marker to decide the audience. OpenAI then writes an email tuned to that tier — emphasizing value framing relevant to Pro buyers, or a broad benefit message for an all-tiers change. The finished email is sent via Gmail to the matching segment only, so free users are not pitched a feature they cannot use and Pro customers do not get diluted blasts.
When to use it
Use it when your product gates features by plan and a single all-hands announcement either confuses free users or buries the upsell. It fits teams with clear plan tiers who want every release email to land with the audience that can actually act on it. Encoding the tier in the release notes keeps targeting decisions with engineering, where the gating already lives.
How it works
- 1A GitHub trigger fires when a release is published.
- 2A logic step reads the plan-tier marker from the notes and selects the target segment.
- 3OpenAI generates email copy framed for that specific tier's audience.
- 4Gmail sends the announcement only to customers on the matching plan tier.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GmailRead, draft, send, label.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
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.
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.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.