Automation
Scheduled Content
Publish one-time or recurring Discord announcements.
Getting started
Create content
Build text or an embed with fields, media, footer, buttons, mentions, and the live Discord preview.
Choose timing
Set the server timezone and create a one-time, daily, weekly, monthly, interval, or advanced schedule.
Add campaign behavior
Configure multi-step follow-ups, A/B variations, conditions, quiet hours, skip rules, expiry, and catch-up behavior.
Use the calendar
Review upcoming sends in agenda, week, or month views and detect overlapping campaigns.
Operate safely
Pause, clone, send a test, send now, retry failed deliveries, inspect the execution timeline, and review interaction analytics.
Back up your settings
Export or back up schedules. Restored campaigns remain paused until their channels and timing are reviewed.
Settings reference
Use this reference when you need to check what a setting does.
Dashboard identifier.
Text or embed with optional fields, media, footer, buttons, and mentions.
Destination validated against the active server.
Once, hourly, daily, weekly, or calendar-month recurrence with a configurable interval.
Named timezone used for local scheduling and quiet-hour rules.
Member count, recent activity, deduplication, blackout dates, approval, and other skip controls.
Durable delayed follow-up messages after the primary delivery.
Optional A/B content selected and measured per send.
Send, skip, or reschedule behavior after downtime.
Paused items retain data but are skipped.
How it works
Here’s what happens once you’ve finished setup.
- 1Scheduler
Checks due items every 30 seconds and claims a database lease.
- 2Due item
Confirms entitlement, module state, approval, timing, quiet hours, and conditions.
- 3Send
Renders variables and posts the selected variation and components.
- 4Sequence
Queues durable follow-up jobs.
- 5Advance
Calculates the next calendar-aware run or disables a completed one-time item.
- 6Measure
Records delivery, failure, click, RSVP, poll, and variation activity.
Example
Monday 20:00 UTC, #announcements, weekly frequency, red accent, short title, and a message with events, creators, and links.
Permissions
- View Channel
- Send Messages
- Embed Links
- Mention roles only when the message requires them
Troubleshooting
The worker checks every 30 seconds and hosting or Discord latency can add a short delay.
Check timezone, next run, active state, approval, conditions, quiet hours, channel, permissions, and bot uptime.
Calendar recurrence preserves the day when possible and uses the final valid day in shorter months.
Change the missed-run policy from Send to Skip or Reschedule if catch-up delivery is unwanted.
Common questions
It posted at the wrong time+
Confirm the timezone shown in the schedule editor and the UTC conversion stored in the execution timeline.