Reply.io is an AI-powered sales engagement platform that automates and optimizes sales outreach across multiple channels, integrating with various business tools to enhance lead conversion rates and overall sales productivity.
Reply.io is an AI-powered sales engagement platform that automates and optimizes sales outreach across multiple channels, integrating with various business tools to enhance lead conversion rates and overall sales productivity. On Nagent, Reply.io is exposed as a fully-configurable marketing automation integration that any agent can call — 33 actions, and API key authentication. No code is required to wire Reply.io into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Reply.io to automate the kinds of tasks marketing automation teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Reply.io into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Reply.io, with input parameters and output schema. Drop these into any step of an agent built in Helix.
REPLY_IO_ADD_CONTACT_TO_SEQUENCETool to add an existing or new contact to a sequence. Use when you need to enroll contacts in email sequences. Provide either contactId for existing contacts or contact details to create and add a new contact.
Input parameters
Contact details for creating a new contact.
Existing contact ID to add to the sequence
Move contact from current sequence if already in another sequence
Sequence ID to add the contact to
Sequence step ID to start from
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_ARCHIVE_SEQUENCETool to archive a sequence. Use when you need to archive an existing sequence without permanently deleting it.
Input parameters
Sequence ID to archive; must be an integer ≥ 1
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_CLEAR_CONTACT_STATUSTool to clear statuses from contacts. Use when you need to remove specific or all clearable statuses from contacts.
Input parameters
Specific statuses to clear. Allowed values: OptedOut, Called, ToCall, MeetingBooked, Bounced, Replied, or Finished. If omitted, clears all clearable statuses (OptedOut, Called, ToCall, MeetingBooked).
Array of contact IDs to clear statuses from
Optional sequence ID for sequence-specific status clearing
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_CONNECT_EXCHANGE_ACCOUNTTool to initiate OAuth connection for an Exchange email account. Use when you need to connect an Exchange account to Reply.io via OAuth flow. Returns the Microsoft OAuth consent page URL where the user should be redirected.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_CONNECT_GMAIL_ACCOUNTTool to initiate Gmail account connection via OAuth. Returns the OAuth authorization URL where the user should be redirected to grant permissions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_CREATE_CONTACTTool to create a new contact in Reply.io. Use when adding contacts to your outreach database.
Input parameters
City
Email address of the contact
Additional notes about the contact
Phone number of the contact
State or province
Job title
Company name
Country
Industry sector
Last name of the contact
Timezone identifier
First name of the contact (required)
Company size range
List of custom fields with key-value pairs
LinkedIn profile URL
LinkedIn Recruiter URL
LinkedIn Sales Navigator URL
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_CREATE_SEQUENCE_STEPTool to add a new step to an existing sequence. Use when you need to build or modify sequence workflows with Email, Call, Task, SMS, WhatsApp, LinkedIn, Condition, or Zapier steps.
Input parameters
Required for Zapier steps. Name of the Zapier action.
Type of sequence step to create
Required for Zapier steps. Zapier action identifier.
Optional for Call steps (notes/script). Required for SMS and WhatsApp steps.
Required for Email steps. Array of email templates with subject and body.
Required for Task steps (ToDo/Meeting) and LinkedIn steps (determines variant).
Required for Condition steps. Array of condition rules to evaluate.
Message body for LinkedIn InMail steps.
Required for Task steps. Task instructions or description.
Sequence ID to add the step to; must be an integer ≥ 1
Execution mode for automated steps.
Subject line for LinkedIn InMail steps.
Required for Condition steps. How long to wait for condition to be met.
Connection note for LinkedIn Connect steps.
Delay in minutes before executing this step after the previous step
Message content for LinkedIn Message steps.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_DELETE_CONTACTTool to delete a contact. Use after confirming the contact exists to remove it permanently.
Input parameters
Contact ID to delete; must be a positive integer
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_DELETE_EMAIL_ACCOUNTTool to delete a specific email account. Use when you need to remove an existing email account identified by its ID.
Input parameters
The unique identifier of the email account to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_DELETE_SCHEDULETool to delete a schedule. Use after confirming the schedule exists to remove it permanently.
Input parameters
Schedule ID to delete; the unique identifier for the schedule
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_DELETE_SEQUENCETool to delete a sequence. Use after confirming the sequence exists to remove it permanently.
Input parameters
Sequence ID to delete; must be an integer ≥ 1
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_DELETE_USERTool to delete a user. Use after confirming the user exists to remove them permanently.
Input parameters
User ID to delete; string identifier to maximize compatibility
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GENERATE_ULIDGenerate ULID
Input parameters
Optional seed to influence randomness
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GET_CONTACT_BY_IDTool to retrieve a contact by ID. Use when you have a contact ID and need detailed contact information.
Input parameters
Unique contact ID to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GET_CONTACT_STATUSTool to get contact status. Use when you need to retrieve all current statuses for a contact.
Input parameters
Contact ID
Optional sequence ID to filter statuses to a specific sequence
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GET_CURRENT_USERTool to get the current authenticated user's ID. Use when you need to verify API key validity or identify the current user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GET_DISCONNECTED_EMAIL_ACCOUNTSTool to list email accounts that are currently disconnected due to authentication or connection errors. Use when you need to identify and troubleshoot problematic email accounts.
Input parameters
Maximum number of items to return (default 25, max 1000)
Number of items to skip for pagination
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GET_SEQUENCE_BY_IDTool to retrieve detailed information about a sequence by its ID. Use when you need to get comprehensive sequence details including settings, email accounts, and workflow steps.
Input parameters
Sequence ID to retrieve; must be an integer ≥ 1
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GET_SEQUENCE_CONTACTS_EXTENDEDTool to retrieve all contacts enrolled in a sequence with additional details. Use when you need to see contact engagement status, current step, or completion timestamps within a sequence.
Input parameters
Sequence ID to retrieve contacts from
Maximum number of items to return (max 100)
Number of items to skip for pagination
Comma-separated list of additional columns to include. Valid values: CurrentStep, LastStepCompletedAt, Status
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_GET_SEQUENCE_STEP_BY_IDTool to retrieve details of a specific sequence step. Use when you need to inspect step configuration including type, delays, execution mode, and type-specific settings.
Input parameters
Sequence ID; must be an integer ≥ 1
Step ID; must be an integer ≥ 1
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_LIST_CONTACTS_BASICTool to list contacts. Use when verifying API access and gathering contact IDs.
Input parameters
Page number to retrieve (1-based indexing)
Number of items per page (max 100)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_LIST_EMAIL_ACCOUNTSTool to list all email accounts. Use when you need to retrieve email accounts page by page.
Input parameters
Page number to retrieve (1-based indexing)
Number of items per page (max 100)
Filter by account status (active/inactive)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_LIST_LISTSTool to list all contact lists. Use when you need to retrieve all available lists in your Reply.io account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_LIST_SEQUENCESTool to retrieve a paginated list of sequences. Use when you need to browse sequences with optional filtering by name.
Input parameters
Filter sequences by name
Page number, starting at 1
Number of items per page, between 1 and 100
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_LIST_SEQUENCE_STEPSTool to retrieve all steps in a sequence. Use when you need to get the complete list of steps configured for a specific sequence.
Input parameters
Sequence ID to retrieve steps for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_PAUSE_SEQUENCETool to pause a running sequence. Use when you need to temporarily stop a sequence from sending emails or executing steps.
Input parameters
Sequence ID to pause; must be a positive integer
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_REMOVE_CONTACT_FROM_SEQUENCETool to remove a contact from a sequence. Use when you need to stop a contact from receiving further steps in a specific sequence.
Input parameters
Sequence ID; string identifier to maximize compatibility
Contact ID to remove from the sequence; must be a positive integer
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_REMOVE_CONTACTS_FROM_SEQUENCETool to bulk remove multiple contacts from a sequence at once. Use when you need to remove several contacts from a sequence efficiently in a single operation.
Input parameters
Sequence ID from which contacts will be removed; must be an integer ≥ 1
Array of contact IDs to remove from the sequence; each must be an integer ≥ 1
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_SEARCH_CONTACTSTool to search contacts by email. Use when you need to find existing contact IDs for update tests.
Input parameters
Email address to search for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_SET_CONTACT_STATUSTool to set the status of one or more contacts. Use when you need to update contact statuses in bulk.
Input parameters
Target status to set for the contacts. Note: Active, Paused, OutOfOffice, Finished, Replied, and Bounced require a sequenceId parameter.
Array of contact IDs to update
Sequence ID required for sequence-specific statuses (Active, Paused, OutOfOffice, Finished, Replied, Bounced). Optional for other statuses (OptedOut, Called, ToCall, MeetingBooked).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_START_SEQUENCETool to start a sequence. Use when you need to activate a sequence that is in New or Paused status.
Input parameters
Sequence ID to start; must be an integer ≥ 1
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_UPDATE_CONTACTTool to update an existing contact's information. Use when you need to modify contact details.
Input parameters
Contact ID to update, must be a positive integer
City location
Primary email address
Additional information about the contact
Phone number
State or province
Job title
Organization name
Country name
Business sector
Last name of the contact
Timezone identifier
First name of the contact
Organization employee count range
Phone validation status
List of user-defined custom fields with key-value pairs
LinkedIn profile URL
LinkedIn Recruiter URL
LinkedIn Sales Navigator URL
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
REPLY_IO_UPDATE_EMAIL_ACCOUNTTool to update an existing email account with custom SMTP/IMAP settings. Use when you need to modify email account configuration such as sender name, signature, server settings, or daily limits.
Input parameters
Email address in valid format
Organization folder name for grouping email accounts
Enable SSL/TLS encryption for IMAP connection (default: true)
Enable SSL/TLS encryption for SMTP connection (default: true)
IMAP server hostname/IP
IMAP port number 1-65535 (typically 993 for SSL/TLS or 143 for STARTTLS)
SMTP server hostname/IP
SMTP port number 1-65535 (typically 465 for SSL/TLS or 587 for STARTTLS)
Target number of emails to send daily during warmup phase
Email signature text
Maximum number of emails that can be sent per day (minimum 1)
Display name shown to email recipients
IMAP authentication password
SMTP authentication password
Daily volume increase during warmup phase
Maximum randomized email volume per day
Minimum randomized email volume per day
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 95 agents privately built on Nagent that already use Reply.io.
Build on Nagent
Connect Reply.io to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Reply.io, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Reply.io is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Reply.io is connected, you configure its 33 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Reply.io steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Reply.io event fires, the agent kicks off automatically.
Every Reply.io action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Reply.io ships with 33 pre-built marketing automation actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Reply.io together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Reply.io-based workflows tailored to your business.