OTHER
Reclaim Discord Roles from Inactive Members
On a schedule, finds members who have been inactive past a threshold, downgrades their roles to free access.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled cleanup run
- ActionQuery inactive membersPostgres
- LogicExclude lifetime and staff
- ActionRemove elevated roles, set baselineDiscord
- ActionMark reclaimed in PostgresPostgres
- OutputPost cleanup summary to staffDiscord
What it does
Runs periodic hygiene on community access: it queries activity records, identifies members who have gone quiet beyond your threshold, removes their elevated Discord roles, and delivers a summary of who was reclaimed.
When to use it
Use it when role sprawl accumulates over time and you want gated channels to reflect genuinely active members rather than everyone who ever qualified once.
How it works
- 1A scheduled trigger runs the cleanup (for example weekly).
- 2A Postgres query returns members whose last activity timestamp is older than the configured threshold and who still hold elevated roles.
- 3A logic step excludes lifetime members and staff from reclamation.
- 4For each remaining member, Discord removes the elevated roles and reassigns the baseline role.
- 5The activity table is updated to mark them reclaimed, and a summary of the run is posted to the staff Discord channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect DiscordCommunity channels + voice + bots.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Other workflows
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Build a daily expected-visitor roster and send it to the front desk
Every morning this pulls the day's pre-registered visitors from Airtable, builds a sorted arrival roster with hosts and times.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
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.
