Facebook Marketplace Discord Bots: Build One or Use a Webhook?

The three ways listings end up in Discord

“Facebook Marketplace Discord bot” gets used for three quite different set-ups. They all finish with a message in a channel, but who does the watching, and who fixes it when it stops, is very different.

Tools and prices in this post were checked on 15 September 2026 from each project’s own public pages. If you are comparing alert services rather than DIY options, the alert app comparison covers that side in more depth.

You probably want a webhook, not a bot

A Discord bot is an application with its own user account and token, which you invite to a server and keep running so it can read commands and reply. That is a lot of machinery for a job that only goes one way: a listing appears, a message is posted.

A webhook does exactly that one-way job. Discord’s developer documentation describes webhooks as “a low-effort way to post messages to channels” that need no bot user. You create one on a channel, Discord gives you a URL, and anything that sends a message to that URL appears in the channel. There is nothing to host and nothing to keep online on the Discord side.

So the useful question is not “which bot?” but “what is going to watch Marketplace and send to my webhook?” That watcher is where all the difficulty lives, and it is the part the rest of this post is about.

How to create a Discord webhook

You need the Manage Webhooks permission on the server, which server owners and admins have by default. On desktop or in a browser:

1. Create a text channel for the alerts, for example #marketplace-alerts. Keeping alerts in their own channel lets you set notifications for that channel alone.
2. Hover over the channel, click the cog to open Edit Channel, and choose Integrations.
3. Click Webhooks, then New Webhook.
4. Give it a name you will recognise, such as “Marketplace”, and check it is pointed at the right channel.
5. Click Copy Webhook URL. It starts with https://discord.com/api/webhooks/.
6. Paste that URL into whatever is doing the watching, and send a test message before you rely on it.

Two habits save trouble later. Treat the URL like a password: anyone who has it can post into your channel, and if it leaks you can delete the webhook and make a new one. And set the channel’s notification setting to All Messages on your phone, because a webhook message does not mention anyone and will otherwise arrive silently.

The open-source bot route, honestly

There are several free projects on GitHub that watch Marketplace and post to Discord. The most complete is Hyacinth, a Python project which, according to its repository, sends notifications for new listings with built-in support for Craigslist and Facebook Marketplace. It offers boolean filtering rules and adjustable polling intervals, is deployed with Docker, and needs a Discord bot token that you create yourself.

If you are comfortable with that stack, it is a genuinely good way to learn how these systems work. The catch is everything that sits around the code:

• It has to run all the time. A script on your laptop stops watching the moment the lid closes. In practice you need a small server or a home machine left on, and you need to notice when it quietly stops.
• Facebook is not a stable target. Marketplace pages change their structure without notice, and a scraper that parsed them last week can return nothing this week. With a free project, the fix arrives when a volunteer has time.
• Repeated requests get throttled. Checking often from the same connection is exactly the pattern Facebook limits, and the faster you poll, the sooner you hit it. Logged-out visitors can also be shown login prompts in place of results.
• Using your own account is a risk. Signing a script in with your personal Facebook login to get past those prompts puts the account you actually buy and sell with on the line if automated activity is flagged.
• Repeats and near-misses are your problem. Every check sees the same listings again, so the bot has to remember what it has sent. And a keyword match is not the same as the item: “iPhone 15” also matches cases, cracked screens and wanted-to-buy posts.

None of this makes DIY wrong. It makes it a hobby project whose upkeep grows the faster you want it to check.

Scraper platforms and what frequent checks cost

The middle route is a hosted scraper you schedule yourself. Apify’s Facebook Marketplace Scraper is the best-known example: its page lists pricing of $2.60 per 1,000 listings returned, with $5 of free usage credit each month, scheduled runs, and webhooks and integrations such as Zapier and Make. Someone else maintains the scraper, which removes the biggest DIY headache.

What remains is the arithmetic. A scraper run returns the listings currently showing for your search, not only the new ones, and you pay for each listing returned. Suppose each run of one search returns 20 listings. The monthly cost of that single search then looks like this:

