Pingmee
MessagingList and inspect conversations and send messages through Pingmee, a business messaging platform built around customer conversations. Agents handle routine threads and escalate the ones that need a person.
What This Integration Enables
Pingmee is built around the conversation object, and one property on that object makes this connector unusual: answer mode. Every conversation carries an explicit statement of who is replying, the workflow bot, a human agent, or the AI agent, and Set Conversation Answer Mode changes it. Most messaging platforms leave the handover implicit, a social convention enforced by whoever is watching the inbox. Pingmee makes it a field you can read and write, which means an automation can actually reason about it.
That matters more than it sounds, because a handover you cannot express is a handover you cannot govern. FlowRunner's whole argument is that agents should do the work and stop at the decisions that carry risk, and a platform that treats "a person is handling this now" as first-class data lets an agent enforce that rather than hope for it. Around the answer mode sit the operations that make a handover useful. Conversations move through Open, Closed and Standby. Agents are assigned and unassigned by email address, and conversation tags drive routing and reporting. Sends cover both templates and free-form messages, inside and outside the WhatsApp customer service window. A bot workflow can be started for one specific conversation, from a particular node, with trigger data attached. The API is split across microservices on separate hosts, all of which expect the same two credentials, a business API key and a personal access token, and neither works alone. FlowRunner's connectors are built and verified against each vendor's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Escalation that carries its context with it
On New Message fires and the agent reads the exchange with Get Messages. It detects a cancellation request, which is outside what the AI agent is scoped to handle. Rather than letting the assistant improvise, the agent applies a cancellation tag with Assign Tags To Conversation, assigns the retention specialist with Assign Agents To Conversation, and switches the thread to manual handling with Set Conversation Answer Mode. It then posts the conversation summary, the customer's plan from HubSpot and the reason for escalation into the retention channel. The specialist opens a thread that has already been prepared for them.
Order notifications inside the window rules
An order status changes in Shopify. The agent calls List Phone Numbers to resolve the business number, List Templates to find the template ID, and Send Template Message with body parameters in the order the placeholders appear. If the customer replies, On New Message fires with the customer service window now open, and the agent switches to Send Message for the rest of the exchange. When the thread reaches a natural end, Set Conversation Status closes it and Assign Tags To Conversation records the outcome so the next report has something to count.
Closing the loop from a downstream system
A refund completes in the finance system. The agent finds the originating thread through List Conversations, calls Trigger Workflow to start the confirmation bot workflow for that conversation with the refund reference passed as trigger data, and then Set Conversation Status to close the thread once the workflow reports back. The customer gets a confirmation from the same conversation they raised the issue in, rather than an email from a system they have never interacted with.
Human-in-Loop Highlight
Because Pingmee makes answer mode settable, an agent can take a person out of a conversation exactly as easily as it can put one in. Those two directions are not symmetrical, and treating them as though they were is the mistake this gate exists to prevent.
Switching a thread to Manual runs unattended, always. Escalating to a person never needs approval, and an agent that asks permission to fetch a human has misunderstood its job. The gated direction is the return: Set Conversation Answer Mode back to AI or Bot on a conversation a person is currently handling. The customer receives no notice that this happened. Their next message goes to a different kind of correspondent in the middle of a conversation they believed they were having with a person, and if the assistant then answers a question the specialist was carefully working around, the damage is already in the transcript.
So the agent assembles the case and asks the assigned specialist directly. It reads the current mode and assignments with Get Conversation, pulls the recent exchange with Get Messages, and sends: "The thread with this customer has been quiet since your last reply. Return it to AI handling, park it in Standby, or keep it manual?" The specialist answers in one tap and the agent applies whichever mode they chose. The same rule covers Update AI Agent, where roles must be supplied as the complete list rather than a delta and any changed role has its function tool regenerated, so a partial update silently drops the roles you did not resend and changes behaviour across every conversation at once. Escalation is free. De-escalation is a decision. That asymmetry is the practical shape of human-in-the-loop, and this connector is one of the few that lets you encode it directly.
Agent Capabilities
31 actionsConversations
9- List Conversations Retrieves a page of conversations using cursor-based pagination, optionally narrowed to one business phone number. Each carries the customer profile, last message, unread count, status and answer mode. Pass the lastEvaluatedKey back as Start Key to continue paging.
- Get Conversation Retrieves a single conversation by its participant identifiers, returning the customer profile, last message, assigned agents and tags, unread count, status and AI settings. The identifier combines the business and customer phone number IDs and must be URL encoded.
- Set Conversation Status Moves a conversation to Open, Closed or Standby. Used to close a thread once handling is finished, or to park it while waiting on the customer rather than leaving it open in a queue.
- Set Conversation Answer Mode Controls who replies in a conversation: the workflow bot, a human agent, or the AI agent. Switching to Manual hands the thread to a person and needs no approval. Switching back is the direction that belongs behind one.
- Assign Agents To Conversation Associates one or more human agents with a conversation so it appears in their queue. Agents are identified by their email address, which is their agent ID.
- Unassign Agents From Conversation Removes one or more human agents from a conversation, taking it out of their queue.
- Get Conversation Tags Returns the IDs of the tags currently on a conversation. Resolve them to titles and colours with the tag list operation.
- Assign Tags To Conversation Adds one or more existing tags to a conversation for routing, reporting or to trigger downstream automation. The tags must already exist on the account.
- Remove Tags From Conversation Removes one or more tags from a conversation. The response lists any that could not be removed and is empty when every removal succeeded.
Messages
3- Send Message Sends a free-form message into an existing conversation on WhatsApp, Instagram or Facebook Messenger, optionally quoting an earlier WhatsApp message. WhatsApp only allows free-form sends inside the customer service window.
- Get Messages Retrieves a batch of messages for a conversation, newest first, paging backwards through history with the returned key. Used to give a person or an AI step the exchange before either acts on it.
- Send Template Message Sends an approved WhatsApp template, the only way to open a conversation outside the 24 hour customer service window. Body parameters are supplied in the order the placeholders appear, with an optional image, video or document header.
Business
2- List Phone Numbers Retrieves the WhatsApp business phone numbers on the account with their ID, verified business name and display number. These IDs are what the other operations expect.
- List Templates Retrieves the WhatsApp templates available on a business phone number with each template's ID and name. Read it to resolve the template ID a send needs.
Customers
5- List Customers Retrieves a page of customers using cursor-based pagination, returning name, nickname, email, platform, country code and activity timestamps.
- Get Customer Retrieves a single customer by phone number ID, returning profile image, names, email, platform and last activity timestamp.
- Create Customer Creates a customer record. When no profile image is supplied Pingmee attempts to resolve one automatically. The phone number ID must include the country code.
- Update Customer Applies a partial update, changing only the fields supplied. Nickname, email, description and the business-controlled phone number are editable; the platform-sourced customer name is not.
- Delete Customer Permanently deletes a customer record by phone number ID, removing their profile data from the business.
Tags
4- List Conversation Tags Retrieves every conversation tag defined on the account with its ID, title and colour.
- Get Conversation Tag Retrieves a single tag by ID with its title, colour and owning business.
- Create Conversation Tag Creates a tag that can then be assigned to conversations for routing and reporting. You choose the tag ID yourself, so keep it short and stable since other operations reference it.
- Delete Conversation Tag Deletes a tag by ID. Removing a tag also removes it from every conversation it was assigned to, which makes it a wider change than it looks.
Agents
2- List Agents Retrieves the human agents on the account with their email identifier, display name and type. These are the identifiers assignment accepts.
- Get Agent Retrieves a single human agent by email identifier.
AI Agents
3- List AI Agents Retrieves a paginated list of the business's AI agents with their roles, activity flag and token usage. Enable the file option only when the vector store contents are actually needed, since it makes the response considerably larger.
- Get AI Agent Retrieves a single AI agent by ID including its description, roles with their instructions and webhooks, and vector store files where available.
- Update AI Agent Updates an AI agent's name, description, roles or vector store requirement. Roles must be supplied as the complete list rather than a delta, and any changed role has its function tool regenerated, so a partial update drops what it does not resend.
Workflows
2- List Workflows Retrieves the bot workflows defined on the business with each workflow's ID and name.
- Trigger Workflow Manually starts a bot workflow for a specific conversation, optionally from a particular node and with a JSON payload the workflow reads as trigger data. This is how an event in another system resumes a conversation where it left off.
Webhooks
1- List Webhooks Retrieves every webhook subscription on the account with its ID, callback URL and subscribed event, including the ones this connector's triggers create. Useful for auditing which endpoints Pingmee notifies.
Triggers
4 triggersEvent Triggers
4- On New Conversation Fires when a customer starts a new conversation with the business, using a webhook subscribed to the conversation created event. The entry point for intake routing, tagging and first-response automation.
- On New Message Fires when a message is created in any conversation, inbound or outbound. This is the usual entry point for message-driven work, and because it covers outbound messages too, a flow can react to what a human agent said as well as what the customer did.
- On Conversation Status Updated Fires when a conversation moves between Open, Closed and Standby, so a flow can act when an agent closes or parks a thread. Used to kick off post-resolution surveys, quality scoring or downstream ticket closure.
- On Conversation Tags Updated Fires when tags are added to or removed from a conversation. Convenient for routing a thread the moment a human labels it, which turns the tag into an instruction rather than a note.
Frequently Asked Questions
What can FlowRunner do with Pingmee?
FlowRunner agents can run List Conversations, Get Conversation, and Set Conversation Status in Pingmee, plus 28 more actions.
Does connecting Pingmee to FlowRunner require OAuth?
No. Pingmee connects to FlowRunner with an API key, no OAuth flow required.
Can Pingmee trigger a FlowRunner workflow automatically?
Yes. Pingmee supports 4 triggers that can start a FlowRunner workflow automatically.
Start building with Pingmee
$100 in credits. No card required. Connect in minutes.