Webhook targets
Save named Discord webhook destinations, server/channel labels, and optional webhook username/avatar overrides.
Local Discord Scheduler
DisDoveOnTime
Discord Post Scheduler.
Schedule Discord posts from your own Windows machine. Keep webhook targets, drafts, media, queue state, and send history local while the app handles the operational details around timing, missed runs, retries, and review.
Windows 10 / Windows 11
Discord webhooks
Local JSON data
A scheduler for Discord posts.
DisDoveOnTime is not a hosted marketing platform or a Discord bot account. It is a focused Discord Scheduler for people who already use Discord webhooks and want predictable scheduled posting from a computer they control.
Posts and media
Create scheduled posts with message text, normal or embed mode, and image or video attachments up to the documented 10 MB non-Nitro limit.
Missed-run policy
Choose what happens when the app was closed or the computer slept: send on next run, mark missed, or mark failed.
Operational state
Queue handling, send-state transitions, retry/backoff fields, health summaries, and redacted send-attempt journaling keep the flow inspectable.
The app stays close to the actual Discord send flow.
It prepares content locally, sends through Discord's webhook endpoint, and treats uncertain network outcomes as something the user should review instead of pretending every timeout is a clean failure.
It works best when you already know what should be posted and only need a Discord Scheduler to hold the draft, send it at the right time, and keep the result easy to review.
1
Add a target
Paste a Discord webhook URL, give it a readable label, and keep the destination information local.
2
Prepare the post
Set local Budapest-aware date/time fields, message body, mode, attachment, and missed-run behavior.
3
Send when due
The local scheduler moves due posts into a guarded queue and sends them through the webhook transport.
4
Review outcomes
Success stores Discord message IDs when available. Ambiguous outcomes move to review instead of blind duplicate retries.
Security and reliability boundaries are explicit.
- Webhook URLs are secrets. Treat local app data, logs, screenshots, backups, and exports as sensitive if they can include webhook data.
- The app stores its working data locally under Unity's persistent data path, including database JSON and managed attachments.
- Discord-side global exactly-once delivery is not promised. The realistic goal is local dedupe, state tracking, review, and auditability.
- Rate limits and retryable failures use explicit retry/backoff state instead of uncontrolled repeated sends.
PayPal donation
Donate to Xefande
DisDoveOnTime is free to use. If it helps your Discord workflow, a small donation helps keep releases moving.