This is an illustration using Apify’s published per-listing price on 15 September 2026, before the free credit, and your real numbers depend on how many results a search returns and any platform charges. The shape is what matters: per-result pricing is cheap for a daily or hourly check and becomes expensive exactly where alerts start to be useful. You would still need to build the step that drops listings you have already posted and sends only new ones to your webhook.

Why check frequency decides whether you get the item

Whichever route you pick, the message format hardly matters. What matters is how long a listing has been live before it reaches your channel.

Good listings follow a predictable pattern. Someone posts a console, a bike or a dresser priced to be gone this week rather than to squeeze out every dollar. The first message arrives within minutes, more follow, and within the hour it is often marked pending. By the time most people see it while scrolling, the seller has already said yes to someone else.

You cannot beat that by refreshing the app, and an hourly check is not much better. A good listing can be claimed well inside the gap between two checks. Facebook’s own saved searches do not publish how often they run, and their notifications are often late or missing, which the notifications guide covers. That is why check frequency is the one specification worth comparing, whether you are building a bot or buying a service — and why it is the specification that makes DIY hardest and scraper platforms most expensive.

Setting up an alert channel that you will actually act on

A Discord channel full of alerts is only useful if you notice the right ones quickly. A few set-ups work well:

• One channel per kind of search. Cars in one, phones in another. You can then set phone notifications to All Messages on the channels that are worth waking up for and leave the rest quiet.
• Tight searches beat busy channels. A channel that pings forty times a day trains you to ignore it. Use exclude words and a price ceiling so each alert is a listing you might genuinely buy; the keyword alerts guide shows how to build those lists.
• Share it with a buying partner. One of the best reasons to use Discord at all is that a partner or small team sees the same feed, so whoever is free first sends the message.
• Have your opening message ready. Speed only pays if the message you send is clear. A short, specific question about pickup time converts better than “is this available?”, and how to negotiate on Marketplace covers what to say next.

Where Outpost Alerts fits

Outpost Alerts is an Australian-built service that watches Facebook Marketplace for new listings matching your keywords and sends them to a web dashboard or Discord. For Discord it is the hosted route in the table above: you paste your webhook URL into Settings → Alerts, press Send test webhook to confirm it lands, and matches start arriving in that channel.

Each match is posted as its own message with the listing title, price, location and how recently it was listed, plus an Open in Outpost button. The text sits in the message itself rather than in an embed, so it shows up in your phone’s notification preview. Turn on the full-listing option and the alert carries the seller’s description too, with a second button straight to the Facebook listing.

The watching happens in the cloud, as often as every minute on Pro, every 3 minutes on Standard and every 30 minutes on Basic, across 10, 5 or 1 watchlists. Each watchlist has its own include and exclude words, price range, cities and radius. Outpost also filters out keyword matches that are not the item: across 30,777 keyword-matching listings, 38.6% were discarded as not the item searched for — 18,890 kept against 11,887 rejected. In a Discord channel, that is the difference between a feed you watch and one you mute.

What it does not do is just as clear. It watches Facebook Marketplace only, with no Craigslist, Gumtree or eBay. It is not an interactive bot, so there are no slash commands; you manage searches in the web dashboard. It does not value a listing or tell you whether it is a good buy. And it has no free plan: Basic is $14.99, Standard $39 and Pro $79 a month in US dollars, each with a 3-day trial, on the pricing page on 15 September 2026. If you enjoy running your own scraper, Hyacinth is a fine project. If you want the listing rather than the project, Outpost does the watching for less than frequent scraper runs cost. For the wider set-up, see how Marketplace alerts work, and the Swoopa alternatives comparison if you are weighing other services.

FAQ

Sources checked

• Discord developer documentation: Webhook resource, checked 15 September 2026.
• Hyacinth on GitHub: features, Docker deployment and bot token requirement, checked 15 September 2026.
• Apify Facebook Marketplace Scraper: per-listing pricing, free monthly credit and integrations, checked 15 September 2026.

Marketplace features, fees, and policies change. Confirm current rules in Facebook's Help Center before relying on specific details.