CHATBOTS

Nudge Stalled Discord Members Who Skipped Onboarding

On a daily schedule, finds members who joined but never picked a use-case role, and sends a friendly DM nudging them to complete onboarding with a one-click prompt.

CategoryChatbots
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionQuery un-roled stale members from PostgresPostgreSQLPostgres
  • LogicFilter out recently nudged members
  • ActionSend onboarding nudge DM on DiscordDiscordDiscord
  • ActionRecord nudge timestamp in PostgresPostgreSQLPostgres
  • OutputPost nudge summary to staff channelDiscordDiscord

What it does

This workflow catches members who joined your server, got a welcome, but never told you their use-case or picked up a role. Once a day it identifies these stalled arrivals and sends a personalized direct message nudging them to finish onboarding so they unlock the right channels.

When to use it

Use this when a meaningful share of joiners go quiet before completing setup and you want to recover them automatically. It re-engages drop-offs without a moderator manually auditing the member list each morning.

How it works

  1. 1A daily schedule triggers the flow.
  2. 2It queries Postgres for members who joined more than 24 hours ago and still have no use-case role logged.
  3. 3A logic step filters out members already nudged recently to avoid spamming.
  4. 4For each remaining member, it sends a friendly Discord DM with a short prompt to pick their use-case.
  5. 5It records the nudge timestamp in Postgres so the same person isn't pinged repeatedly.
  6. 6A summary of how many were nudged is posted to the staff channel.

Set it up

What you configure once, before turning it on.

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