Reply action

Get Contact by Email (Reply.io)

Retrieve details for a specific contact using their email address.

Reply logoReply
reply-get-contact-by-email
crmReturns in secondsLight tier
Input

What it needs.

Map each field to a column in your table. Optional fields can stay empty.

FieldType
  • email
    The email address of the contact to retrieve.
    dynamic_select

When to use this.

The "Get Contact by Email" action in Reply.io allows users to efficiently retrieve detailed information about a specific contact using their email address. By providing the email as a dynamic input parameter, users can access a wealth of data, including the contact's ID, first and last names, company affiliation, job title, phone number, and geographical location (city, state, country). The output also includes LinkedIn profile links, time zone information, and additional details such as company size and industry. This action is particularly useful for CRM applications, enabling sales and marketing teams to quickly gather essential contact information for lead generation, customer relationship management, and targeted outreach campaigns. With its focus on semantic types like email, name, and company data, this action enhances user efficiency in managing and leveraging contact information.

Output

What it returns.

Every field this action writes back to the row. Click a line to expand nested objects.

FieldType
  • id
    Id
    number
  • email
    Email
    string
  • first_name
    First Name
    string
  • last_name
    Last Name
    string
  • company
    Company
    string
  • title
    Title
    string
  • mobile_number
    Mobile Number
    string
  • mobile_number_status
    Mobile Number Status
    nullablestring
  • city
    City
    nullablestring
  • state
    State
    nullablestring
  • country
    Country
    nullablestring
  • time_zone_id
    Time Zone Id
    nullablestring
  • linkedin_url
    Linkedin Url
    string
  • adding_date
    Adding Date
    nullablestring
  • company_size
    Company Size
    nullablestring
  • industry
    Industry
    nullablestring
  • sales_navigator_url
    Sales Navigator Url
    nullablestring
  • linkedin_recruiter_url
    Linkedin Recruiter Url
    nullablestring
  • account_id
    Account Id
    nullablenumber
Workflow

How this fits a workflow.

Trigger → Get Contact by Email (Reply.io) → enrich → push to your CRM. You set it up once; after that it runs without you.

  1. Step 1TriggerNew row, form submit, or schedule.
  2. Step 2Get Contact by Email (Reply.io)The Reply action runs.
  3. Step 3EnrichWaterfall fills missing fields.
  4. Step 4Push to CRMHubSpot / Pipedrive / Zoho CRM / GoHighLevel.

Two actions you can chain after this one:

Get Contact by Email (Reply.io)Delete Contact By ID (Reply.io)Delete Contact by Email (Reply.io)
Reliability

Throughput & reliability.

How fast it drains a table, and what happens when the upstream provider has a bad day.

  • Per-minute limitNo public cap
  • Per-day limitPlan-defined
  • RetriesAutomatic w/ backoff
  • Failed lookupsZero credits

Who runs this

GTM EngineerRevOpsAgency

Light tier. See pricing; per-action credit cost is private.

FAQ.

Mostly. Fast actions fill the cell in a few seconds. Long-running ones run in the background and write back to the row when they finish, so you can close the tab.

No. A failed lookup costs zero credits. When a provider misses or times out, the waterfall moves to the next one and you only pay for the match you actually got.

No. Run it on one cell, on a selection, on the whole table, or on a schedule. Same action either way.

HubSpot, Pipedrive, Zoho, and GoHighLevel are bidirectional, with Salesforce coming soon. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Get Contact by Email (Reply.io) in 60 seconds.

Connect the account, drop the action on a column, run it on your rows.