SOCIAL MEDIA

Chase creators who never replied to a UGC permission request

Scans for clearance records stuck in Permission Requested past a waiting window, sends one polite follow-up email per creator, increments a reminder counter.

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule runs follow-up sweep
  • ActionFetch stale pending requestsAirtableAirtable
  • LogicSplit by reminder count vs limit
  • ActionSend polite follow-up emailGmailGmail
  • OutputBump counter or escalate to reviewAirtableAirtable

What it does

This workflow recovers silent rights requests. It finds clearance records that have sat in "Permission Requested" longer than your chosen waiting period and sends a single courteous follow-up. It tracks how many reminders each creator has received and stops chasing after the limit, handing those off for a human decision instead of spamming.

When to use it

Use it when permission requests routinely go unanswered and you are leaving usable content on the table. It enforces a respectful cadence: nudge, wait, nudge again, then escalate, with every step logged.

How it works

  1. 1A schedule runs the follow-up sweep.
  2. 2Airtable returns rows in "Permission Requested" whose last-contact date is older than the waiting window.
  3. 3A logic step splits rows by reminder count: under the limit gets a follow-up, at the limit gets escalated.
  4. 4For under-limit rows, Gmail sends a short follow-up referencing the original request.
  5. 5Airtable increments the reminder counter and refreshes the last-contact date.
  6. 6At-limit rows are set to "Manual Review" so an operator decides whether to drop or pursue them.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect GmailRead, draft, send, label.
  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.