SOCIAL MEDIA

Parse guest approval emails and auto-update the clip-rights tracker

Watches a shared inbox for guest replies to clip-approval requests, uses an agent to extract which clips were approved, declined, or need edits.

CategorySocial Media
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGuest reply lands in approval inbox (Gmail)GmailGmail
  • ActionAgent extracts per-clip decision from email
  • LogicSeparate clear decisions from ambiguous/edits
  • ActionUpdate each clip's status in AirtableAirtableAirtable
  • OutputRoute edge cases and edits to producerGmailGmail

What it does

Reads free-form guest email replies and turns them into structured rights decisions. Guests rarely fill out forms neatly; they reply "yeah the first two are fine but drop the bit about my old company." An agent reads the thread, maps each comment to the right clip, and records approved, declined, or edit-requested per clip, escalating anything ambiguous to a human.

When to use it

Use it when guests approve by email in their own words rather than via a form, and someone is manually translating those replies into your tracker. This captures the nuance without losing the audit trail.

How it works

  1. 1A Gmail trigger fires on a reply landing in the clip-approval inbox or label.
  2. 2An agent step reads the email plus the original clip list and extracts a per-clip decision with reasoning.
  3. 3A logic branch separates clear decisions from ambiguous or edit-request cases.
  4. 4An Airtable action updates each clip's status and notes requested edits.
  5. 5The output sends edge cases and edit requests to the producer for manual handling.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.