Integration · SMS and messaging
AI agents for respond.io
Message customers on WhatsApp, Messenger, Instagram, Telegram, LINE, Viber, SMS or email through respond.io.
- Actions
- 10
- Read
- 3
- Write
- 7
Actions
What your agents can do in respond.io
Message customers on WhatsApp, Messenger, Instagram, Telegram, LINE, Viber, SMS or email through respond.io: send texts, files and WhatsApp templates, read a contact's message history, find, create and tag contacts, assign or close conversations, and leave internal comments for the team.
Read 3
Look things up. Nothing changes.
Get a contact
Reads one contact by ID, email or phone: id, firstName, lastName, phone, email, language, countryCode, custom_fields (name and value), tags, lifecycle, conversation status.
Search contacts
Searches the workspace's contacts by name, phone or email text, newest first.
List a contact's messages
Lists a contact's messages, newest first, at items[].
Write 7
Create, change or send.
Create or update a contact
Creates the contact named by email or phone, or updates it when it exists.
Tag a contact
Adds tags to a contact (up to 10 a call); tags that do not exist yet are created.
Send a message
Sends a message to a contact on a channel: the given channel ID, or the contact's last-interacted channel.
Send a WhatsApp template
Sends an approved WhatsApp template to a contact, which is how a business starts a WhatsApp conversation or writes after the 24-hour window.
Assign a conversation
Assigns a contact's open conversation to a workspace user, by the user's email or ID.
Open or close a conversation
Opens or closes a contact's conversation.
Add an internal comment
Adds an internal comment to a contact's conversation, seen by the team only, never sent to the customer.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your respond.io account.
What you enter
- Access token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your respond.io data
Ask a question in plain words. The agent can get a contact, search contacts or list a contact's messages in respond.io, then answers with what it found.
- 02
Let an agent update respond.io
Have the agent create or update a contact or tag a contact in respond.io as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Work from your CRM
Give one agent HubSpot and respond.io: it can search contacts in HubSpot and create or update a contact in respond.io in the same run.
FAQ
respond.io and MyDeepAgents
Can MyDeepAgents connect to respond.io?
Yes. The respond.io connector has 10 actions: 3 read and 7 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect respond.io?
Paste an API key from your respond.io account. You'll need: Access token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in respond.io without asking?
Only if you let it. Each of the 7 actions that change data can be set to wait for a person's approval before it runs.
Can I use respond.io in workflows as well as agents?
Yes. Every respond.io action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put respond.io to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.