CRM Whats Pro
MessagingConnect AI agents to CRM Whats Pro, a Brazilian WhatsApp CRM built on a WhatsApp Web browser extension. Agents send text and media messages, verify numbers on WhatsApp, and read chats and conversation history so WhatsApp outreach and follow-up run without manual copying.
What This Integration Enables
CRM Whats Pro is honest about what it is, and that honesty is the reason to pick it. This is not Meta's official Business Platform. It is a browser extension that overlays WhatsApp Web with a CRM, and the API plane this connector talks to drives the channel that extension has paired. There is no approved template library, no 24 hour conversation window to reason about, and no Meta review queue. There is a real WhatsApp account, signed in, with a human on the other side of it. Connected accounts remain subject to WhatsApp's own terms, and the vendor gates the API module behind its premium plan. If you want the enterprise contract and the compliance surface, use an official gateway. If your sales team already lives in WhatsApp Web and the actual problem is that nothing they do there ever reaches the CRM, this is the connector built for that shape.
Agents get eight actions organized around a single object, which is the channel. Get Channel Status reports how many users are online and whether the channel can send at this moment, and it is a real pre-flight rather than a formality: with no online user the API rejects sends outright. Send Text Message and Send Media Message dispatch to one number at a time in international form, with @nome as the only merge variable the vendor publishes and an 11 MB ceiling that the connector enforces before anything is transmitted. Check WhatsApp Number resolves reachability through the same channel. List Chats, Get Chat and List Chat Messages page the session's conversations, and Download Media File decrypts an attachment out of a message record and stores it in FlowRunner file storage as a URL rather than pushing megabytes of base64 through the flow. Worth knowing before you design around it: the vendor publishes no schema for chat and message elements, so those collections are returned exactly as the API sends them, and any field your flow depends on is a field you confirmed by looking at a live response.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Follow ups that only fire when the channel is awake
A list of leads in Pipedrive has passed its follow up threshold. Before composing anything, the agent calls Get Channel Status. If no user is online, the run does not start and the rep gets a note instead of a queue of rejections. When the channel is live, the agent walks the list, calls Check WhatsApp Number on each one, and dispatches Send Text Message only to the numbers that came back reachable. The unreachable ones are flagged in the CRM for an email sequence instead of quietly consuming attention as WhatsApp leads that never answer.
Proof of delivery attached to the deal, not to a screenshot
A customer asks for a copy of the signed order form and the rep sends it in the thread. Later, finance wants it filed. The agent calls List Chat Messages for that chat, locates the message record carrying the attachment, and passes its seven encrypted media descriptors to Download Media File, which decrypts the file and stores it in FlowRunner file storage. The returned URL goes onto the deal record in the CRM. What used to be a screenshot pasted into a comment becomes a real file with a real link, and the rep never had to save it to a laptop first.
Media that fails locally instead of on the recipient's phone
Marketing publishes a new product sheet and the team wants it sent to a segment. The agent calls Send Media Message with the file supplied as a public URL and the correct extension so the recipient's WhatsApp renders it as a document rather than an unknown blob. The 11 MB ceiling is checked before the request leaves, so an oversized asset is refused as a clean automation exception with a name attached to it rather than as a vendor error code partway through the run. Marketing resizes the file once and the send goes out.
Human-in-Loop Highlight
The paired channel is not a shared inbox. It is a specific person's WhatsApp, and it contains threads with customers, threads with suppliers, and threads with people who are neither. List Chat Messages will hand an agent 500 messages per page of whatever is in a conversation. Download Media File will take an encrypted attachment out of that conversation, decrypt it, and put it in FlowRunner file storage where it becomes a URL with different retention and different access than WhatsApp had. That is a real movement of private material across a boundary, and the connector cannot help the agent judge it, because the vendor publishes no schema for chat and message elements at all. The arrays come back exactly as the API sends them, with no documented field to filter on, no sender role, no thread classification. An agent that cannot name the fields cannot decide which ones are safe to export. So it does not decide. When a flow is about to pull a thread's history or an attachment into the CRM, the agent posts the chat identifier, the message count, and the file name and size it is proposing to extract. Then it asks the rep who owns that account: "This thread has 1,204 messages and one attachment named contrato-final.pdf. Import the attachment and the last 20 messages onto the deal, import the attachment only, or skip this thread?" The rep answers, and only then does anything leave WhatsApp. That is human-in-the-loop placed where the judgment actually lives, which is with the person whose conversation it is.
Agent Capabilities
8 actionsMessaging
2- Send Text Message Sends a WhatsApp text message from the connected channel to a single number given in international form with no punctuation. The literal variable `@nome` inside the message is replaced with the contact's own WhatsApp display name, and it is the only merge variable the vendor publishes. Requires a paired channel with a user currently online, so pair it with Get Channel Status at the top of any run.
- Send Media Message Sends an image, video, audio file or document to a single number with an optional caption. Supply the file either as a base64 string or as a public URL the vendor downloads, exactly one of the two, and give the file extension so the recipient's WhatsApp renders the correct media type. Media is capped at 11 MB and an oversized base64 payload is rejected locally before any request is made.
Channel
1- Get Channel Status Reports whether the WhatsApp channel behind this token is ready to send, returning the number of users currently online and whether sending is possible right now. Used as the pre-flight check at the start of a batch, because a channel with no online user rejects every send and the rejection looks the same as a bad number.
Contacts
1- Check WhatsApp Number Checks whether a phone number has a WhatsApp account before a flow dispatches to it, returning a valid flag alongside the vendor's own message. The check runs through the connected channel, so it needs the channel online too. Used to split a lead list into a WhatsApp track and an email track before either one costs anything.
Chats
3- List Chats Lists the conversations held by the connected channel, 200 per page, with independent toggles for including group chats and archived chats. The response carries the current page and the total page count so a flow can loop to the end. Chat elements are returned exactly as the API sends them, because the vendor publishes no schema for them.
- Get Chat Retrieves the full record of a single chat by its WhatsApp identifier, for example `[email protected]` for an individual conversation. Identifiers come from List Chats or the chat picker. The chat object is returned exactly as the API sends it, for the same reason.
- List Chat Messages Lists the messages of one conversation, 500 per page, in the order the API returns them, with the current page and total page count so a flow can walk a long history. This is the action that reads what was actually said, and it is the one that belongs behind a human decision when the thread is a person's own rather than a shared queue.
Media
1- Download Media File Decrypts a WhatsApp media attachment and stores it in FlowRunner file storage, returning a URL the rest of the flow can use. It needs the seven encrypted media descriptors that come from a message record returned by List Chat Messages: media key, file hash, mime type, media type, size, direct path and the legacy MMS URL. The base64 payload is decoded and uploaded rather than returned, so a large attachment never travels through the flow as text.
Frequently Asked Questions
What can FlowRunner do with CRM Whats Pro?
FlowRunner agents can run Send Text Message, Send Media Message, and Get Channel Status in CRM Whats Pro, plus 5 more actions.
Does connecting CRM Whats Pro to FlowRunner require OAuth?
No. CRM Whats Pro connects to FlowRunner with an API key, no OAuth flow required.
Can CRM Whats Pro trigger a FlowRunner workflow automatically?
CRM Whats Pro doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with CRM Whats Pro
$100 in credits. No card required. Connect in minutes.