Integration · Sell and serve

Reply.io and Meteor AI agents

Connect Reply.io to a WhatsApp Met: search contacts and sequences, review their activity and add them to a sequence if you turn that action on.

Book a demo See every integration

How does Reply.io connect to Meteor?

With the Reply.io ready connector, your WhatsApp Met queries your Reply account with your API key. It finds a contact by email or LinkedIn profile, pulls their activity with your sequences, lists sequences and their metrics, and checks the inbox and your tasks. Every action that writes arrives turned off because Reply marks it as destructive: if the admin turns them on, the Met creates the contact, adds it to a sequence, creates a task or replies to a thread. It is the official Reply.io server: usage runs on your Reply plan and its call limits.

What it automates

What a Meteor Met does with Reply.io

Know whether a prospect is already in your account

When someone writes on WhatsApp with their work email, the Met looks them up in Reply and pulls their activity: which sequences they got, whether they opened or replied and whether there were calls.

Add them to the right sequence

With the write actions on, the Met creates the contact if it does not exist, finds the sequence by name and enrolls them, so your outreach continues from Reply.

Leave the requested call as a task

If the person asks for a call, the Met creates a call task in Reply for the right salesperson, who sees it in their task list.

Answer how a sequence is doing

The owner asks on WhatsApp how this month's campaign is going and the Met replies with the sequence metrics or compares several, up to 25 at a time.

31 tools

Everything your Met can ask Reply.io for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`reply_search_sequences`	Searches sequences by name, status or archive flag, with a summary of each one.
`reply_get_sequence_steps`	Lists a sequence's steps in order, with their type, delay and variant count.
`reply_get_sequence_stats`	Returns the email and LinkedIn metrics of a sequence.
`reply_compare_sequence_performance`	Compares the metrics of up to 25 sequences side by side.
`reply_start_sequence`	Starts or resumes a sequence so it begins sending. Starts turned off.
`reply_pause_sequence`	Pauses a sequence and stops its scheduled steps. Starts turned off.
`reply_add_contact_to_sequence`	Enrolls up to 100 existing contacts into a sequence. Starts turned off.
`reply_change_status_in_sequence`	Changes a contact's status within a sequence. Starts turned off.
`reply_search_contacts`	Looks up contacts by exact email or LinkedIn profile URL.
`reply_filter_contacts`	Lists contacts by list or sequence, or with a free text search.
`reply_create_contact`	Creates a contact with a name and an email or LinkedIn URL. Starts turned off.
`reply_update_contact`	Changes fields on an existing contact. Starts turned off.
`reply_get_contact_activity`	Returns a contact's history, with sends, opens, replies and calls.
`reply_mark_contacts_as_replied`	Marks up to 100 contacts as replied, or clears the flag. Starts turned off.
`reply_change_contact_owner`	Reassigns up to 100 contacts to another user. Starts turned off.
`reply_blacklist_contact`	Blocks a contact's email, or the whole domain, from outreach. Starts turned off.
`reply_get_inbox_emails`	Lists inbox threads, email and LinkedIn, with a short preview.
`reply_send_inbox_reply`	Sends a reply on an existing thread, with the message body only. Starts turned off.
`reply_change_inbox_category`	Assigns or clears the category of an inbox thread. Starts turned off.
`reply_list_pending_approvals`	Lists the drafts from the Reply sales agent waiting for approval.
`reply_approve_message`	Approves a pending draft and sends it immediately. Starts turned off.
`reply_reject_message`	Rejects a draft and removes the contact from the sequence. Starts turned off.
`reply_list_knowledge_bases`	Lists the knowledge bases of the Reply sales agent.
`reply_list_offers`	Lists the offers of the Reply sales agent, with their id and name.
`reply_list_my_tasks`	Lists your tasks, with filters by type, status, due window or contact.
`reply_create_task`	Creates a standalone task, such as a call, a meeting or a to do. Starts turned off.
`reply_complete_task`	Marks a task as completed, with the call outcome when it applies. Starts turned off.
`reply_list_email_accounts`	Lists connected mailboxes, with their status, daily limits and tags.
`reply_list_schedules`	Lists sending schedules, with their time zone and whether they are the default.
`reply_search_lists`	Finds a contact list by name and returns its id.
`reply_search_team_members`	Finds a teammate by name or email and returns their id.

The limits

What the Reply.io integration does NOT do

We would rather say it here than have you find out during rollout.

It writes nothing with the default actions. Reply marks the 39 actions that write as destructive, so they all start turned off until the admin turns them on in Connections.
It does not ask for confirmation in the chat before sending. If the admin turns on starting sequences, replying to threads or approving drafts, sending goes out with the connected Reply account.
It does not enroll more than 100 contacts per call or compare more than 25 sequences at once; lists return up to 100 results per page.
It does not configure the Reply sales agent from this page: its knowledge bases, playbooks and offers are edited in Reply.
It respects the Reply usage limit: 120 calls per minute, 3,000 per hour and 150,000 per week for your API key.

Before you start

What you need to connect Reply.io

1

The API key of your Reply.io account

In Reply.io, open Settings → API Key and copy your key. Met stores it encrypted and uses it on every call to the Reply server.
2

Connect it in Met

In Met, open Connections → Reply.io → Connect and paste the API key. Then you choose which actions to turn on: every action that writes arrives turned off.

Frequently asked questions

Questions about Reply.io and Meteor

Because the Reply server itself marks them as destructive, and Met keeps every action with that mark turned off. The admin turns on only the ones it needs.

Only if the admin turns on actions such as starting a sequence, replying to a thread or approving a draft. Emails go out from the mailboxes connected in your Reply account.

The exact lookup is by email or LinkedIn profile. For a name, the Met uses the free text search over your lists and sequences.

You do, with your Reply.io plan. Meteor does not resell Reply: the connector uses your API key and follows the limits Reply sets for it.

Step by step