Connect your website’s RSS or Atom feed once and every new article, release or episode lands in the Discord channel you choose — as a proper embed card, in front of the community that already cares, without anyone pasting a link.
Discord is where a growing share of audiences now actually gather. Software projects, games, creators, shops, investing groups and local communities all run servers, and the people in them are there deliberately — they joined, they stayed, and they read. That makes a Discord channel one of the few places where an announcement is genuinely likely to be seen rather than swept past.
The problem is the same as everywhere else: a channel only stays useful if it is fed. Announcing every new article by hand means switching to Discord after each publication, finding the right channel, pasting the link and waiting for the embed. It takes a minute, and it is forgotten constantly — most reliably on the days you publish something that matters.
Your site already maintains a machine-readable list of everything it publishes: the RSS feed. WordPress, Shopify, Ghost, Substack, Blogger, PrestaShop, OpenCart, every podcast host and every YouTube channel emit one without being asked. PostRSS reads that feed and posts each new item into the channel you nominate. Publishing becomes the trigger, so the channel updates itself.
Discord is unusual among the networks PostRSS supports, and it is worth understanding why before you set anything up.
Facebook, X and LinkedIn are built around public pages, and each offers an OAuth login that grants an outside tool permission to post on your behalf. Discord is architected around private, invite-based servers, and it deliberately does not offer a “connect your RSS feed” switch. Instead it exposes webhooks — a URL tied to one specific channel that any external service can post into.
That difference has three practical consequences, all of them in your favour:
There is no bot to invite and nothing installed in your server. There is no login — PostRSS never sees a Discord account, yours or anyone’s. And access is scoped to a single channel: a webhook cannot post anywhere else, read your messages, see your member list or change anything. If you want the mechanism itself explained in depth — creating the URL, keeping it safe, what the errors mean — see autoposting to Discord with a webhook. This page is about the destination: which channel, what members see, and how to keep it welcome.
Open the channel’s settings with the gear icon beside its name, go to Integrations, choose Webhooks and create a new one. Name it something recognisable — “PostRSS” or “Blog” — click Copy Webhook URL, then Save Changes. It takes under two minutes and requires the Manage Webhooks permission, which server owners and most admin roles already have.
In PostRSS, every destination is a Target. Paste the webhook URL to add the channel as one. A single account can hold as many Targets as your plan allows, so several Discord channels, a Telegram channel and a Facebook Page can all run from the same content.
Paste the address of your RSS or Atom feed. On WordPress this is usually your domain followed by /feed/, and every category and tag has its own — /category/releases/feed/, for example, which is frequently exactly what a Discord channel wants rather than the whole blog. If you are unsure whether your site publishes one, open the homepage source and look for application/rss+xml.
From then on, publishing on your site is the only action required. PostRSS notices the new item, builds the message and posts it into that channel. Nothing needs opening, checking or approving.
PostRSS sends the item’s title and a link to the original page, and Discord builds an embed card from the destination page’s open-graph tags — the image, the title and the description your site already declares for sharing. The result is a card with a thumbnail and a summary, not a bare blue link in the middle of a conversation.
This is worth understanding, because it means the appearance of your Discord posts is controlled by your website. If a post arrives with no image, the article is missing an og:image, or the image is too large, or a CDN rule is blocking Discord’s fetcher. Fixing it at the source fixes every network at once — Discord, Telegram, Facebook, LinkedIn and X all read the same tags.
Discord caches embeds, so if you correct an image and the old one persists for a while, that is the cache rather than the automation. It clears on its own, and a changed image URL bypasses it immediately.
This decision matters more than any setting. An automated feed dropped into a server’s #general is an interruption: it pushes down whatever conversation was happening, and the cost is paid by your most active members.
Almost every server that automates content well uses a dedicated channel — #blog, #releases, #news, #announcements. People who want the content subscribe to that channel’s notifications; people who are there to talk are not pushed past it. The channel becomes a browsable archive of everything you have published, which is useful in its own right.
Set the channel to read-only for most roles if you want it to stay an archive, or leave it open if you would rather people react and discuss underneath each post. Both work; the one to avoid is a busy conversational channel that also receives automation.
Discord has a channel type worth knowing about here. An announcement channel can be followed by other servers, so posts published in it are mirrored into a channel in each following server automatically.
For anyone publishing content other communities care about — a library, a game, a tool, a data source — this changes the arithmetic considerably. You automate one channel in your own server, other server owners follow it, and your articles reach their members too, with no further work from you and no additional Tasks consumed.
A webhook posts into an announcement channel exactly as it does into a normal one, so nothing about the PostRSS setup changes. The only thing to be deliberate about is volume: a channel other servers have chosen to mirror should carry your signal, not your whole blog.
Most Discord channels want a slice of a site rather than the whole thing. A support server wants release notes and documentation updates. A game community wants patch notes. A shop’s server wants one product line, not the catalogue.
PostRSS applies filters to the feed before anything is sent. You can restrict a Target by category or tag, require a keyword in the title, or exclude one. Several Targets can run from the same feed with different rules, which is how a single site feeds #releases, #blog and a partner’s server without publishing three times.
A useful check before you enable anything: look at the last month of your feed and count how many items would have passed your filter. If a general-purpose channel would have received more than eight or ten, tighten the filter. Discord members are quick to mute a channel, and a muted channel is a channel that no longer works.
A common request is to have automated posts ping people. Be careful here. A role mention on every automated post turns a useful channel into a notification source people disable, and the effect is permanent — once muted, members rarely unmute.
The pattern that works is to let the channel itself carry the signal and leave notification choice to members. Discord lets anyone opt into all messages for a specific channel, and the people who want your articles the moment they appear will do exactly that. Save actual pings for the handful of announcements that genuinely warrant interrupting everyone.
PostRSS checks your feed every 5 minutes on every plan, and every 1 minute on Enterprise. That is how fast a post can arrive; it is not always how fast it should.
Two situations call for scheduling. The first is bursts — an editorial team publishing six articles in one morning will otherwise fire six messages into the channel within minutes of each other. The second is time zones: a community concentrated in one region gets more from a post that lands during waking hours than one buried overnight.
PostRSS’s scheduling controls constrain when a Target may publish, holding items found outside the window and releasing them inside it. Feed checking is unchanged; only the release moves. It also keeps you comfortably clear of Discord’s per-channel rate limit, which allows roughly five messages every five seconds across everything posting into that channel.
Release notes and changelogs are close to ideal. Discord communities form around products, and the questions that follow a release get answered in the channel instead of in support tickets.
Documentation updates behave the same way, and give the channel a searchable history that reduces repeat questions.
Podcast episodes and YouTube videos both work well, and neither needs extra setup: every podcast is already an RSS feed, and every YouTube channel exposes one keyed to its channel ID.
Long-form articles land well when the server’s subject matches the article’s, and poorly when the feed is a general blog. Filter accordingly.
Product feeds are the category to handle carefully. A shop pushing every new item into a community server reads as advertising quickly. Use a dedicated channel, filter hard, or reconsider.
Check the webhook first. If someone deleted it in the channel’s Integrations panel, or the channel itself was deleted, publishing stops — the feed is still being read and PostRSS still has your content, but Discord has nowhere to deliver it. Recreating the webhook produces a new URL, which has to be updated in PostRSS.
That is a filter behaving as configured. Review the category, tag and keyword rules on the Target before assuming a fault.
No schedule is set on the Target, so everything found in one feed check goes out together. Add a publishing window.
Compare timestamps against your publication time. Under five minutes is the feed-check interval working normally. Hours means the feed is cached — a caching plugin or CDN serving a stale copy. PostRSS can only read what your server serves.
Open the article and inspect its open-graph tags. Discord renders what the page declares.
Servers grow, and so does the case for more than one automated channel. A project might run #releases for changelog entries, #blog for articles and #status for incident notices — three channels, three webhooks, three Targets, and potentially one feed filtered three ways.
The same applies across servers. If you run a community server and also participate in a partner’s, each gets its own webhook, and each can receive a different slice. Nothing is shared between them: deleting one webhook affects only that channel.
In PostRSS terms, each channel is one Target and each message is one Task against your plan’s monthly allowance. A channel receiving five items a week costs roughly twenty-two Tasks a month.
Discord gives you less analytics than most networks — no per-message view counts outside Server Insights on Community servers. The signals that matter are simpler anyway.
Watch reactions and replies. A post that consistently draws neither is a post the channel did not want, and the fix is the filter rather than the frequency. Watch the member count of the channel if it is opt-in. And add UTM parameters to your links so your analytics can separate Discord traffic from everything else — after a month you will know how many sessions the server sends and how they behave.
Also watch what stops happening. If conversation in the wider server drops after you automate, the automation is too loud. That signal appears long before anyone complains.
Each Discord channel you connect is one Target, and each automated message is one Task against your plan’s monthly allowance. Paid plans raise both numbers and add the other networks, and they are chosen on postrss.com rather than inside the mobile app.
Discord Targets are usually inexpensive in Task terms precisely because they are filtered — the costly Targets are high-volume broadcast channels, not focused server channels.
The mechanism behind this page is covered separately in autoposting to Discord with a webhook, which goes through creating the URL, keeping it safe and reading the errors. If your audience prefers a messenger to a server, a Telegram channel is the closest equivalent, and a Matrix room is the option that bridges to several networks at once.
For a team rather than a community, the same feed belongs in Slack or Microsoft Teams. And if you want your feed to reach something PostRSS has no native destination for, a webhook into Zapier, n8n or Make will get it there.
No. Publishing uses a channel webhook, so nothing is installed in your server and no bot appears in your member list.
No. There is no OAuth step and no password. The webhook URL is the only thing PostRSS holds, and it can only post into the one channel it belongs to.
Yes. A webhook works identically in a private server; whoever creates it simply needs the Manage Webhooks permission.
Yes. Create a webhook in each channel, add each as its own Target, and point them at the same feed — with different filters if the channels cover different things.
No. PostRSS publishes items that appear in the feed after the Target starts running, so a channel is never flooded with your archive.
Two ways: pause the Target in PostRSS, or delete the webhook in the channel’s Integrations panel. Either stops publishing immediately.
Pick the server you know best, create a dedicated channel rather than using an existing conversation, choose the narrowest feed that still carries something members asked for, and set a publishing window before enabling it. Watch the first two weeks for reactions. If they appear, widen carefully; if they do not, narrow the filter rather than raising the volume.
