CONTENT CREATION

Customer-Facing Release Email from Shipped Features

On a GitLab milestone close, drafts a customer-friendly product update email from MRs labeled customer-facing.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab milestone closedGitLabGitLab
  • ActionFetch milestone MRs and labelsGitLabGitLab
  • LogicKeep only customer-facing MRs
  • ActionRewrite as benefit-led email copyOpenAI
  • OutputCreate Gmail draft for reviewGmailGmail

What it does

Generates a customer product-update email from a closed GitLab milestone, but only from the changes customers actually care about. It reads the milestone's merged MRs, keeps the ones labeled customer-facing, rewrites them into benefit-led prose, and creates a Gmail draft addressed to your announcement list.

When to use it

When engineering milestones don't map cleanly to customer value and you need someone to translate "what we merged" into "what's new for you." The Gmail draft (not auto-send) keeps marketing in control of the final send.

How it works

  1. 1A GitLab milestone-closed event triggers the flow.
  2. 2The flow fetches MRs in that milestone and reads their labels.
  3. 3A logic branch keeps only MRs tagged customer-facing and drops internal work.
  4. 4If nothing customer-facing shipped, the flow exits quietly with a Slack note.
  5. 5An LLM step rewrites the kept changes as benefit-focused email copy.
  6. 6A Gmail draft is created for marketing to review and send.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.