SOCIAL MEDIA
Post-event Discord attendance recap and host digest
After a synced calendar event ends, reconciles who RSVP'd against who actually showed, posts a thank-you recap in Discord, and emails the host a digest of attendance and no-shows.
How it runs
The automated pipeline, trigger to output.
- TriggerCalendar event endsGoogle Calendar
- ActionPull RSVP and check-in recordsPostgres
- LogicCompute attendance rate and no-shows
- ActionPost thank-you recap in Discord threadDiscord
- OutputEmail host the attendance digestGmail
What it does
When a Google Calendar event ends, this workflow compares the RSVP list against recorded check-ins, posts a public recap thanking attendees in the Discord event thread, and sends the event host a private email digest with attendance rate, no-shows, and waitlist conversions.
When to use it
Run this to close the loop after every community event so hosts get attendance data automatically and members feel acknowledged. Useful for tracking engagement trends across a recurring event series.
How it works
- 1A Google Calendar event-ended notification triggers the workflow.
- 2The flow pulls the event's RSVP and check-in records from the attendee table.
- 3It computes attendance rate, lists no-shows, and counts waitlist promotions that converted.
- 4It posts a thank-you recap in the event's Discord thread tagging confirmed attendees.
- 5It emails the host a formatted digest via Gmail with the full breakdown for their records.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect DiscordCommunity channels + voice + bots.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect GmailRead, draft, send, label.
- 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
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.
Multi-Platform Comment Escalation Router
Ingests inbound comments and replies from your connected social platforms, classifies each for legal or PR risk.
Agent-Driven Comment Policy Review Queue
An agent reviews ambiguous comments against your brand's response policy, decides whether to auto-clear, draft a reply for approval, or escalate, and routes its decision…
Carousel render with brand-safety pre-check
Before rendering, an LLM checks the brief copy against brand and policy rules; clean briefs render and archive to S3, flagged briefs route to a review queue instead.
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.
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.