One sharp WhatsApp growth tactic in your inbox each week. Joined by 238,000+ founders, marketers and support leads.
Free forever. No spam, unsubscribe in one click.
Give Windsurf's Cascade agent a WhatsApp send-and-read tool so it pings your phone when a long run finishes and asks before it ships. Hosted MCP connector or /v1, no Meta Cloud API.
One authenticated POST from Elixir with Req and Jason, no vendor SDK. Then the parts that bite: the path escape that sends to the wrong number, the null waMessageKey, and an Oban retry that sends twice.
Give Cursor a WhatsApp send-and-read tool so its agent pings your phone when a long run finishes and asks before it ships. Hosted MCP connector or /v1, no Meta Cloud API.
One authenticated POST from Swift with async/await, URLSession, and Codable, no third-party package on Apple platforms. Then the parts that bite: the percent-encoder that ruins the path, the null waMessageKey, and a Task fan-out that sends twice.
Give Claude Code a WhatsApp send-and-read tool so it pings your phone when a build or deploy finishes, and waits for your yes before it ships. Hosted MCP connector or /v1 API, no Meta Cloud API.
One authenticated POST from Rust with reqwest, Tokio, and serde. Then the parts that bite an Actix or Axum service: the encoder that ruins the path, the null waMessageKey, and a spawn fan-out that sends twice.
There is no first-party Grok bot on WhatsApp. But you can point your own Grok at the number you already own and have it read, triage, and draft, with every send waiting for your approval.
One authenticated POST from Kotlin, no third-party HTTP client. Then the parts that bite a Spring Boot app: the encoder that ruins the path, the null waMessageKey, and a coroutine retry that sends twice.
There is no official Gemini bot on WhatsApp. But you can point your own Gemini at the number you already own and have it read, triage, and draft, with every send waiting for your approval.
One authenticated POST from Ruby, zero gems. Then the parts that bite Rails: the escape method that ruins the path, the null waMessageKey, and a Sidekiq retry that sends twice.
Let your own AI or coding agent ping your WhatsApp number before it refunds, merges, or deploys, then wait for your yes. The outbound approval loop, set up honestly.
One authenticated POST from Go, zero third-party packages. Then the parts that bite: the http.Get with no timeout, the encoder that ruins the path, and a retry that sends twice.
Point your assistant at the WhatsApp number you already own and it reads the backlog, ranks the few messages that matter, and drafts replies for you to approve. Here is how, and the honest hosted-vs-DIY call.
One authenticated POST from .NET, no NuGet package required. Then the parts that bite C#: the new HttpClient that exhausts sockets, the encoder that ruins the path, and a retry that sends twice.
Point any LLM at the WhatsApp number you already use and let it read, sort, and draft before you touch a thread. No Meta approval, no per-message fees, no chatbot.
A queued message is not a sent message. Here is exactly why scheduled WhatsApp sends fail, how to read the delivery signals, and how to make them fire on time.
The WhatsApp Business API never verifies consent for you. Here's what opt-in actually means at the API layer, how to collect it before your first call, and how to record and sync opt-in and opt-out programmatically with webhooks.
WhatsApp has no built-in birthday automation. Here's how to set up an automatic birthday message once and have it send from your own number every year.
One POST from the JDK, no build tool needed. Then the parts that bite Java: the plus sign in the path, the request that blocks a thread forever, and a retry that sends twice.
The nine WhatsApp MCP tools an AI agent can call, a capability-and-limits table for each, which AI clients work today, and why none of it runs without a live session.
Short answer: WhatsApp has no send later button. Here is what people mistake for one, and the workflow that puts a message out at the time you picked.
Meta's Cloud API sends, but it never hands you the conversations you already have. Here is the read path on your own number, endpoint by endpoint, gaps included.
A chat connector acts only while you are in the chat. Here are the three pieces that make WhatsApp work at 03:00 when nobody is typing, and the failure that catches everyone.
A WhatsApp webhook closes the loop your send call leaves open: the outbound lifecycle event by event, honest reliability notes, and receiver code in Python and Node.
The click-path most guides still get wrong, the nine WhatsApp tools ChatGPT actually sees, and the prerequisite that decides whether any of it works.
Fifteen lines of cURL, no Composer needed. Then the parts that break: the plus sign in the URL, Guzzle's zero-second timeout, and a retry that sends twice.
There is no Blueticks node to search for. There is an HTTP Request node and an API key, and that is enough. Every field, for all three platforms.
Your day-by-day plan works for one batch. Here's the operating model for a rolling intake: cohort-anchored enrollment, a weekly cadence, and no no-reply branch.
Sending to a group is one path segment. Creating one, adding twelve people in a single call, promoting an admin and knowing in advance which groups will reject you is the rest of the job.
Attachments are where WhatsApp API integrations quietly break. Here is the real media request contract: caption in `text`, the mediaKind enum, filename rules, two different size ceilings, and the GIF that arrives as a file.
Runnable Node code for a WhatsApp bot on the number your customers already have saved. Send, receive in Express, schedule follow-ups, and the production bits that stop double-sends.
Your agent can query production and file tickets but still hands you WhatsApp drafts to copy-paste. Here is the tool definition, the send call, and what actually breaks.
Your first scheduled POST works. This is everything that breaks after it: naive timestamps, double sends on retry, 429s, and messages that vanish without a trace.
You have the group, you have the message, and you want it out at 7am. Here's the workflow that works, and the honest list of group types where it won't send.
Turn Claude into your WhatsApp chief of staff: a morning brief prompt, a reusable triage rubric, and a draft-and-approve habit you can be running by tonight.
Fire a WhatsApp message straight from your code with one POST. Working Python, Node, and cURL examples, how to schedule for later, and no Meta Business verification.
A step-by-step build for a WhatsApp automation sequence that fires timed follow-ups on its own and stops the second a lead replies. From your own number, free to start.
WhatsApp still has no send-later button. A Chrome extension that runs inside WhatsApp Web is the closest thing to native scheduling, and it sends from your own number.
Automating WhatsApp from code is easy to start and easy to break. Here's how to run triggered sends, scheduled sequences, and safe retries on your own number, without a Meta approval queue.
You want Claude to read and answer WhatsApp for you. Here is the exact MCP setup: link your number, add the connector, approve access, and run a read-only triage first.
You're already in WhatsApp Web and want to write now, send later. There's no native button, so here's the send-later workflow that actually works, and its one honest catch.
Your phone can be off. Your computer usually cannot. Here is which WhatsApp schedulers actually send while your devices are dark, and how to test it in three minutes.
A REST API that sends WhatsApp messages from the number you already text people from, no Meta Business verification, no per-message fees. The full curl and Python walkthrough.
Four ways to put an AI agent on WhatsApp in 2026, the uptime each one really gets, and how to build a Blueticks agent in plain words and test it from a second phone.
Wire up a WhatsApp API with webhooks so inbound messages hit your server and get an instant auto-reply. Real Flask and Express code, signature verification, and the production traps.
The WhatsApp Business app can't send a reminder on a schedule. Here's how to automate recurring client follow-ups anyway, with cadences that don't feel like spam.
Scheduling and automating WhatsApp are two different jobs. Here's what each one means, why the app can't do either, and the fastest reliable way to do both.
You describe the workflow in plain English, and Claude runs it on your own WhatsApp number. Four real recipes for automating WhatsApp with AI, plus the honest limits nobody mentions.
A working WhatsApp bot in Python, on the number you already use, without Meta Business verification. Send, receive replies over a webhook, auto-reply to keywords, and schedule messages, with runnable code and the failure modes nobody mentions.
WhatsApp has no native follow-up scheduler. Here's how to build a real automated follow-up sequence — 5 copy-paste templates and a step-by-step setup that actually runs.
No native scheduler. No background auto-send via Shortcuts. Here's what actually works for iPhone users who need WhatsApp messages to go out at a specific time.
Type 'schedule a WhatsApp to Dana tomorrow at 9am' and Claude does it. The popular open-source WhatsApp MCP servers can only read and send. Blueticks' MCP is the one that also schedules and runs paced campaigns — from your own number, no terminal required.
Most WhatsApp APIs can only send a message right now. Far fewer let you schedule one for later — from your own number, over a plain REST call. Here's how to do both in Python and Node, with webhooks for delivery and replies.
Stop copy-pasting the same WhatsApp message 80 times. Here's how to take a spreadsheet of contacts, personalize each message, and schedule the whole batch from your own number with Blueticks.
How to send appointment, payment, and follow-up reminder messages on WhatsApp: what WhatsApp can't do natively, the templates that actually get a reply, and the reliable way to schedule them.
Everything about WhatsApp Web in 2026: how to log in by QR, how linked devices work when your phone is off, the real fixes when it won't load, and what it can't do.
You can run two WhatsApp numbers on one phone — but not the way most guides claim. Here's what the app actually allows, where companion mode and linked devices fit, and when you really need the API.
WhatsApp has no native scheduler on Android. Here's how Tasker and MacroDroid fake one with the accessibility service, exactly why they break, and what to use instead.
WhatsApp read receipts are how the ticks tell you a message was read. Here's exactly how they work in 2026, how to turn them off, and what they can never tell you.
Schedule WhatsApp messages free, right inside WhatsApp Web. QR linking, the exact workflow, recurring and offline sends — no native scheduler exists yet.
WhatsApp has no native recurring scheduler. Here's how to set up daily, weekly, and monthly WhatsApp messages that send themselves on autopilot.
Neither iOS nor Android has a native WhatsApp scheduler — not even WhatsApp Business. Here's the full picture of workarounds, and what actually works in 2026.
WhatsApp Business has auto-replies but no real outbound scheduler. Here's what works in 2026 for scheduling business messages, broadcasts, and bulk sends.
One tick, two ticks, blue ticks. Each state tells you something different about your message. Here's exactly what WhatsApp's tick system means and how to use it.
Native scheduling is barely a thing. Here's how to set up reliable one-time and recurring WhatsApp messages on desktop and mobile in 2026.
