SOCIAL MEDIA

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.

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled run every 15 minutes
  • ActionQuery upcoming events and RSVP listsPostgreSQLPostgres
  • LogicClassify event into 24h / 1h / live tier
  • ActionDM unreminded attendees for the tierDiscordDiscord
  • OutputMark reminders sent to prevent duplicatesPostgreSQLPostgres

What it does

This workflow checks all upcoming events on a fixed cadence and sends each confirmed RSVP a direct message reminder at three tiers: 24 hours out, 1 hour out, and right at start time. Each attendee receives exactly one DM per tier.

When to use it

Use this when no-shows are hurting your community events and channel-wide @everyone pings are too noisy. It targets only people who actually RSVP'd and respects how close the event is.

How it works

  1. 1A scheduled trigger runs every 15 minutes.
  2. 2The flow queries upcoming events and their RSVP lists from the attendee table.
  3. 3A branch classifies each event by how much time remains, selecting the 24h, 1h, or live reminder tier.
  4. 4For attendees who have not yet received that tier, it sends a personalized Discord DM with event details and a join link.
  5. 5It marks each reminder as sent in the table to guarantee no duplicates.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.