--- title: "360Messenger Integration" description: "Connect AI agents to 360Messenger, a WhatsApp HTTP API. Agents send text and file messages to numbers and groups, read sent and received message queues, administer groups and labels, and manage chats and contacts so WhatsApp outreach and follow up run automatically." url: https://flowrunner.ai/integrations/whatsapp-360messenger date_modified: 2026-08-12T15:40:33-07:00 --- # 360Messenger [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Connect AI agents to 360Messenger, a WhatsApp HTTP API. Agents send text and file messages to numbers and groups, read sent and received message queues, administer groups and labels, and manage chats and contacts so WhatsApp outreach and follow up run automatically. 81 actions · API key · available [360Messenger website](https://360messenger.com/) · [Platform Documentation](https://360messenger.com) · Capability data verified 2026-08-12 1. A polling schedule runs every few minutes, because this API publishes no event payload and holds one webhook slot 2. Agent calls Get Received Messages and reads everything that arrived since the last cursor 3. Agent runs Is Registered User and Get Number ID on any sender it does not recognize 4. Agent answers with Send Message and records the chat and message identifier pair the API uses to address a message 5. Agent calls Get Message Info for WhatsApp's own per-recipient delivery and read receipts, not just the queueing state 6. Agent posts the day's unanswered threads into the sales channel with the last inbound line from each 7. Before any scheduled batch goes out, a person confirms the send date, because the vendor's date format and its own example do not agree on which number is the month ## What This Integration Enables 360Messenger is a WhatsApp HTTP API operated by a vendor registered in India, and it is worth being precise about which company it is. Searching for its API returns documentation for 360dialog, an official Meta Business Solution Provider registered in Germany with a different host and a different authentication header. They are unrelated. This connector authenticates to 360messenger.com with a Bearer key, and the key belongs to one WhatsApp service in the vendor's panel, so one FlowRunner connection reaches one number. Access is unofficial: the account is linked as a device rather than provisioned through Meta's Cloud API, and connected accounts remain subject to WhatsApp's terms. What makes this connector distinct in a crowded field is that it exposes plumbing the others hide. Sent, received and pending are three separate reads rather than one blended history, so a message that the vendor queued but never dispatched is visible as exactly that. Get Message Status answers the vendor's question, what happened to what I submitted, while Get Message Info answers WhatsApp's, whether the recipient received and read it. And the service's own delivery behavior is under your control through actions rather than through a dashboard: auto-seen, whether inbound messages are collected at all, country code handling, the default country code, and the outbound rate limit. There is no trigger, and the reason is stated rather than glossed over: the vendor publishes no payload shape for its webhook, and the account holds a single webhook URL that registering ours would silently take from whatever the customer already points at their own systems. Inbound is read by polling instead, which is slower and honest. ### Without FlowRunner **Inbound read on a phone**: Somebody scrolls WhatsApp on a handset to find out which prospects replied overnight **Queue state invisible**: A message that was submitted but never dispatched looks identical to one that was delivered **Scheduling trusted blind**: A scheduled send is set from a documented format that nobody has actually tested against the platform ### With FlowRunner **Inbound read on a schedule**: Get Received Messages is swept on a cadence and every new message enters the same queue **Three queues read separately**: Sent, received and pending are distinct reads, so a stuck message is visible as a stuck message **Scheduling proven before it is used**: One test send is dispatched and its actual delivery time is read back before a batch is committed ## Use Case Scenarios ### Overnight replies turned into a morning queue An outbound team works prospects over WhatsApp. Every ten minutes an agent sweeps Get Received Messages, filters to threads it started, and classifies each reply into interested, not now, wrong person or unsubscribe. Interested replies get an answer from Send Message and a note written to [Pipedrive](https://flowrunner.ai/integrations/pipedrive). Unsubscribes are marked in the CRM first and only then acted on in WhatsApp. Anything the classifier is unsure about is left untouched and posted to [Slack](https://flowrunner.ai/integrations/slack) with the thread pulled from Fetch Chat Messages, so the rep reads what the prospect actually wrote rather than a summary of it. These are the [automation exceptions](https://flowrunner.ai/concepts/automation-exceptions) worth a person's attention, and everything else has already been handled by the time anyone opens a laptop. ### A stuck message treated as a stuck message A billing reminder flow submits messages through Send Message and stores the chat and message identifier pair for each. A later sweep reads Get Pending Messages. Anything still pending past a threshold is not resent, because a duplicate reminder about money is worse than a late one. Instead the agent reads Get Session State to establish whether the linked number is even connected, and Get Service Settings to check whether the rate limit is throttling the queue. If the session is down, the agent stops the flow, writes the affected account list to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and escalates. The rest of the queue waits rather than piling into a backlog nobody knows exists. ### Group operations for a customer cohort An onboarding cohort is run as a WhatsApp group. The agent creates it with Create Group, sets the subject and description, restricts posting during the first session with Set Group Messages Admins Only, and shares the link from Get Group Invite Link with the enrolled list. It removes participants who churn with Remove Group Participants, promotes the customer's own lead with Promote Group Participants, and rotates the link with Revoke Group Invite Link at the end of each cohort so the previous group's link stops admitting people. Group membership is reconciled against the enrollment record every night, and any mismatch is reported rather than silently corrected. ## Human-in-Loop Highlight The gate on this connector is a date. Send Message takes a delay value that the vendor documents as `MM-DD-YYYY HH:MM` in GMT, while the vendor's own example value in the same collection is `01-12-2025 09:29`, which does not disambiguate the day from the month. The connector repeats the vendor's format claim rather than quietly picking an interpretation, because picking one and being wrong is the failure mode nobody catches. A January reminder that lands in December, and a December promotion that lands in January, are both successful API calls with a queued message behind them. The vendor's cron also runs on a fixed interval, so the actual send falls on the next tick after whatever time was understood. So the agent does not schedule a batch on documentation. It schedules exactly one message to an internal number a few minutes out, waits, reads the real delivery time back from Get Sent Messages, and posts the evidence to the operations channel: "Scheduled a test for 2026-08-14 09:20 using `08-14-2026 09:20`. It delivered at 09:30 on 14 August, so the format reads as month first and delivery lands on the next ten-minute tick. The 2,400-message batch is queued behind this approval. Commit, or send unscheduled?" A person answers once, the interpretation is recorded, and the batch goes. That is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) doing what a retry never could: an agent cannot resolve a contradiction between a vendor's specification and a vendor's example, but it can prove which one holds and hand a person a decision with the answer already attached. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 81 actions ### Messaging 15 - **Send Message** Sends a text or file message to a number. This is also the scheduling path: supplying a delay value queues the message for later delivery rather than dispatching it now. - **Send Group Message** Sends a text or file message to a group rather than a number. - **Get Message Status** Returns the vendor's queueing state for something submitted through this API. Used to tell a message that is waiting from a message that failed. - **Get Sent Messages** Returns messages the connected number has sent, including scheduled ones once they land. The read that proves what actually went out and when. - **Get Received Messages** Returns inbound messages. With no trigger available on this API, this is the action a polling flow sweeps. - **Get Pending Messages** Returns messages accepted but not yet dispatched. Used to spot a queue that has stopped moving before customers do. - **Forward Message** Forwards an existing message to another chat. - **Reply To Message** Sends a message as a threaded reply to a specific earlier message, which keeps a long thread legible for the recipient. - **React To Message** Adds an emoji reaction to a message. - **Star Message** Stars a message on the linked account so a human reviewer can find it in WhatsApp later. - **Unstar Message** Removes a star. - **Get Quoted Message** Returns the message that a reply quoted, which is how an agent recovers the context a one-word answer refers to. - **Get Message Info** Returns WhatsApp's own per-recipient delivery and read receipts, a different question from the vendor's queue state. - **Get Media Download URL** Returns a download URL for media on a message. - **Download Media File** Decodes the media payload and writes it to FlowRunner file storage. A message with no attachment fails loudly rather than producing a zero-byte file behind a URL that looks like a successful download. ### Groups 15 - **Get Group List** Lists the groups the connected number belongs to. - **Create Group** Creates a group seeded with participants. - **Leave Group** Leaves a group. - **Add Group Participants** Adds participants. An empty list is refused before any request is issued. - **Remove Group Participants** Removes participants, with the same empty-list guard. - **Promote Group Participants** Promotes participants to admin. - **Demote Group Participants** Demotes admins back to participants. - **Set Group Subject** Sets the group name. - **Set Group Description** Sets the group description. - **Set Group Picture** Sets the group image. - **Delete Group Picture** Clears the group image. - **Set Group Messages Admins Only** Restricts posting to admins. Used to run a broadcast-style session inside a group without muting it permanently. - **Set Group Info Admins Only** Restricts who may edit the group's name, description and image. - **Get Group Invite Link** Returns the current invite link. - **Revoke Group Invite Link** Invalidates the current link and issues a new one. The right response to a link that has traveled further than intended. ### Chats 7 - **Fetch Chat Messages** Returns the message history of one chat. Used to assemble the context a reply needs before composing it. - **Send Typing State** Shows a typing indicator. It persists until cleared or superseded by a message, so pair it with Clear Chat State in any flow that might not follow through. - **Send Recording State** Shows a recording indicator, with the same persistence behavior. - **Clear Chat State** Clears a typing or recording indicator. - **Delete Chat** Removes the chat from the connected account. - **Clear Chat Messages** Clears the messages in a chat while keeping the chat itself. - **Get Chat Contact** Returns the contact behind a chat. ### Client and Session 28 - **Get Chats** Lists chats on the connected account. - **Get Contacts** Lists contacts on the connected account. - **Get Session State** Reports whether the linked WhatsApp session is connected. The first thing to check when a queue stops draining. - **Search Messages** Searches message history by text. - **Is Registered User** Confirms whether a number has a WhatsApp account, before a flow spends a send on it. - **Get Number ID** Returns the platform identifier for a number. - **Mark Chat Unread** Marks a chat unread so a human picking up the inbox sees it. - **Send Seen** Marks a chat as seen. - **Pin Chat** Pins a chat to the top of the list. - **Unpin Chat** Unpins a chat. - **Mute Chat** Mutes notifications for a chat. - **Unmute Chat** Unmutes a chat. - **Archive Chat** Archives a chat. - **Unarchive Chat** Restores an archived chat. - **Get Blocked Contacts** Lists blocked numbers. Used before outreach so a blocked number is never mistaken for an unresponsive one. - **Get Common Groups** Returns groups shared with a contact. - **Get Invite Info** Reads a group's details from an invite link before joining. - **Accept Invite** Joins a group from an invite. - **Set Status** Sets the connected account's status text. - **Set Profile Picture** Sets the connected account's profile image. - **Get Profile Picture URL** Returns a profile image URL. - **Get Chat By ID** Returns one chat by identifier. - **Get Contact By ID** Returns one contact by identifier. - **Get Label By ID** Returns one WhatsApp Business label. - **Get Chat Labels** Returns the labels currently on a chat. Always read this before writing labels. - **Set Chat Labels** Applies a label list to chats. It replaces rather than adds, so a label already on a chat but absent from the list is removed, which is why the read above matters. - **Set Presence Available** Sets the connected account as available. - **Set Presence Unavailable** Sets the connected account as unavailable. ### Contacts 6 - **Get Contact About** Returns a contact's About text. - **Get Contact Profile Picture URL** Returns a contact's profile image URL. - **Block Contact** Blocks a number on the connected account. - **Unblock Contact** Unblocks a number. - **Get Formatted Number** Returns a number in the platform's normalized form, which is what every other action expects. - **Get Contact Chat** Returns the chat for a contact. ### Service Settings 6 - **Get Service Settings** Returns the service's current delivery behavior. Read this before changing anything, because these settings apply to the whole number. - **Set Auto-Seen** Turns automatic read receipts on or off for the connected number. - **Set Message Receiving** Controls whether inbound messages are collected at all. Turning this off makes Get Received Messages return nothing, which reads exactly like a quiet day. - **Set Country Code Handling** Controls how the service interprets numbers supplied without a country code. - **Set Default Country Code** Sets the country code applied when one is missing. - **Set Message Rate Limit** Sets the outbound pacing for the number. The lever that keeps a bulk run looking like a business rather than a burst. ### Webhooks 4 - **Set Webhook** Points the account's single webhook slot at a URL you control. Because there is one slot, this replaces whatever was registered before. - **Remove Webhook** Clears the webhook slot. - **Get Pending Webhook Deliveries** Lists deliveries the vendor has queued but not confirmed. - **Resend Webhook Deliveries** Replays queued deliveries to the registered endpoint. ## Frequently Asked Questions ### What can FlowRunner do with 360Messenger? FlowRunner agents can run Send Message, Send Group Message, and Get Message Status in 360Messenger, plus 78 more actions. ### Does connecting 360Messenger to FlowRunner require OAuth? No. 360Messenger connects to FlowRunner with an API key, no OAuth flow required. ### Can 360Messenger trigger a FlowRunner workflow automatically? 360Messenger doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at 360Messenger?** This integration exposes 360Messenger 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/whatsapp-360messenger. Site index: https://flowrunner.ai/llms.txt