CHATBOTS

Discord Stalled Onboarding Nudge

Runs daily to find members who started but never finished Discord onboarding, DMs them a reminder of exactly which FAQ step they got stuck.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionQuery in-progress onboarding recordsSupabaseSupabase
  • LogicSplit by days stalled: nudge vs escalate
  • ActionDM stalled member their stuck stepDiscordDiscord
  • ActionPost long-stalled members to moderator channelDiscordDiscord
  • OutputUpdate nudge count and last-contacted in SupabaseSupabaseSupabase

What it does

This scheduled job scans your onboarding records for members who opened a verification thread but never reached the final step. It DMs each stalled member a personalized nudge naming the exact step they stopped at, and escalates anyone stuck for more than seven days to a moderator channel.

When to use it

Use it when partial onboarding is hurting activation — people join, get distracted, and sit unverified forever. Instead of manual chasing, this recovers stalled members automatically and surfaces the truly inactive ones to your mod team.

How it works

  1. 1A daily schedule triggers the run.
  2. 2The flow queries Supabase for onboarding records where status is in-progress.
  3. 3A logic step splits members into recently-stalled (nudge) versus long-stalled (escalate) by days since last activity.
  4. 4For nudge cases, Discord sends a DM citing the specific incomplete step.
  5. 5For escalation cases, the flow posts a summary to the moderator channel in Discord.
  6. 6Supabase is updated with the new nudge count and last-contacted timestamp.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SupabaseTables, auth, storage, edge functions.
  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.