SOCIAL MEDIA
Weekly recap thread from the week's GitLab releases
On a weekly schedule, collects all GitLab release tags from the past seven days, writes a single 'this week we shipped' founder thread.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionList past 7 days of GitLab releasesGitLab
- LogicExit if nothing shipped this week
- ActionWrite weekly recap threadOpenAI
- ActionSend recap to Slack for approvalSlack
- OutputPublish approved recapSocial publishing
What it does
Rather than one post per release, this builds a weekly highlight reel. It pulls every release tag from the last seven days, summarizes the arc of what shipped into one cohesive founder thread, and sends it for approval before going out.
When to use it
For founders who ship often and would flood their feed with per-release posts. A weekly recap keeps a consistent presence without spamming — and reads as a story of momentum rather than disconnected notes.
How it works
- 1A weekly schedule trigger fires (e.g. Friday afternoon).
- 2A GitLab action lists all release tags and notes created in the last seven days.
- 3A logic step checks the count — if nothing shipped, the run exits quietly.
- 4An OpenAI step weaves the releases into one narrative thread with a momentum-focused hook.
- 5The draft posts to Slack with Approve / Reject and pauses.
- 6On approval, post-to-platforms publishes the recap.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect Social publishingCross-post to X, LinkedIn, Instagram, TikTok, and 4 more in one call.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Social Media workflows
Discord event capacity gate with automatic waitlist promotion
Enforces a seat cap on RSVPs: once an event is full, new sign-ups join a waitlist, and when someone drops out the next person is promoted, notified in Discord.
Tiered Discord event reminder fan-out (24h / 1h / live)
On a schedule, scans upcoming Discord-tracked events and DMs each confirmed attendee staged reminders at 24 hours, 1 hour, and event start.
A/B carousel cover variants from one brief
Takes a single approved brief and uses an LLM to write three distinct cover-slide headlines, renders a carousel cover for each, and logs the variants to Airtable for an A/B test.
Localized carousel variants per target market
From one approved master brief, translates the copy into each target locale, renders a localized carousel per market, and publishes each to its region's platform account.
Carousel render and auto-publish on Slack approval
Renders carousel variants from a brief, posts a preview to Slack for a one-click approve, and on approval publishes the chosen variant to the connected social platforms.
Discord /rsvp slash command with Outlook calendar invite
Lets members RSVP to an event via a /rsvp slash command, captures their status (yes/maybe/no), and sends a matching Outlook calendar invitation or cancellation to their email.
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.