Connverz
MessagingWork with a Connverz omnichannel messaging account on the Convrs platform, sending WhatsApp template messages and SMS. Agents manage conversations across channels and keep contact records aligned.
What This Integration Enables
Connverz, running on the Convrs platform, treats the person as the record rather than the thread. That shows up everywhere in its API. There is no assign action and no close action, because the conversation is not the object you manipulate. What you manipulate is the user: their name, email, phone, notes, custom data and tags, each with its own dedicated setter. Conversations are things you read. Reports are things you run. The write surface is deliberately narrow and it points at the customer profile.
That makes it a good fit for teams who want messaging to behave like an operational system of record rather than a chat window. An agent can keep the Connverz user in step with a CRM, tag people from events that happened somewhere else entirely, pull closed-conversation transcripts into a quality pipeline, and run any of the platform's built-in analytics reports on a schedule. The API is command based, so every call is a single POST carrying a command name, and errors come back on HTTP 200 rather than as HTTP failures. The FlowRunner connector surfaces those as real action errors, which means a failed write stops the flow instead of quietly passing. That is the kind of detail that decides whether an automation can be trusted to run unattended, and it is also why the writes that cannot be walked back get a person on them. FlowRunner's connectors are built and verified against each vendor's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Closed conversations into a quality pipeline
On Closed Conversation fires each time an agent completes a thread, carrying the conversation ID, user, bot, agent and the flat list of messages exchanged. The agent loads the transcript into Snowflake or BigQuery, scores it against the team's quality rubric with an AI step, and writes the score back onto the customer with Set User Data. Because closed-conversation history is limited to a 90 day window, the flow is also the archive: transcripts captured by the pipeline outlive what the platform will hand back later.
Order events into approved WhatsApp templates
An order status changes in the commerce backend. The agent calls Get WhatsApp Template first to inspect the approved template's components and placeholder count, fills the body parameters, and sends with Send WhatsApp Template. It then polls Get Message Details, whose ack code distinguishes sent, delivered, read and, usefully, whether the customer replied to the template at all. A reply routes the thread to a person. Silence after several days routes it to a follow-up sequence. The delivery status is treated as information, not as a receipt to file away.
Scheduled reporting without the dashboard
Every Monday the agent calls Get Report against the report IDs the operations lead cares about, over a rolling window inside the 90 day maximum, and posts the results into Slack with the week-over-week movement highlighted. Report requests are limited to ten per minute per token, so the flow paces itself rather than firing everything at once. When a metric moves outside the band the lead set, the agent does not just post the number. It flags the specific report and asks whether to open an investigation.
Human-in-Loop Highlight
Set User Phone is a one-line write with a blast radius that nothing else on this connector matches. The phone number stored on a Connverz user is the address every future WhatsApp template and SMS resolves to. Change it and the conversation does not break, which is the problem: it continues, to somebody else. A CRM sync that overwrites a stale-looking number can silently re-point a customer's entire messaging history to whoever holds that number now. So the agent gathers evidence rather than applying the change. It reads the current value with Get User, checks how recently that number was actually in use with Get Conversation, and posts to the operations channel: "CRM has a different mobile for user 88213. Connverz currently holds the number the customer last messaged from; the CRM value has never been seen on this account. Apply Set User Phone, keep the current number, or open a ticket for the account owner?" Everything else in the sync runs unattended. Name, email, notes and tags are all correctable in one call. The identity write is the one that stops the line and asks, which is exactly the behaviour a digital andon cord is supposed to produce.
Agent Capabilities
21 actionsUsers
7- Get User Retrieves a single user by ID, returning the profile fields the platform stores: name, email, phone, channel, language, creation date, notes and dashboard URL. Used as the comparison step before any profile write.
- Get Users Retrieves up to 5000 users, optionally filtered to a single bot or to users created after a given date. Used for bulk reconciliation against a CRM.
- Set User Data Stores custom key-value data on a user and can optionally trigger a flow route for that user after the update. New keys merge with existing data by default; enabling overwrite replaces everything stored, so the merge behaviour is worth being deliberate about.
- Set User Name Sets the full display name stored on a user profile.
- Set User Email Sets the email address stored on a user profile.
- Set User Phone Sets the phone number stored on a user profile. This is the address future WhatsApp and SMS sends resolve to, which is why it belongs behind a human decision rather than inside an unattended sync.
- Set User Notes Sets the free-text notes on a user profile, visible to agents in the dashboard. Used to push account context from the CRM to the person who will answer the next message.
Tags
4- Get User Tags Retrieves all tags currently assigned to a user. Used to check state before adding or removing membership.
- Add User Tag Assigns an existing tag to a user. The tag must already be defined in the workspace.
- Remove User Tag Removes a tag from a user while leaving the tag definition in place.
- Create Tag Creates a new tag definition in the workspace with an optional colour and description. The response reports 1 when the tag was created and 0 when it already existed, which makes the call safe to repeat.
Conversations
3- Get Conversation Retrieves the full chat message history for a single user across their channel. Used to give a person or an AI step the context behind a decision.
- Get Closed Conversations Retrieves completed conversations within a date range as a flat list of message rows carrying conversation, user, message, sender, timestamp, agent and bot. The maximum range is 90 days, which makes a scheduled export the practical archive.
- Get Open Conversations Retrieves all currently active conversations with agent, bot, start time and per-side message counts. Used for live queue monitoring and staffing alerts.
Messaging
6- Send WhatsApp Template Sends a pre-approved WhatsApp template to a phone number through a WhatsApp bot, with optional body parameters, header component and delivery-status webhook. This is the only way to open a WhatsApp conversation outside the customer service window.
- Get WhatsApp Template Retrieves the cached structure of an approved template, including its status and components, so placeholder counts and header requirements can be checked before a send rather than after a failure.
- Send SMS Message Sends an SMS to a phone number through an SMS bot. Rate limited to one message per second per mobile number and ten per second per token, so bulk flows need to pace themselves.
- Send Text Message Sends a text message to an existing user by user ID on their own channel, currently supported for Telegram users.
- Send Routed Message Sends a message to a phone number using routing logic configured on the Connverz server, optionally attaching custom user data. The server-side route decides which channel and which flow handle the message.
- Get Message Details Retrieves the delivery status of a previously sent message. The ack code separates sent, delivered and read, and reports both that the recipient is not on WhatsApp and that they replied to the template, which is more useful for branching than a plain delivery flag.
Reports
1- Get Report Runs one of the platform's built-in analytics reports, covering volume, agent, user, WhatsApp, AI, sales and executive views, over a date range of up to 90 days. Report-dependent filters are merged into the query. Rate limited to ten requests per minute per token.
Triggers
2 triggersEvent Triggers
2- On New User Fires when a new user is created, optionally limited to a single bot. The first run records a baseline and emits nothing, so pre-existing users are never replayed into a live flow. Afterwards each newly created user fires once, de-duplicated by user ID. Polling interval is configurable with a 30 second minimum.
- On Closed Conversation Fires when an agent-user conversation is completed, carrying the conversation ID, user, bot, agent and the flat list of messages exchanged. Like the user trigger, the first run establishes a baseline and emits nothing. This is the entry point for quality scoring, transcript archiving and post-resolution follow-up. Connverz posts webhook events to a single dashboard-configured URL and its API has no webhook create or delete command, so both triggers poll the documented list endpoints instead.
Frequently Asked Questions
What can FlowRunner do with Connverz?
FlowRunner agents can run Get User, Get Users, and Set User Data in Connverz, plus 18 more actions.
Does connecting Connverz to FlowRunner require OAuth?
No. Connverz connects to FlowRunner with an API key, no OAuth flow required.
Can Connverz trigger a FlowRunner workflow automatically?
Yes. Connverz supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with Connverz
$100 in credits. No card required. Connect in minutes.