--- title: "InOut Personal WhatsApp Integration" description: "Send messages to your own WhatsApp number through InOut.bot, a personal notification API built on the official Meta stack. Agents deliver alerts to the phone you actually check." url: https://flowrunner.ai/integrations/inout-personal-whatsapp date_modified: 2026-08-07T17:20:23-07:00 --- # InOut Personal WhatsApp [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Send messages to your own WhatsApp number through InOut.bot, a personal notification API built on the official Meta stack. Agents deliver alerts to the phone you actually check. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 4 actions · API key · available [InOut Personal WhatsApp website](https://inout.bot/) · [Platform Documentation](https://inout.bot) · Capability data verified 2026-08-12 1. A flow reaches an action it will not take unattended, such as a payment run above the standing threshold 2. Agent assembles the decision context, what it wants to do, the amount, and every check it already passed 3. Send Message delivers the question to your own WhatsApp with the message type set to Urgent 4. Agent reads the remaining message balance returned with the send and confirms the channel can still reach you 5. Make Phone Call reads the same question aloud down a GSM line when no reply arrives before the deadline 6. You answer, and the flow releases the held action or abandons it ## What This Integration Enables Read the configuration before you plan anything with this connector, because it decides what the connector is for. Messages are delivered to the WhatsApp number the API key is bound to. Sending to other numbers is listed by the vendor as in progress and is not part of the API. This is not a customer channel. It is a personal notification line to the person who owns the automation, built on the official Meta WhatsApp stack, and it does one job unusually well. That job is the delivery leg of a [digital andon cord](https://flowrunner.ai/concepts/digital-andon-cord). An agent that stops and asks for a human decision is only as reliable as the channel carrying the question, and the failure mode of most alerting is not that the message was never sent, it is that it landed somewhere nobody was looking. InOut.bot sends to the phone in your pocket, tags each message with a type such as Urgent, Alarm or Reminder so it arrives with a matching emoji and title, and returns your remaining message balance in the send response so a flow can see when its own escalation path is running out. When WhatsApp is not enough, Make Phone Call places a real GSM call through the vendor's separate Phone Calls API and reads the message aloud with text to speech. Two rungs, both of them reaching one person on purpose. ### Without FlowRunner **Alerts land where you are not**: Notifications pile into an inbox or a channel you check when you get to it **Escalation has one speed**: Everything arrives the same way, so the urgent item looks like the routine one **Silence reads as approval**: A flow waiting on a person eventually proceeds, or stalls without telling anyone ### With FlowRunner **The question reaches your phone**: The ask arrives on WhatsApp on the number you carry, tagged with its own type and title **Escalation has a second rung**: No reply before the deadline turns the same question into a spoken phone call **Silence stops the line**: The held action does not proceed on its own, and the flow says so ## Use Case Scenarios ### The payment run that waits for you A weekly disbursement flow assembles the batch in [QuickBooks Online](https://flowrunner.ai/integrations/quickbooks-online) and checks it against the rules: no new payees, no amount above the standing threshold, no duplicate reference. Batches that pass every check post themselves. This one does not, because a payee added four days ago is receiving an unusually large first payment. The agent sends the whole picture to your WhatsApp with the type set to Urgent: what it wants to pay, to whom, why the check tripped, and what it already verified. The batch is held open in FlowRunner until you reply. This is the pattern the platform is built around, agents doing the assembly and the checking and a person owning the release, and this connector is simply the wire the question travels down. ### The house that tells you what it did A [Home Assistant](https://flowrunner.ai/integrations/home-assistant) automation reports that the garage door opened at an odd hour, and the camera step produces a still. The agent calls Send Media From URL with the image and a one line summary, or Send Media From Base64 when the image was generated inside the flow and never existed at a public URL. The alert arrives with the Alarm type, so it is visually distinct from the reminder that arrived an hour earlier. Nothing about this needs a dashboard. ### The incident that will not be slept through [Sentry](https://flowrunner.ai/integrations/sentry) fires on an error rate crossing its threshold. The agent enriches the event with the deploy that preceded it and the affected customer count, then sends it to WhatsApp. If no acknowledgement comes back within the window the flow is holding open, it escalates: Make Phone Call rings your number and reads the summary aloud, using the separate Phone Call API key configured for that purpose. A message can be missed while the phone is face down on a nightstand. A ringing phone is harder to miss, which is the entire reason the second rung exists. ## Human-in-Loop Highlight The gate on this connector is not the message, it is the escalation ladder, and the ladder is worth building deliberately because this API tells you when it is about to stop working. Send Message returns your remaining message balance alongside the delivery result. An agent that reads that balance knows something most alerting never knows: whether its own question will still arrive next time. So the pattern is to send the ask on WhatsApp with the Urgent type, hold the downstream action open, and treat two conditions as reasons to escalate rather than to proceed. No reply before the deadline triggers Make Phone Call, which reads the identical question aloud over GSM using a separate key that is not the WhatsApp one. A balance approaching zero triggers the same call, because the next attempt to reach you may not land at all. What the agent never does is take the held action because the question went unanswered. Silence is not consent, and on this channel the agent has enough information to tell the difference between "you have not answered yet" and "I can no longer reach you". Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via WhatsApp Human decides Agent resumes with decision ## Agent Capabilities 4 actions ### Messaging 3 - **Send Message** Sends a text message to your own connected WhatsApp number. The optional message type changes the emoji and title the message arrives with, which is how an Urgent decision request is made visually distinct from a routine Reminder. The response includes the delivery result and your remaining message balance, so a flow can check its own escalation path is still viable. - **Send Media From URL** Sends an image with a text message to your own connected number, fetched by InOut.bot from a publicly accessible URL. The API rejects files that exceed its size limit and reports the rejected size in kilobytes, so an agent can resize and retry rather than failing the step. - **Send Media From Base64** Sends an image with a text message with the file content embedded in the request as a Base64 string. Use it for images produced inside the flow, such as a rendered chart or a cropped camera frame, that never existed at a public URL. The same size limit and rejection behaviour applies. ### Phone Calls 1 - **Make Phone Call** Places a GSM phone call to the given number and reads the message aloud with text to speech, through the InOut.bot Phone Calls API. It requires the separate Phone Call API key in the service configuration, which is not the same key as the WhatsApp one. Voice language and style are optional and the available styles vary per language. This is the second rung of an escalation ladder, not a routine notification path. ## Frequently Asked Questions ### What can FlowRunner do with InOut Personal WhatsApp? FlowRunner agents can run Send Message, Send Media From URL, and Send Media From Base64 in InOut Personal WhatsApp, plus 1 more action. ### Does connecting InOut Personal WhatsApp to FlowRunner require OAuth? No. InOut Personal WhatsApp connects to FlowRunner with an API key, no OAuth flow required. ### Can InOut Personal WhatsApp trigger a FlowRunner workflow automatically? InOut Personal WhatsApp doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at InOut Personal WhatsApp?** This integration exposes InOut Personal WhatsApp to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/inout-personal-whatsapp. Site index: https://flowrunner.ai/llms.txt