New Hermes Agent Integration Update. What if your WhatsApp could think for you? What if you could text one number and a real AI agent texts you back?
Most people have no idea this just dropped and the few who do are already setting it up. Why is nobody talking about this yet? Hey, I'm the digital
avatar of Julian Goldie. I help you learn AI tools and actually use them in your real work, not just
watch videos about them. Today I want to show you something that just landed inside Hermes Agent. It's a brand new WhatsApp Business Cloud
integration. By the end of this video, you'll know what it is, why it matters, and how to wire it up yourself. Stick around because there's a sneaky
setup mistake near the end that trips up almost everyone. If you've never heard of Hermes Agent, here's the
short version. It's an open-source AI agent built by Nuse Research that lives in the background on your computer. It has memory, so it learns your
projects and remembers how it solved things before. It can run scheduled tasks and build its own skills. And the big one for today, it connects to a
bunch of messaging apps from a single process. Telegram, Discord, Slack, Signal, email, and WhatsApp.
Instead of opening a separate app every time you want AI help, you just text it and it replies right there in the chat. Now, here's the new part.
Hermes Agent now has a production-grade WhatsApp Business Cloud integration. You can run it as a private WhatsApp bot just for you or your team or as
a customer-facing support bot. You connect to WhatsApp Business Cloud number or make a new one through
Meta Business Manager, then run one command to wire it into Hermes. The command is Hermes WhatsApp Cloud and it walks you through the whole thing step
by step. And it's not bare-bones. It comes with guided setup, secure webhooks, media and voice support, read receipts, typing indicators, and
interactive approval buttons. You'll see the blue double check marks the moment it reads your message,
typing while it's thinking, and a real tappable button when the agent needs you to confirm something. It feels like a proper app. One thing worth
knowing, there are two ways to put Hermes on WhatsApp. The older way uses the Bailey's bridge. It's quick and works on a personal account with no
public link, but it's unofficial, so there's a small risk Meta restricts the account. This new Cloud API way
is the official Meta supported path. No ban risk. The trade-off is you need a Meta business account and a public web link for messages to come in. For
a real bot you plan to lean on, the Cloud path is the stable choice. Let me walk you through what you need before you start. First, a Meta business
account, not your personal WhatsApp, a business one at business.facebook.com. Second, a Meta app with
WhatsApp turned on. Third, a way to expose your computer to the internet with a secure link. The docs recommend a free tool called Cloudflare tunnel.
No port forwarding, no domain needed. One optional extra. If you install FFmpeg, your voice replies show up as proper WhatsApp voice notes with that
green waveform instead of a plain audio file. If you skip it, everything still works, you just get an
MP3. Now, let's create the Meta app. Go to developers.facebook.com/apps and click create app. Choose the use case connect with customers through
WhatsApp and hit next. Then pick or create a business portfolio, review the requirements, and confirm to create the app. You'll land on a quick start
page. Click start using the API and now you're on the API setup page. One thing to check, make sure a
WhatsApp business account is linked. If you made a fresh portfolio a second ago, one was already created for you. Before I show you the exact values
to copy, let me talk about something most tutorials skip, which is why doing this inside a community changes everything. Setting up a tool is one
thing. Knowing what to do with it once it's live is another. That's the whole reason the AI Profit
Boardroom exists. Inside, for this exact kind of integration, you get walk-throughs that go screen by screen, so you're never guessing where a button
is. There are live coaching calls where you can share your screen, show where you're stuck on your Meta dashboard, and get unstuck on the spot. And
here's a use case I want you to know about. We've built out a complete 30-day roadmap inside the
boardroom. So, you're not just connecting a bot and then staring at it wondering what's next. It lays out what to set up first, second, and third day
by day, so you always know your next move. If you're watching this thinking, "I want to do this, but I don't want to fumble through it alone." that
room was built for exactly this moment. Here's another thing we made inside the boardroom that members
love. We created a single HTML page for an SEO ROI calculator with inputs for monthly traffic, conversion rate, average order value, and estimated SEO
lift. You plug in your numbers and it shows you the projected return from your SEO work all on one clean page. It's the kind of practical tool you can
copy, tweak, and use right away. And it's exactly the type of build we walk you through step by
step. Okay, back to the setup. On that API setup page, you'll collect a few values. The first is the phone number ID, and this is the number one
mistake. The phone number ID is not your actual phone number. It's a long internal ID, around 15 to 17 digits, sitting below the from drop-down.
People paste their real phone number there and wonder why nothing works. Copy the ID, not the phone number.
Next, you grab an access token. It starts with the letters EAA and runs over 100 characters. The quick token only lasts 24 hours, which is fine for
testing, but useless for a real bot that needs to run tomorrow. For something you rely on, the docs walk you through making a permanent system user
token. You give it the right permissions, set the expiration to never, then drop it into your Hermes
settings file and restart. The last must-have value is the app secret, a 32-character code under settings, then basic, by clicking show next to app
secret. This is how Hermes checks the incoming messages are really from Meta and not someone faking it. Without it, your messages get refused. So,
treat it like a password and never share it. Now, you need to let Meta reach your computer, and this is
where Cloudflare tunnel comes in. You install it, then run one line that points a tunnel at your local Hermez port. It hands you back a public link
ending in trycloudflare.com. That's what you give Meta. One catch, the free quick tunnel gives you a new link every time you restart it. So, if it
stops working later, grab the fresh link and update it. For a steady link, make a free named tunnel
instead. With your tunnel running, you set up the webhook on Meta's side. You generate a verify token, a shared secret that lets Meta and Hermez
confirm they're talking to the right place, then start the Hermez gateway. In the Meta dashboard, you open the webhook section, paste your tunnel link
with /whatsapp/webhook on the end as the callback URL, paste your verify token, and click verify and
save. Last step, under webhook fields, you click manage and subscribe to the messages field. That's the switch that tells Meta to start sending you
incoming messages. Miss that one and your bot sits there silent. If you haven't installed Hermez yet, that part is the easy bit. On Mac or Windows,
you download the Hermez desktop installer and run it. Or for a command line install, you run a single
curl command from the install page. The installer handles all the dependencies for you, Python, Node, FFmpeg, all of it. By the end, you type Hermez
and start chatting. Then you run that Hermez WhatsApp Cloud Wizard. A few pro tips if you're new to this. One, use a dedicated phone number for the
bot, not your personal one. Two, while you're still in development mode, Meta only lets your bot
message a small list of numbers you approve, up to five. So, add your own number there first to test. Three, remember the 24-hour rule. Meta only lets
your bot send free messages within 24 hours of someone messaging it, which covers normal back and forth chat just fine. And four, if a setup check
fails, it's usually a stale tunnel link or a mismatched verify token. If you want the full process,
SOPs, and 100 plus AI use cases like this one, join the AI Success Lab. Links in the comments and description. You'll get all the video notes from
there, plus access to our community of 75,000 members who are crushing it with AI. And once you're ready to go build this, here's my honest take. The
setup is simple when someone shows you, but the spots where people get stuck are always the same. The
phone number ID mix-up, the expiring token, the webhook field you forgot to subscribe to. Inside the AI Profit Boardroom, we have walkthroughs for
this exact integration, coaching calls where you can show your screen and get past the stuck point fast, that 30-day roadmap so you know the order to
do things in, and prompts so your new WhatsApp agent is useful from day one. If you want this working
without the trial and error, come join us at aiprofitboardroom.com.