Skip to content
Base44 logoUnofficial Office Hours archive

Wiring diagram / Session 54

Advanced build-along

One way out
is free.

Discord Bots & Webhooks

Push from your app into Discord and nothing needs hosting. Ask Discord to push back and you have just bought a server. Everything else in this session follows from that.

Thursday 30 July 202616:00 UTCAdvanced
Sam server / template botadmin scope
BASE44 APPholds the secretBOTwakes on commandDISCORDchannels · rolesNO HOST REQUIREDDISCORD/purge · /helpLISTENERalways onBASE44 APPcannot host thisNEEDS A SERVER
15 steps15 answers10 signals

Session brief

Sam has been integrating Base44 apps with Discord bots for about six months, and picked this Thursday to teach it end to end. Discord had other plans. He was rate limited across the developer portal, could not reset a bot token on his desktop because the multi-factor prompt only offered a security key he did not own, and spent the first thirty-six minutes working around failures live — eventually resetting the token from an Android phone and pasting it into the app as a secret.

Once the plumbing held, the payoff was quick. A Base44 app acting as a command centre, holding the bot token as a back-end secret, drove a single natural-language instruction into a fully built Minecraft-themed Discord server: roles, administrators and moderators with real permissions, public and private channels, multiple voice channels, a rule set, and welcome messages posted through webhooks. Sam then created a webhook by hand to show the manual path, and finally configured Discord's native onboarding — questions, server guide and automatic role assignment — from the Base44 app, walking through the finished flow as a new member.

The conceptual core of the session was directional. Sending from a Base44 app out to Discord needs no hosting at all: the bot wakes on command, executes and shuts down. The moment you want Discord to talk back — a slash command, a moderation listener, an always-on process — you need a persistent listener on a server, and Base44 will not host that. Sam's recommended architecture is to keep control inside the app behind a permissions-gated admin panel rather than building slash commands.

Schedule, roadmap, and live incidents

Ten signals from a bumpy hour.

Next week's prompting theme, the roadmap that still does not exist, and two issues escalated mid-stream.

Scroll-scrubbed wiring diagram

Which way does it point?

The single question that decides whether this project costs you a server.

  1. 01 / Outbound

    App → Discord.

    Wake on command, execute, shut down. Nothing to host, nothing to keep alive.

  2. 02 / Inbound

    Discord → app.

    The command has to land somewhere. That somewhere is a server you pay for.

  3. 03 / Design around it

    Keep the controls inside.

    Put moderation in a permissions-gated admin tab and the problem disappears.

OUTBOUND — WAKE ON COMMANDBASE44 APPbot token as secretadmin panel · RLSBOTwakes · executesshuts down againDISCORD SERVERroles · channelswebhooks · onboardingNO HOSTING REQUIRED — THE BOT IS NOT A PERMANENT LISTENERINBOUND — SOMETHING HAS TO BE LISTENINGDISCORD/purge user reasonmember eventsLISTENERalways-on processexternal serverBASE44 APPwill not host thisMANAGE IT FROM BASE44 INSTEAD — GATE THE PANEL WITH ROLES
01

Outbound is free

Your app pings the bot, it wakes, executes and shuts down. It lives in the ether, not on a server.

02

Inbound needs a host

A slash command has to reach something that is always listening. Base44 will not run that process.

03

So keep control in the app

A moderation tab behind row-level security and role permissions beats slash commands, and needs no server.

The path Sam actually walked

Six rungs, in order.

Follow along with your own app open. The recording lets you rewind any rung you lose.

Field notes from the build-along

Fifteen things worth keeping.

Scopes, tokens, webhooks, native onboarding, and the architecture you should actually ship.

Full session

Watch the hour back.

Sam's own advice: skip or speed through the first thirty minutes unless you want the debugging. The server builds itself from around thirty-eight minutes in.

Open on YouTube (opens in a new tab)

15 answered questions

Asked while the build fought back.

Grouped by category. Featured answers settle something the community keeps raising.

Technical7

  • Could you connect the Base44 dashboard to a server and then to a bot, rather than the other way round?

    Sam asked for a use case before endorsing it. Base44 can connect to a server via Discord OAuth login. But for anything resembling a moderation panel, he said you would always do it the way demonstrated: connect the bot to the Base44 app and have the bot embedded in the Discord server.

  • Why is my builder responding in Spanish and Russian?

    A real issue, not user error. Sam confirmed it had been reported on multiple occasions that day and had already been escalated. He did not have a root cause.

  • Could this have been done six months ago?

    Yes, Sam confirmed there are no new restrictions or gates here. What has changed is how long it takes. In the pre-no-code era he said the same result would have taken around six hours, and autonomous creation of Discord channels from scratch was not achievable at all.

Product3

  • Is customising the forgot-password flow on the product roadmap?

    It is on the product team's agenda and they are aware it is a pain point. Sam gave no timeline.

  • Could the newsletter include upcoming features rather than only shipped ones?

    Sam said that is his own request too, and it comes back to the same missing roadmap. The current newsletter covers what has already shipped — the edition going out that day had around six features from the previous two weeks.

Community4

  • When will I be able to use this bot?

    You will not — that was the point. The bot Sam built was deleted straight after the session. The purpose was teaching you how to create and wire your own.

  • Where can I watch the recorded live streams?

    Each session has a permanently hosted YouTube URL you can return to at any time, and the unofficial events archive holds the full back catalogue.

  • Why run such a niche session at all?

    Sam was candid that this will never be a guide on the Base44 website because it is too niche and would not perform. He ran it because a minority of the community are gamers who want to build this themselves, because it is his own passion, and because he values teaching logical thinking and how to navigate unfamiliar territory over waiting for a guide that is never going to exist.

General1

  • Can I use a googlemail.com address in place of a gmail.com one?

    No, and not the other way round either. Sam explained googlemail addresses belong to original Gmail users from before Google held the gmail domain, and the two are not interchangeable.

Carry these out

What to remember before you wire anything.

  1. 01

    Direction is everything. App to Discord needs no host; Discord to app needs an always-on listener that Base44 will not run for you.

  2. 02

    Ask an LLM which scopes your bot needs before granting anything. Administrator is for bots that build servers, not bots that post messages.

  3. 03

    Build the bot into your real app behind a permissions-gated admin panel. The standalone command centre in this demo was scaffolding, not the pattern.

  4. 04

    The bot token is a back-end secret. Reset it, store it, and never let it reach a prompt or a screen share — and expect to re-save it if you reset it again.

  5. 05

    Test on a throwaway server you own. Administrator scope in a real community is not a mistake you get to undo.

  6. 06

    Screenshot straight into the builder. Print Screen, drag, Ctrl+V gives it the visual context that prose cannot.

  7. 07

    Third-party rate limits will ruin a demo and there is no clever fix. Sam lost thirty-six minutes to Discord and recommended returning on a day it behaves.