SOCIAL MEDIA

Repost only rights-cleared UGC on a schedule

On a recurring schedule this pulls Approved-but-unpublished rows from the Airtable tracker, double-checks the consent is still valid, reposts the cleared asset with creator credit.

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerRecurring publish schedule fires
  • ActionFetch Approved, unpublished rowsAirtableAirtable
  • LogicBranch: consent valid and unexpired?
  • ActionRepost cleared asset with creditSocial publishing
  • OutputMark row Published with post URLAirtableAirtable

What it does

Turns your cleared-asset backlog into scheduled posts. It selects Airtable rows that are Approved but not yet published, confirms the consent record and expiry are valid, then publishes the stored media to your social accounts with an auto-built credit caption tagging the creator. Each published row is stamped so nothing is reposted twice.

When to use it

Use this once clearance is flowing and you want a steady, compliant repost cadence without a person manually checking which assets are safe to publish.

How it works

  1. 1A recurring schedule triggers the publisher.
  2. 2Airtable returns rows marked Approved with no Published date.
  3. 3A branch verifies the consent is on file and not expired.
  4. 4Invalid consent rows are flagged Needs Review and skipped.
  5. 5The cleared media and a credit caption are sent to post-to-platforms.
  6. 6The Airtable row is updated with the live post URL and Published timestamp.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect Social publishingCross-post to X, LinkedIn, Instagram, TikTok, and 4 more in one call.
  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.