SOCIAL MEDIA
Classify creator email replies as consent granted, denied, or unclear
Triggers on creator replies to permission requests, classifies the response as granted, denied, or needs-clarification, updates the Airtable consent status.
How it runs
The automated pipeline, trigger to output.
- TriggerCreator reply arrives in GmailGmail
- ActionClassify reply intent and conditionsOpenAI
- LogicBranch on granted, denied, or unclear
- ActionUpdate consent status on recordAirtable
- OutputNotify team on a clear grantSlack
What it does
This workflow reads inbound replies to your rights requests and decides what the creator actually said. It classifies each reply as consent granted, denied, or ambiguous, matches it back to the right clearance record, and updates the consent status. Clear grants trigger a Slack ping so the content can move toward reshare.
When to use it
Use it once outreach is live and replies are landing in your inbox. It removes the manual triage of "did they say yes?" and keeps your consent ledger trustworthy, which matters when legal asks for proof of permission.
How it works
- 1A new Gmail message in the rights-requests label triggers the run.
- 2OpenAI classifies the reply intent as Granted, Denied, or Needs Clarification and extracts any conditions the creator attached.
- 3A logic branch routes by classification.
- 4The matching Airtable row is updated with the new consent status and a quote of the relevant reply text for the audit trail.
- 5On a clear grant, a Slack message notifies the social team that the asset is cleared.
- 6Denied or unclear replies are flagged in Airtable for human follow-up.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.
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.
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.
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.