Free Discord Giveaway Bot

If you're searching for a Discord giveaway bot, NoriaFlow's Giveaway node handles the whole lifecycle in one node. It posts the giveaway, collects entries, and automatically picks and announces winners: no separate bot, no manual draw.

Why people look for a giveaway bot#

• Manual draws are error-prone: copying reaction lists into a random picker by hand doesn't scale past a few dozen entries, and it's easy to miscount or forget a rule.
• No requirement gating: many quick giveaway tools can't restrict entry to a specific role (like a booster or subscriber role).
• Single-purpose bots: a bot that only does giveaways is one more thing to invite, permission, and maintain alongside everything else running your server.

How NoriaFlow's giveaway works#

• Enter by button or reaction: pick whichever style fits your community; both give an instant confirmation.
• Runs on its own: set a duration ("30m", "2h", "3d") and NoriaFlow closes entries and draws winners automatically, even if nobody's watching.
• Entry conditions: restrict entry to a role, to accounts older than a given age, or to members who have been on the server long enough. The usual defence against throwaway accounts joining for the prize.
• Bonus entries: chosen roles get extra entries, so boosters or subscribers are likelier to win. They can still only win once.
• Multiple winners: pick as many distinct winners as you need from one giveaway.
• Customizable announcement: the winner announcement can post in a different channel than the giveaway itself, and winners can also get a DM.
• Free in beta: the whole feature is included at no cost while NoriaFlow is in open beta.

Every Giveaway option, explained#

One node, one screen of settings. Here is what each one does:

• Server & channel: where the giveaway post goes.
• Prize: what winners get. It appears in the giveaway post and in the winner announcement.
• Duration: how long entries stay open, written like 30m, 2h, or 3d (default 24h). When it elapses, entries close and winners are drawn automatically.
• Number of winners: how many distinct entrants are picked at random when it ends.
• How members enter: Click a button gives every entrant an instant "you're entered" reply. React with an emoji is the classic giveaway-bot style, with a configurable entry emoji (🎉 by default).
• Required role: optional. Only members holding this role can enter; anyone else gets a private reply naming the role they need.
• Minimum account age (days): 0 for no limit. Otherwise a Discord account created more recently than this cannot enter, and is told how many days it still needs.
• Minimum time on the server (days): 0 for no limit. Otherwise a member who joined too recently cannot enter, so the prize goes to the community rather than to people who joined for it.
• Bonus entry roles & entries: members holding any of these roles get that many entries instead of one, so their odds of taking a winner slot go up. Holding several bonus roles still counts once, and no member can ever take two of the winner slots.
• Giveaway post text: optional custom text for the post itself. {{prize}}, {{duration}}, and {{winnerCount}} are filled in automatically; leave it empty to use the default.
• Winner announcement: the message posted when the giveaway ends. {{winners}} becomes the winner mention(s) and {{prize}} the prize.
• No-entries message: posted instead of the winner announcement when nobody entered.
• Winner announcement channel: leave empty to announce where the giveaway was posted, or point it at a dedicated channel like #winners.
• Also DM winners: sends each winner the winner text as a direct message too. A winner with DMs closed doesn't get one; the public announcement still names everyone.

One quirk worth knowing: the editor may flag {{prize}}-style placeholders as unknown variables. That warning is expected and harmless. The Giveaway node fills them in itself when it runs.

Run your first giveaway#

1. Connect your own Discord bot to NoriaFlow.
2. Open the Discord Giveaway Entry template or add a Giveaway node to a blank workflow.
3. Set the prize, duration, number of winners, and (optionally) a required role.
4. Test, then Activate: the giveaway posts and runs on its own.

Three giveaway formats that work#

• On-demand: a Manual Trigger wired to the Giveaway node. Click Run whenever you feel like it; the giveaway posts immediately and draws when its duration ends.
• Weekly: swap in a Schedule trigger with a cron like 0 18 * * 5 (every Friday at 18:00, in the timezone you set). Give the giveaway a 2d duration and it posts Friday evening and announces winners Sunday evening: every single week, hands-off.
• Timed reveal: post a hype message first, add a Wait node set to a duration like 1h, then the Giveaway node. Wait is durable, so the countdown survives restarts and can span hours or days.

Troubleshooting#

• Someone clicked but wasn't counted: check the required role. Members without it are silently ignored by design; mention the requirement in your giveaway post text so it isn't a surprise.
• A winner never got the DM: their DMs are closed. The public announcement still mentions them, so nobody misses a win.
• Winners announced in the wrong place: an empty announcement channel means "same channel as the giveaway". Set it explicitly to route announcements elsewhere.
• The bot can't post: make sure it has permission to send messages in both the giveaway channel and the announcement channel.

Make it your own#

• Gate it to a role: reward boosters, subscribers, or verified members only.
• Announce somewhere else: post the giveaway in one channel and the winner announcement in another, like a dedicated #winners channel.
• Combine it with a level milestone, the leveling bot can grant a role at a level milestone, then that role becomes the giveaway's required role, only members who've reached it can enter.

That's a giveaway bot you fully control: free during the beta, no code. Start building free, see what else you can build on the same bot in the template library, or build your first workflow to get started.

Setup checks and next steps#

• Check the selected bot, server and destination channel. Role actions also require the bot role to sit above the role it changes.
• Test with a dedicated channel or member before enabling this automation for everyone.
• If a step fails, inspect its error and inputs rather than reconnecting every account.

See the extension setup guide for adding and reusing services, the node reference for parameters, and testing and debugging for execution diagnostics.