CONTENT CREATION

Release tag to customer email draft plus ReadMe post

On a new GitLab release tag, generates release notes, publishes them to ReadMe, and drafts a ready-to-send customer announcement email in Gmail for a final human review.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab release tag pushedGitLabGitLab
  • ActionFetch merge requests in the tag rangeGitLabGitLab
  • ActionGenerate changelog entry and customer emailOpenAI
  • ActionPublish changelog post to ReadMeReadMeReadMe
  • OutputCreate reviewable announcement draft in GmailGmailGmail

What it does

Bridges shipping and customer comms. A new GitLab release tag produces polished release notes that both go live on your ReadMe changelog and become a drafted announcement email in Gmail, so marketing or success only has to review and hit send.

When to use it

Use it when each release deserves a proactive customer email, not just a docs update. Best for teams that announce releases to a customer list and want the docs post and the email written from one source so they never drift.

How it works

  1. 1A new release tag in GitLab triggers the flow.
  2. 2The flow pulls the merge requests included in the tag range.
  3. 3An LLM step writes two outputs from the same change set: a structured ReadMe changelog entry and a warmer, narrative customer email.
  4. 4The changelog entry is published to ReadMe as a dated post.
  5. 5The email is created as a Gmail draft addressed to your announcement alias, left unsent for a human 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 ReadMeAPI docs, changelog, auth.
  4. 4
    Connect GmailRead, draft, send, label.
  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.