SOCIAL MEDIA
Evergreen Decay Auditor: Requeue Winners, Retire Losers
Audits each older post's last-reshare performance, automatically retires posts whose engagement has decayed, and re-queues the ones still pulling their weight with refreshed copy.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule triggers audit
- ActionRead library and reshare metrics from PostgresPostgres
- LogicCompare engagement vs baseline; retire decliners
- ActionRefresh copy for healthy posts (OpenAI)OpenAI
- OutputPublish requeued post to socialSocial publishing
- ActionWrite new metrics and timestamp to PostgresPostgres
What it does
This workflow stops you from recycling content that has stopped working. On a regular cadence it reviews how each evergreen post performed on its most recent reshare, compares it against the post's own baseline, and makes a decision: posts still earning solid engagement get refreshed and re-queued, while posts in steady decline are flagged retired so they stop cluttering the rotation.
When to use it
Use it when your evergreen library has grown large and some pieces have clearly aged out. It keeps the rotation lean and high-quality instead of mechanically resharing everything forever.
How it works
- 1A schedule triggers the audit.
- 2It reads the evergreen library and recent reshare metrics from Postgres.
- 3A logic step compares each candidate's latest engagement against its baseline threshold.
- 4Declining posts are marked retired in the database and skipped.
- 5For healthy posts, OpenAI generates refreshed copy.
- 6The refreshed post is published to your social platforms.
- 7Postgres is updated with the new reshare timestamp and metrics for the next audit.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Social publishingCross-post to X, LinkedIn, Instagram, TikTok, and 4 more in one call.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Social Media workflows
Discord event capacity gate with automatic waitlist promotion
Enforces a seat cap on RSVPs: once an event is full, new sign-ups join a waitlist, and when someone drops out the next person is promoted, notified in Discord.
Tiered Discord event reminder fan-out (24h / 1h / live)
On a schedule, scans upcoming Discord-tracked events and DMs each confirmed attendee staged reminders at 24 hours, 1 hour, and event start.
A/B carousel cover variants from one brief
Takes a single approved brief and uses an LLM to write three distinct cover-slide headlines, renders a carousel cover for each, and logs the variants to Airtable for an A/B test.
Localized carousel variants per target market
From one approved master brief, translates the copy into each target locale, renders a localized carousel per market, and publishes each to its region's platform account.
Carousel render and auto-publish on Slack approval
Renders carousel variants from a brief, posts a preview to Slack for a one-click approve, and on approval publishes the chosen variant to the connected social platforms.
Discord /rsvp slash command with Outlook calendar invite
Lets members RSVP to an event via a /rsvp slash command, captures their status (yes/maybe/no), and sends a matching Outlook calendar invitation or cancellation to their email.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.