SOCIAL MEDIA

Detect brand-tagged creator posts and queue them for rights clearance

Scrapes new public posts that tag or mention your brand, filters for genuine creator UGC.

CategorySocial Media
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionScrape posts tagging the brandApify
  • LogicDrop own posts and known duplicates
  • ActionCreate clearance record per candidateAirtableAirtable
  • OutputWrite run summary to trackerAirtableAirtable

What it does

This workflow watches for fresh creator content that tags your brand handle or hashtag, separates real user-generated content from your own posts and reposts, and writes every qualifying candidate into an Airtable base as a clearance record. Each row starts at status "Needs Permission" so your team has a clean queue of content to chase rights for before resharing.

When to use it

Run it when you want a reliable, deduplicated intake of UGC mentions instead of manually scrolling feeds. It is the front door of a rights pipeline: detection and logging only, so downstream workflows can handle outreach and consent tracking.

How it works

  1. 1A daily schedule kicks off the run.
  2. 2Apify scrapes recent public posts matching your brand handle and tagged hashtags.
  3. 3A filter drops posts authored by your own accounts and any already present in Airtable, keeping only new third-party creators.
  4. 4For each survivor, an Airtable row is created with creator handle, post URL, caption, follower count, and status "Needs Permission".
  5. 5The final output writes a run summary row noting how many new candidates were captured.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ApifyActors, scrapers, datasets.
  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.