SOCIAL MEDIA

Retire Evergreen Posts That Stop Earning Engagement

Compares each evergreen post's most recent recycle performance against its lifetime average and, when a post underperforms across repeated re-shares, retires it from the rotation…

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule starts review
  • ActionRead recent recycle performance from AirtableAirtableAirtable
  • LogicCompare latest engagement to lifetime baseline
  • LogicBranch underperformers to retire path
  • ActionMark posts Retired in AirtableAirtableAirtable
  • OutputPost retired-items digest to SlackSlack

What it does

Prunes your evergreen rotation so it doesn't fill up with tired content. It reads recent recycle results from Airtable, flags any post whose last few re-shares fell well below its own historical average, marks those posts "Retired," and sends a Slack digest so a human can confirm or rescue them.

When to use it

Use it when your recycle pool has grown large and some posts clearly aren't landing anymore. Running this weekly keeps the rotation lean and protects your feed from diminishing-returns reposts.

How it works

  1. 1A weekly schedule starts the review.
  2. 2Recent recycle performance for each post is read from Airtable.
  3. 3A logic step compares the latest re-share engagement to the post's lifetime baseline.
  4. 4Posts that fell below baseline across multiple recent runs are branched into the retire path.
  5. 5Those posts are marked "Retired" in Airtable and a digest of what was retired is posted to Slack for review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.