Preflight is a Discord scheduler that posts announcements to a channel through a webhook, at a time you choose, with Markdown text, up to ten files and an optional name and avatar. It is for community managers, creators and small teams who announce the same thing on Discord and elsewhere and do not want to add a bot to the server to do it. Discord has no built-in way to schedule a message, and a webhook has no scheduling field, so the post is held by Preflight and sent when it is due. How to schedule Discord posts is the walkthrough; this page is the integration.
| Discord through Preflight | What the API allows |
|---|---|
| Text limit | 2,000 characters |
| Media | Pictures and video, up to 10 files |
| Pictures | Up to 10 MB each |
| Video | 10 MB, no limit enforced |
| Thread in one go | No |
| First comment | No |
| Alt text | Yes |
| Edit after publishing | Yes |
| Delete from Preflight | Yes |
| Comments | Not available through the API |
| Figures reported | None |
| Retention and traffic sources | No |
What goes out
- Text. Up to 2,000 characters, with Discord's own Markdown (bold, lists, code blocks, links).
- Files. Up to ten per message, 10 MB each and 25 MB together. Pictures take alt text, which Discord shows as the attachment's description.
- A name and an avatar. A message can be posted under a different name and picture than the webhook's default, set per post.
- Silent. A flag that sends the message without a notification.
- A forum thread. In a forum channel, the thread name you give opens a new thread with the message as its first post.
- A link. Once the connection knows its server and channel, the post row links to the message. The link opens only for people who are in that server, which is how Discord works.
Preflight sends plain content and files. It does not build embeds, buttons, polls or role mentions.
Connecting a channel
There is no OAuth, no bot to invite and nothing to approve. In Discord, open Server Settings, then Integrations, then Webhooks, create a webhook for the channel you want and copy its URL. Paste the URL into Preflight. Anyone with the Manage Webhooks permission on the server can do this.
Preflight accepts only an address of the form discord.com/api/webhooks (including the canary, ptb and discordapp variants), then requests it once to prove it exists and to learn which server and channel it points to. The URL carries its own secret in the last segment, so Preflight stores it encrypted, as it does any credential. One webhook is one channel; a second channel is a second webhook.
What fails most often:
- The webhook was deleted. Discord answers 401 or 404, Preflight marks the channel as needing a new webhook and does not retry. Create a new one and paste its URL.
- The URL was copied from the wrong place. A channel's invite link or a message link is not a webhook URL; the paste is refused with the expected form.
- A forum channel without a thread name. Discord requires either a thread name or an existing thread for a webhook in a forum or media channel.
- A custom name with "discord" or "clyde" in it. Discord refuses these names, and Preflight refuses them first.
What the API allows
| Capability | Allowed | Notes |
|---|---|---|
| Publish text | Yes | Up to 2,000 characters |
| Publish files | Yes | Up to 10, 10 MB each, 25 MB together |
| Schedule on the network's clock | No | The webhook documentation describes no scheduled sending; Preflight sends at the chosen time |
| Edit after publishing | Yes | The text, by the webhook that posted it |
| Delete | Yes | Only messages that webhook posted |
| Custom name and avatar | Yes | Per message |
| Forum thread | Yes | Needs a thread name in a forum channel |
| Silent | Yes | Suppresses notifications |
| Read the channel, comments, reactions | No | A webhook can only write |
| Embeds, polls, components | Not used | Discord allows them; Preflight does not send them |
What the API refuses
- Reading anything. A webhook can write to its channel and read back its own messages, and that is all. It cannot see replies, reactions or other channels, so there are no figures to show and the analytics columns are off for Discord. Reading would take a bot, with the access that implies.
- Messages by other people. A webhook edits and deletes only what it posted. Preflight can fix its own announcement but cannot touch a moderator's message.
- A bot's abilities. Slash commands, buttons, role mentions with permissions and presence in a voice channel belong to bots. Preflight is a webhook on purpose: it is scoped to one channel, can be deleted from Discord's settings at any time, and takes nothing with it. A bot would be able to read every channel it is let into, which is more than a scheduler needs.
- Bigger files. The limit Preflight applies is 10 MB per file, the ceiling for a server with no boost. Boosted servers allow more, but Preflight does not assume it, so it warns before a long upload rather than after.
- Scheduled sending. Discord has no field for it. The post waits in Preflight, and if you cancel it there, nothing was ever sent.
What Preflight checks before a post leaves
The checks run in the composer, the scheduler, the public API and the MCP server alike.
- Text against 2,000 characters.
- Each file against 10 MB, and all of them against 25 MB together, naming the total when it is over.
- More than ten files: warned about as not sent.
- A custom name containing "discord" or "clyde".
- An empty post, with neither text nor a file.
Limits for every network are collected at limits. If Discord answers 429 or 503, Preflight waits for the time Discord gives and tries again, up to eight times, instead of failing the post. A 400, 401 or 404 is treated as permanent, because retrying cannot fix a deleted webhook or a refused message.
The platform's rules in short
- Webhooks are rate limited per webhook. Discord's documentation sets a global ceiling of 50 requests per second for bots and tracks webhooks as their own resource with their own buckets. Announcements a few times a day are far from it. A script that posts in a loop is not.
- Obey the wait. A 429 carries a retry time. Discord asks you to read it and wait rather than hard-code limits, and to stop sending on an exhausted bucket until it resets.
- A dead webhook stays dead. Discord says that if a webhook returns 404 you should stop using it, and repeated attempts can get the sender restricted. This is why Preflight stops and asks for a new webhook.
- Invalid requests get an IP banned. Ten thousand 401, 403 or 429 responses in ten minutes lead to a temporary block of the address. One shared sender makes this everyone's problem, which is why a failing webhook is switched off, not retried forever.
- No unsolicited messages. Discord's Developer Policy restricts unsolicited messages and marketing to users and bars attempts to get around limits. Post to a channel whose members expect it.
- Data stays within the feature. The policy limits use of API data to what the app does and bars selling it or scraping. A write-only webhook has little to collect, and Preflight's own policy is at privacy.
- The Terms and Policy apply to webhooks and bots alike once you use Discord's APIs, and Discord may change limits at its discretion.
Checked against the platform's own documents on 8 October 2026; this is a summary, not legal advice. Sources: Discord rate limits, Discord webhook resource.
In the API
Name, avatar, thread name and the silent flag are fields in the API and parameters in the MCP server; the field list is in network options. Discord is on every plan at pricing, including the free one.
Questions people ask
- Can you schedule Discord messages?
- Not inside Discord, which has no message scheduler, and not through a webhook, which has no scheduling field. A scheduler such as Preflight keeps the message and posts it through a webhook at the chosen time.
- Webhook or bot for scheduled Discord posts?
- A webhook is enough for announcements: it writes to one channel, needs no invitation and can be deleted in Discord at any time. A bot is needed only to read the channel, answer replies or use commands, and it asks for far more access.
- Can a Discord webhook post to a forum channel?
- Yes. Create the webhook on the forum channel and give the post a thread name; the message opens a thread with that name. Discord refuses a webhook post in a forum channel with no thread name.
- Can I edit or delete a scheduled Discord message after it is sent?
- Yes, if the same webhook sent it. A webhook can edit the text of its own messages and delete them. It cannot touch messages from people or other webhooks.
- Does Preflight show reactions or replies on Discord?
- No. A webhook cannot read the channel, so Discord reports nothing back, and the analytics columns are left off instead of shown empty.