Home Integrations Reply.io Integration Guide

Reply.io Integration Guide

Last updated on Apr 06, 2026

Reply.io Integration Guide

This guide covers all Reply.io actions available in TexAu. Use these actions to manage contacts and campaigns in Reply.io.

All Reply.io actions in TexAu cost 0 credits. You only pay for the credits on your Reply.io side.

Before you begin

  • A Reply.io account is required. Sign up at reply.io.
  • Your Reply.io API key is at Settings > API inside Reply.io.
  • In TexAu, go to Settings > Integrations, find Reply.io, enter your API key, and click Save.

Contact actions

Create Contact (Reply.io)

Creates a new contact in Reply.io.

Input:

  • Email (required)
  • First Name (optional)
  • Last Name (optional)
  • Company (optional)
  • Job Title (optional)
  • Phone (optional)
  • Custom fields (optional)

Output:

  • Contact ID
  • Creation status

Typical use case: After enriching a prospect list in TexAu, push contacts directly to Reply.io.

Create Contact and Push to Campaign (Reply.io)

Creates a new contact in Reply.io and immediately enrolls them in a campaign.

Input:

  • Email (required)
  • First Name (optional)
  • Last Name (optional)
  • Campaign ID (required)
  • Other contact properties (optional)

Output:

  • Contact ID
  • Enrollment status

Typical use case: Skip the two-step create-then-enroll process when you already know which campaign the contact should enter.

Get All Contacts

Returns a list of contacts from your Reply.io account.

Input:

  • Limit (optional)
  • Page (optional, for pagination)

Output:

  • Array of contacts with ID, email, name, and campaign enrollment status

Get Contact by ID

Returns details for a single contact.

Input:

  • Contact ID (required)

Output:

  • All contact fields

Get Contact by Email

Returns details for a contact matched by email address.

Input:

  • Email (required)

Output:

  • Contact ID
  • All contact fields

Update Contact

Updates fields on an existing Reply.io contact.

Input:

  • Contact ID (required)
  • Fields to update

Output:

  • Update status

Delete Contact by Email

Deletes a contact from Reply.io identified by email address.

Input:

  • Email (required)

Output:

  • Deletion status

Delete Contact By ID

Deletes a contact from Reply.io by Contact ID.

Input:

  • Contact ID (required)

Output:

  • Deletion status

Push Existing Contact to Campaign

Enrolls an existing Reply.io contact into a campaign.

Input:

  • Contact ID or Email (required)
  • Campaign ID (required)

Output:

  • Enrollment status

Get Contacts by List Name

Returns contacts that belong to a specific Reply.io list.

Input:

  • List Name (required)

Output:

  • Array of contacts in the list

Campaign actions

Get All Campaigns

Returns a list of all campaigns in your Reply.io account.

Input: None

Output:

  • Array of campaigns with ID, name, and status

Get Campaign Details

Returns full details for a specific campaign.

Input:

  • Campaign ID (required)

Output:

  • Campaign name
  • Status
  • Step count
  • Contact count
  • Metrics (sent, opened, replied, bounced)

Common workflow patterns

Enrich then push to Reply.io

  1. Start with a list of LinkedIn URLs in a TexAu table.
  2. Add an Action Column for Find Work Email by LinkedIn URL (BetterEnrich).
  3. Add a second Action Column for Find Mobile Number by LinkedIn URL (BetterEnrich).
  4. Add a third Action Column for Create Contact and Push to Campaign (Reply.io).
  5. Map First Name, Last Name, Email, and Campaign ID.
  6. Run enrichment.

Contacts with verified emails get created in Reply.io and enrolled immediately.

Check for existing contacts before creating

  1. Add an Action Column for Get Contact by Email (Reply.io) using the email output from BetterEnrich.
  2. Add a Formula Column: IF({{Contact ID}} != "", "exists", "new")
  3. Use this status in a conditional column to decide whether to create or update.

Troubleshooting

Create Contact fails with "contact already exists". Reply.io uses email as the unique key. Use Get Contact by Email first to check. If the contact already exists, use Update Contact instead.

Push to Campaign returns "campaign not found". Use Get All Campaigns to find the correct Campaign ID. Campaign IDs are numeric, not the campaign name.

Contacts are created but do not appear in campaigns. Check that the campaign is active and accepting new contacts. Paused campaigns do not enroll new contacts even if the API call succeeds.

The API key saves but actions return 401 errors. Your Reply.io API key may be tied to a specific workspace. Verify the key is for the Reply.io account and workspace where your campaigns are active.