SOCIAL MEDIA

File a creator's permission reply and archive the asset

When a creator emails back granting (or denying) repost rights, this parses the decision, updates the Airtable tracker.

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReply received in clearance inboxGmailGmail
  • ActionParse clearance ID and grant decisionOpenAI
  • LogicBranch: permission granted?
  • ActionUpdate Airtable to Approved or DeniedAirtableAirtable
  • OutputArchive cleared media to DropboxDropboxDropbox

What it does

Watches a dedicated inbox for replies to your rights-request emails. It reads the creator's decision, matches it to the clearance ID, and updates the Airtable row to Approved or Denied. For approvals, it pulls the original media into a Dropbox folder so your team only ever sources reposts from cleared files.

When to use it

Use this as the second half of your clearance pipeline: once requests are out, this closes the loop automatically instead of having someone manually read inbox replies and move files.

How it works

  1. 1A reply email lands in the rights-clearance inbox.
  2. 2The clearance ID and grant/deny intent are parsed from the message.
  3. 3A branch checks whether permission was granted.
  4. 4If denied, the Airtable row is set to Denied and the flow ends.
  5. 5If granted, the row is set to Approved with the consent text saved.
  6. 6The post media is downloaded into a dated Dropbox cleared-assets folder.

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
    Connect DropboxFiles and folders.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.