SOCIAL MEDIA
Log guest clip approvals from an intake webhook into Airtable
Captures a guest's clip-approval submission via webhook, validates which episode and timestamps they signed off.
How it runs
The automated pipeline, trigger to output.
- TriggerGuest submits clip-approval form (webhook)HTTP webhook
- LogicValidate required fields and episode ID
- LogicBranch each clip: approved vs declined
- ActionUpsert one rights row per clip in AirtableAirtable
- OutputWrite episode rollup row marking rights loggedAirtable
What it does
Turns a guest's clip-approval reply into a clean, queryable rights ledger. When a guest submits the approval form (which clips they're okay sharing, plus any edits), the workflow normalizes the data and creates one Airtable row per approved clip, tagged with episode, timestamp range, platforms allowed, and an expiry date if they set one.
When to use it
Use it when your show sends guests a clip-approval form after recording and you want every yes/no captured in one place before the social team schedules anything. It removes the "did they actually approve this one?" guesswork.
How it works
- 1A webhook fires when the guest submits the approval form.
- 2A logic step checks required fields are present (episode ID, at least one clip decision) and rejects malformed payloads.
- 3For each clip, a logic branch routes approved vs. declined.
- 4An Airtable action upserts a row per clip with status, allowed platforms, and approval date keyed on clip ID so re-submissions update in place.
- 5The final output writes a rollup row marking the episode "rights logged" once all clips are recorded.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AirtableBases, tables, views, automations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.