Respond.io

Connect AI agents to Respond.io conversations. Agents send messages, open and close conversations, tag and comment on contacts, and update custom fields across every channel your customers write in on.

14 actions API key available

Respond.io website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A new order lands from the storefront

Get Contact looks the customer up by email or phone

Create Contact registers first-time buyers so they are reachable on their messaging channel

The agent checks whether the contact already has an open conversation with a human agent

If a conversation is open, the flow stops: Add Comment leaves the order context as an internal note, and the agent handling the thread decides whether the automated confirmation belongs in it

Send Message delivers the order confirmation on the contact's most recent channel when the lane is clear

Add Tags marks the contact as a paying customer and Update Custom Field records the order value

The team channel logs the touch, so outreach and support see one history

What This Integration Enables

Messaging channels are conversations, not broadcast lists, and the difference is state. An email campaign does not care what else is in the inbox; a WhatsApp thread does. Respond.io's model gets this right: contacts with conversation state, assignees, tags, and internal comments, unified across every channel a customer writes in on. FlowRunner agents work inside that model instead of around it. They message customers on the channel the customer chose, keep profiles current from the systems where events happen, and treat an open conversation as occupied territory. - Send text and attachment messages to a contact's most recent messaging channel from any workflow - Sync contacts from a CRM or database and keep profiles and custom fields current - Tag contacts and leave internal handoff notes as part of automated processes - Open and close conversations programmatically as tickets are created and resolved elsewhere - Look up workspace users to route and assign with real names, not guesses The connector's conversation-state awareness is what makes automation here safe at all: it is the difference between a system that helps the inbox and one the support team turns off.

Without FlowRunner

Channels answered in silos WhatsApp, web chat, and messenger threads live in different tabs, and context does not follow the customer

Automation talks over the conversation A bot blasts a promo into a thread where an agent is mid-refund, and the customer reads it as one company contradicting itself

Profile data goes stale on arrival What the CRM learns about a customer never reaches the tool where conversations happen

With FlowRunner

One contact, every channel Messages go out on the contact's most recent channel, and tags, fields, and notes ride on one profile

Automation respects the inbox state Open conversations are detected before any send, and a human decides what enters a live thread

Profiles sync as systems learn Custom fields update from orders, payments, and CRM changes the moment they happen

Use Case Scenarios

Order updates where the customer actually reads

A [Shopify](/integrations/shopify) order fires. The agent resolves the contact, sends the confirmation with Send Message on whatever channel the customer last used, tags them as a paying customer with Add Tags, and stamps the order value into a custom field with Update Custom Field. After a [Stripe](/integrations/stripe) payment, the same profile updates again and the transaction logs to [Google Sheets](/integrations/google-sheets). The customer gets updates where they already talk to you; the team gets a profile that reflects reality.

Escalation with a clean handoff

A conversation crosses the escalation threshold. The agent pulls CRM context from [HubSpot](/integrations/hubspot), creates the ticket in [Zendesk](/integrations/zendesk) with the thread's substance, and calls Add Comment to leave the handoff note where the next agent will look: what was promised, what is pending, where the ticket lives. Then Close Conversation clears it from the messaging inbox. Nothing about the customer's problem lives only in one person's memory.

New leads become reachable in minutes

When a lead lands in the CRM, the agent mirrors it with Create Contact, carrying name, language, and country so the first touch is properly localized, and posts to [Slack](/integrations/slack) that the contact is now reachable on messaging channels. When lifecycle changes happen upstream, Update Contact and Update Custom Field keep the messaging profile aligned, and Get Custom Fields lets any flow read what is already known before it acts.

Human-in-Loop Highlight

Delete Contact does not just remove a profile; it permanently deletes the contact and their entire conversation history, every channel, every thread, everything anyone ever promised them in writing. In a dedup or CRM-cleanup flow, that is the difference between merging records and erasing a relationship's paper trail. So FlowRunner agents never let a match score fire the deletion. When two profiles look like the same person, the agent lays out the evidence: this phone number and this email, these tags, this many conversations on each, last activity dates side by side. A person names which profile survives, the agent moves tags and custom field values across with Add Tags and Update Custom Field, leaves an Add Comment note recording the merge, and only then does Delete Contact run on the loser. The history that gets destroyed is history a human chose to let go.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

14 actions

Contacts

Get Contact Retrieves a contact by internal ID, email, or phone, returning the profile with name, assignee, lifecycle stage, tags, and custom fields. The lookup step before any message or update.
List Contacts Retrieves the workspace's contacts with cursor-based pagination, for sweeps and sync jobs.
Create Contact Creates a contact from an email or phone number, with optional name, language, country, profile picture, and custom fields. The step that makes a CRM lead reachable on messaging.
Update Contact Updates a contact's profile fields, changing only what is provided. The sync write behind profile hygiene.
Delete Contact Permanently deletes a contact and their conversation history. Cannot be undone, and the operation this page's human gate exists for.

Messaging and Conversations

Send Message Sends a text or attachment message (image, video, audio, or file by public URL) to a contact on their most recent messaging channel. Runs only after the open-conversation check.
Open Conversation Opens or reopens a contact's conversation so it appears in agents' inboxes. Used when an upstream event needs human attention on the thread.
Close Conversation Closes a contact's conversation as resolved, clearing it from open inboxes after a handoff or completed flow.

Tags and Notes

Add Tags Adds tags to a contact, creating unknown tags automatically. The segmentation write for flows that classify as they work.
Remove Tags Removes tags from a contact, ignoring tags not present. Keeps segments honest as states change.
Add Comment Leaves an internal note on a contact's conversation, visible to agents only. The handoff mechanism that moves context between automation and people.

Custom Fields

Get Custom Fields Retrieves a contact's custom field values by name. The read that lets flows act on what is already known.
Update Custom Field Sets one custom field value on a contact, for attributes like loyalty tier, order count, or preferences. The field must already exist in the workspace.

Workspace

List Users Retrieves the workspace's users with IDs, names, and emails, cursor-paginated. The lookup behind assignment and routing decisions.

Frequently Asked Questions

What can FlowRunner do with Respond.io?

FlowRunner agents can run Get Contact, List Contacts, and Create Contact in Respond.io, plus 11 more actions.

Does connecting Respond.io to FlowRunner require OAuth?

No. Respond.io connects to FlowRunner with an API key, no OAuth flow required.

Can Respond.io trigger a FlowRunner workflow automatically?

Respond.io doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Respond.io

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us