SOCIAL MEDIA
Harvest recurring Discord questions into a canonical Coda FAQ
On a schedule, pulls the last day of messages from your Discord support channels, clusters the recurring questions with an LLM.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch last 24h of Discord support messagesDiscord
- ActionCluster and rank recurring questions (OpenAI)OpenAI
- LogicKeep frequent questions not already in FAQ
- ActionDraft canonical answers (OpenAI)OpenAI
- OutputAppend new Q&A rows to Coda FAQ docCoda
What it does
This workflow turns the noisy stream of community questions in Discord into a clean, deduplicated FAQ table in Coda. Once a day it reads recent support-channel traffic, identifies which questions keep coming up, and adds the genuinely new ones to your canonical answers doc so the document stays current without manual triage.
When to use it
Run this when the same handful of questions get asked weekly and your team keeps re-answering them in chat. It is for community managers who maintain a public FAQ or help doc and want it to reflect what people are actually asking right now.
How it works
- 1A daily schedule fires the run.
- 2It fetches the last 24 hours of messages from the configured Discord support channels.
- 3An OpenAI step extracts question-shaped messages, groups near-duplicates, and ranks them by frequency.
- 4A logic step keeps only questions above a recurrence threshold and not already present in the Coda FAQ table.
- 5For each surviving question, OpenAI drafts a concise canonical answer.
- 6The new question-and-answer rows are appended to the Coda FAQ doc as the final output.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect CodaDocs, packs, automations.
- 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.