SOCIAL MEDIA
React with a flag emoji to escalate a community thread to GitHub
When a teammate reacts to a forwarded community message in Slack with a flag emoji, an LLM analyzes the thread sentiment and root cause.
How it runs
The automated pipeline, trigger to output.
- TriggerFlag emoji reaction added in SlackSlack
- ActionFetch the full Slack thread for contextSlack
- ActionClassify sentiment and infer component with OpenAIOpenAI
- LogicMap component to repo, labels, and assignee
- ActionCreate labeled GitHub issue with permalinkGitHub
- OutputReply in Slack thread with issue linkSlack
What it does
Lets your team escalate by reaction. When someone adds a flag emoji to a community message that was mirrored into a Slack channel, this reads the full thread, classifies the sentiment and likely root cause, and files a GitHub issue in the appropriate repository with the right labels and assignee, linking back to the source conversation.
When to use it
Use this when humans, not rules, decide what gets escalated, but you still want consistent, well-formed engineering tickets. A reaction is the lowest-friction signal; the workflow handles the rest of the paperwork and routing.
How it works
- 1A Slack reaction-added event fires when the flag emoji is used.
- 2The workflow fetches the full Slack thread for context.
- 3OpenAI classifies sentiment, summarizes the issue, and infers the likely component.
- 4A logic step maps the inferred component to a GitHub repo, labels, and assignee.
- 5GitHub creates an issue with the summary, sentiment, and Slack permalink.
- 6The bot replies in the Slack thread with the new issue link.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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 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.