SOCIAL MEDIA

Chase creators who haven't answered the rights request

On a daily schedule this scans the Airtable tracker for permission requests still Pending past a set window, sends a polite follow-up email.

CategorySocial Media
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionFind Pending requests past wait windowAirtableAirtable
  • LogicBranch: under reminder limit?
  • ActionSend follow-up or mark ExpiredGmailGmail
  • ActionUpdate reminder count or statusAirtableAirtable
  • OutputPost chase summary to SlackSlack

What it does

Runs every day to find clearance requests that have sat in Pending too long. For each stale request it sends one follow-up email to the creator and increments a reminder count. Once a request crosses the maximum reminders, it is flagged Expired so your team knows that post can never be reposted without fresh consent.

When to use it

Use this when your initial permission emails go unanswered and you need a hands-off way to nudge creators and retire dead requests, keeping the tracker honest about what is actually cleared.

How it works

  1. 1A daily schedule starts the sweep.
  2. 2Airtable is queried for rows with status Pending older than the wait window.
  3. 3A branch checks each row's reminder count against the maximum.
  4. 4Under the limit: a follow-up email is sent and the reminder count is incremented.
  5. 5At the limit: the row is set to Expired.
  6. 6A summary of chased and expired requests is posted to your team Slack channel.

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