# Reply.io

> Run sales outreach in Reply.io: create and update contacts, add them to sequences and finish or pause them there, mark replies, manage tasks, templates, contact lists and do-not-contact rules, and read sequence results.

App · 32 actions. Web page: https://docs.lodol.com/docs/integrations/reply-io

## Actions

### Add contacts to list

Put contacts on a contact list.

**Inputs**

- Contact list (`list_id`, text, required): The contact list. Pick one, or give its id from an earlier step.
- Contact IDs (`contact_ids`, text, required): One contact id, several separated by commas, or a list from an earlier step. Up to 100.

**Outputs**: The add contacts to list result

- `added` (list): Ids of the contacts added
- `added_count` (number): How many were added
- `list_id` (number): The list they were added to
- `not_processed` (list): Contacts Reply.io did not add, with why
- `not_processed_count` (number): How many were not added

**Example output**

```json
{
  "added": [
    4821
  ],
  "added_count": 1,
  "list_id": 12,
  "not_processed": [],
  "not_processed_count": 0
}
```

### Add contacts to sequence

Enrol contacts in a sequence, now or from a time you choose. Contacts already in it, opted out or blocked are reported, not added.

**Inputs**

- Sequence (`sequence_id`, text, required): The sequence. Pick one, or give its id from an earlier step.
- Contact IDs (`contact_ids`, text, required): One contact id, several separated by commas, or a list from an earlier step. Up to 100.
- Start at (`start_at`, date and time): When to begin contacting them. Leave empty to start straight away.
- Skip the first step's delay (`skip_first_delay`, true/false): On sends the first step without waiting for its delay. Default: `false`.
- Move from their other sequences (`remove_from_other_sequences`, true/false): On takes the contacts out of any sequence they are in first. Default: `false`.

**Outputs**: The add contacts to sequence result

- `added` (list): Ids of the contacts added
- `added_count` (number): How many were added
- `not_processed` (list): Contacts Reply.io did not add, with why
- `not_processed_count` (number): How many were not added

**Example output**

```json
{
  "added": [
    4821
  ],
  "added_count": 1,
  "not_processed": [
    {
      "details": "Already in it",
      "error": "alreadyInSequence",
      "id": 4822
    }
  ],
  "not_processed_count": 1
}
```

### Add do-not-contact rule

Stop Reply.io contacting an email address or a whole domain, or add an exception that is always allowed.

**Inputs**

- Rule type (`rule_type`, text, required): Which do-not-contact list: email addresses, domains or exceptions. One of: `email` (Email address), `domain`, `exception` (Email exception (always allowed)).
- Address or domain (`pattern`, text, required): The email address or domain, such as competitor.example.

**Outputs**: The add do-not-contact rule result

- `rule` (object): The new rule

**Example output**

```json
{
  "rule": {
    "id": 63,
    "isGlobal": false,
    "pattern": "competitor.example"
  }
}
```

### Add note to contact

Add a note to a contact's timeline so your team sees the context.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's id, from 'Find contacts' or the step that created it.
- Note (`note`, text, required): The note to add.

**Outputs**: The add note to contact result

- `added` (true/false): Always true once added
- `contact_id` (number): The contact noted
- `note` (text): The note added

**Example output**

```json
{
  "added": true,
  "contact_id": 4821,
  "note": "Asked for a demo."
}
```

### Complete task

Mark a task done. It can also finish the contact in the task's sequence.

**Inputs**

- Task ID (`task_id`, text, required): The task's id, from 'List tasks' or the step that created it.
- Also finish the contact in the sequence (`finish_in_sequence`, true/false): On takes the contact out of the sequence the task came from. Default: `false`.

**Outputs**: The complete task result

- `task` (object): The completed task

**Example output**

```json
{
  "task": {
    "assignedUserId": 1234,
    "contactId": 4821,
    "createdAt": "2026-10-15T09:00:00Z",
    "creationSource": "user",
    "dueTo": "2026-10-17T09:00:00Z",
    "finishedAt": "2026-10-17T10:00:00Z",
    "id": 777,
    "isScheduled": true,
    "linkedInTaskType": "message",
    "sequenceId": 200,
    "startAt": "2026-10-16T09:00:00Z",
    "status": "new",
    "taskType": "toDo",
    "template": {
      "body": "Call about pricing",
      "subject": "Pricing"
    }
  }
}
```

### Create contact

Add a contact to Reply.io. It needs an email address or a LinkedIn address.

**Inputs**

- Email (`email`, text): The contact's email address. Give this or a LinkedIn address.
- First name (`first_name`, text): First name.
- Last name (`last_name`, text): Last name.
- Phone (`phone`, text): Phone number with the country code.
- Job title (`title`, text): Job title.
- Company (`company`, text): Company name.
- Company size (`company_size`, text): Number of employees. One of: `Self-Employed`, `2-10` (2 to 10), `11-50` (11 to 50), `51-200` (51 to 200), `201-500` (201 to 500), `501-1000` (501 to 1,000), `1001-5000` (1,001 to 5,000), `5001-10000` (5,001 to 10,000), `10001+` (More than 10,000).
- Industry (`industry`, text): The company's industry.
- City (`city`, text): City.
- State (`state`, text): State or province.
- Country (`country`, text): Country.
- LinkedIn address (`linkedin_url`, text): The contact's LinkedIn profile address. Give this or an email address.
- Notes (`notes`, text): Free-text notes on the contact.
- Custom fields (`custom_fields`, object): Your own contact fields, each with its name and value, for example {"Lead source": "Webinar"}.

**Outputs**: The create contact result

- `contact` (object): The new contact

**Example output**

```json
{
  "contact": {
    "accountId": 55,
    "addingDate": "2026-10-15T09:00:00Z",
    "city": "Austin",
    "company": "Acme",
    "companySize": "51-200",
    "country": "United States",
    "createdAt": "2026-10-15T09:00:00Z",
    "customFields": [
      {
        "enrichmentStatus": "none",
        "key": "Lead source",
        "value": "Webinar"
      }
    ],
    "domain": "example.com",
    "email": "jo@example.com",
    "firstName": "Jo",
    "id": 4821,
    "industry": "Software",
    "isOptedOut": false,
    "lastModifiedAt": "2026-10-15T09:00:00Z",
    "lastName": "Bloggs",
    "linkedInUrl": "https://www.linkedin.com/in/jo-bloggs",
    "notes": "Met at a conference.",
    "ownerUserId": 1234,
    "phone": "+15555550100",
    "stage": "New",
    "state": "Texas",
    "timeZoneId": "America/Chicago",
    "title": "Head of Sales"
  }
}
```

### Create contact list

Create an empty contact list.

**Inputs**

- Name (`name`, text, required): The list's name.
- Share with my team (`shared`, true/false): On lets your team see and use the list. Default: `false`.

**Outputs**: The create contact list result

- `list` (object): The new list

**Example output**

```json
{
  "list": {
    "id": 12,
    "isShared": false,
    "name": "Webinar attendees"
  }
}
```

### Create email template

Save an email template you can use in sequences.

**Inputs**

- Name (`name`, text, required): The template's name.
- Subject (`subject`, text): The email subject.
- Body (`body`, text, required): The email body. Variables like {{FirstName}} work.
- Who can use it (`visible_to`, text): Keep it to yourself or share it with your team. One of: `personal` (Only me (default)), `team` (My whole team). Default: `personal`.

**Outputs**: The create email template result

- `template` (object): The new template

**Example output**

```json
{
  "template": {
    "body": "Hi {{FirstName}}",
    "createdAt": "2026-10-01T09:00:00Z",
    "folderId": 3,
    "folderType": "personal",
    "id": 88,
    "name": "Intro",
    "subject": "Quick question",
    "updatedAt": "2026-10-02T09:00:00Z"
  }
}
```

### Create sequence

Create a sequence with one email step. It is not started, so nothing is sent until you start it in Reply.io.

**Inputs**

- Name (`name`, text, required): The sequence's name.
- Subject (`subject`, text, required): The first email's subject. Variables like {{FirstName}} work.
- Message (`message`, text, required): The first email's body. Variables like {{FirstName}} work.
- How the email goes out (`send_mode`, text): Send it automatically, or make a task to send it by hand. One of: `automatic` (Send automatically (default)), `manual` (Make a task to send it by hand). Default: `automatic`.
- Sending mailboxes (`email_account_ids`, list): The mailboxes the sequence sends from. Leave empty to choose in Reply.io.

**Outputs**: The create sequence result

- `sequence` (object): The new sequence

**Example output**

```json
{
  "sequence": {
    "created": "2026-10-01T09:00:00Z",
    "emailAccounts": [
      {
        "email": "jo@acme.example",
        "id": 31
      }
    ],
    "health": "healthy",
    "id": 200,
    "isArchived": false,
    "name": "Q4 outbound",
    "ownerUserId": 1234,
    "scheduleId": 7,
    "settings": {
      "emailsCountPerDay": 100
    },
    "status": "active",
    "steps": [
      {
        "delayInMinutes": 0,
        "executionMode": "automatic",
        "id": 9001,
        "type": "email",
        "variants": [
          {
            "id": 5001,
            "message": "Hi {{FirstName}}",
            "subject": "Quick question"
          }
        ]
      }
    ]
  }
}
```

### Create task

Create a task for yourself, such as a call or a to-do, linked to a contact. It starts now and is due in a day unless you set times.

**Inputs**

- Type (`task_type`, text, required): What kind of task it is. One of: `toDo` (To do), `call`, `meeting`, `linkedIn`, `manualEmail` (Email to send by hand), `sms` (Text message), `whatsApp` (WhatsApp message).
- Details (`body`, text, required): What the task is. For an email task, the message.
- Subject (`subject`, text): A subject, for email and LinkedIn tasks.
- Contact ID (`contact_id`, text): The contact the task is about. Needed to fill in {{variables}}.
- Starts (`start_at`, date and time): When the task becomes due to start. Defaults to now.
- Due (`due_at`, date and time): When it is due, after the start. Defaults to a day later.
- LinkedIn action (`linkedin_task_type`, text): Which LinkedIn action the task is. Only when Type is LinkedIn. One of: `message`, `connect` (Connection request), `inMail`, `viewProfile` (View profile).

**Outputs**: The create task result

- `task` (object): The new task

**Example output**

```json
{
  "task": {
    "assignedUserId": 1234,
    "contactId": 4821,
    "createdAt": "2026-10-15T09:00:00Z",
    "creationSource": "user",
    "dueTo": "2026-10-17T09:00:00Z",
    "finishedAt": "2026-10-17T10:00:00Z",
    "id": 777,
    "isScheduled": true,
    "linkedInTaskType": "message",
    "sequenceId": 200,
    "startAt": "2026-10-16T09:00:00Z",
    "status": "new",
    "taskType": "toDo",
    "template": {
      "body": "Call about pricing",
      "subject": "Pricing"
    }
  }
}
```

### Delete contact

Delete a contact from Reply.io for good. They leave every sequence and list they were in.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's id, from 'Find contacts' or the step that created it.

**Outputs**: The delete contact result

- `contact_id` (number): The contact deleted
- `deleted` (true/false): Always true once deleted

**Example output**

```json
{
  "contact_id": 4821,
  "deleted": true
}
```

### Delete contact list

Delete a contact list. The contacts on it are kept.

**Inputs**

- Contact list (`list_id`, text, required): The contact list. Pick one, or give its id from an earlier step.

**Outputs**: The delete contact list result

- `deleted` (true/false): Always true once deleted
- `list_id` (number): The list deleted

**Example output**

```json
{
  "deleted": true,
  "list_id": 12
}
```

### Delete do-not-contact rule

Remove a rule so those contacts can be emailed again.

**Inputs**

- Rule type (`rule_type`, text, required): Which do-not-contact list: email addresses, domains or exceptions. One of: `email` (Email address), `domain`, `exception` (Email exception (always allowed)).
- Rule ID (`rule_id`, text, required): The rule's id, from 'List do-not-contact rules' or the step that added it.

**Outputs**: The delete do-not-contact rule result

- `deleted` (true/false): Always true once deleted
- `rule_id` (number): The rule deleted

**Example output**

```json
{
  "deleted": true,
  "rule_id": 63
}
```

### Delete email template

Delete an email template. Sequences already using its text keep it.

**Inputs**

- Email template (`template_id`, text, required): The template. Pick one, or give its id from an earlier step.

**Outputs**: The delete email template result

- `deleted` (true/false): Always true once deleted
- `template_id` (number): The template deleted

**Example output**

```json
{
  "deleted": true,
  "template_id": 88
}
```

### Delete sequence

Delete a sequence and take everyone out of it. The contacts stay in Reply.io.

**Inputs**

- Sequence (`sequence_id`, text, required): The sequence. Pick one, or give its id from an earlier step.

**Outputs**: The delete sequence result

- `deleted` (true/false): Always true once deleted
- `sequence_id` (number): The sequence deleted

**Example output**

```json
{
  "deleted": true,
  "sequence_id": 200
}
```

### Delete task

Delete a task.

**Inputs**

- Task ID (`task_id`, text, required): The task's id, from 'List tasks' or the step that created it.

**Outputs**: The delete task result

- `deleted` (true/false): Always true once deleted
- `task_id` (number): The task deleted

**Example output**

```json
{
  "deleted": true,
  "task_id": 777
}
```

### Find contacts

List contacts a page at a time, or look one up by exact email address or LinkedIn address.

**Inputs**

- Email (`email`, text): Only the contact with this exact email address.
- LinkedIn address (`linkedin_url`, text): Only the contact with this exact LinkedIn profile address.
- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The find contacts result

- `contacts` (list): The contacts
- `count` (number): How many came back on this page
- `has_more` (true/false): Whether another page follows
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last

**Example output**

```json
{
  "contacts": [
    {
      "accountId": 55,
      "addingDate": "2026-10-15T09:00:00Z",
      "city": "Austin",
      "company": "Acme",
      "companySize": "51-200",
      "country": "United States",
      "createdAt": "2026-10-15T09:00:00Z",
      "customFields": [
        {
          "enrichmentStatus": "none",
          "key": "Lead source",
          "value": "Webinar"
        }
      ],
      "domain": "example.com",
      "email": "jo@example.com",
      "firstName": "Jo",
      "id": 4821,
      "industry": "Software",
      "isOptedOut": false,
      "lastModifiedAt": "2026-10-15T09:00:00Z",
      "lastName": "Bloggs",
      "linkedInUrl": "https://www.linkedin.com/in/jo-bloggs",
      "notes": "Met at a conference.",
      "ownerUserId": 1234,
      "phone": "+15555550100",
      "stage": "New",
      "state": "Texas",
      "timeZoneId": "America/Chicago",
      "title": "Head of Sales"
    }
  ],
  "count": 1,
  "has_more": false,
  "next_skip": 0
}
```

### Find sequences

List sequences a page at a time, by status or part of the name.

**Inputs**

- Status (`status`, text): Only sequences in this state. One of: `active`, `paused`, `new` (Not started yet).
- Name contains (`name`, text): Only sequences whose name contains this text.
- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The find sequences result

- `count` (number): How many came back on this page
- `has_more` (true/false): Whether another page follows
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last
- `sequences` (list): The sequences

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_skip": 0,
  "sequences": [
    {
      "created": "2026-10-01T09:00:00Z",
      "health": "healthy",
      "id": 200,
      "isArchived": false,
      "name": "Q4 outbound",
      "ownerUserId": 1234,
      "status": "active"
    }
  ]
}
```

### Get contact

Get one contact with their profile, owner, opt-out state and custom fields.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's id, from 'Find contacts' or the step that created it.

**Outputs**: The get contact result

- `contact` (object): The contact

**Example output**

```json
{
  "contact": {
    "accountId": 55,
    "addingDate": "2026-10-15T09:00:00Z",
    "city": "Austin",
    "company": "Acme",
    "companySize": "51-200",
    "country": "United States",
    "createdAt": "2026-10-15T09:00:00Z",
    "customFields": [
      {
        "enrichmentStatus": "none",
        "key": "Lead source",
        "value": "Webinar"
      }
    ],
    "domain": "example.com",
    "email": "jo@example.com",
    "firstName": "Jo",
    "id": 4821,
    "industry": "Software",
    "isOptedOut": false,
    "lastModifiedAt": "2026-10-15T09:00:00Z",
    "lastName": "Bloggs",
    "linkedInUrl": "https://www.linkedin.com/in/jo-bloggs",
    "notes": "Met at a conference.",
    "ownerUserId": 1234,
    "phone": "+15555550100",
    "stage": "New",
    "state": "Texas",
    "timeZoneId": "America/Chicago",
    "title": "Head of Sales"
  }
}
```

### Get current user

Get the Reply.io user the API key acts as: their id, username and team id. A quick way to check the connection.

**Inputs**: None.

**Outputs**: The get current user result

- `team_id` (number): The user's team id
- `user_id` (number): The user's id
- `username` (text): The user's username

**Example output**

```json
{
  "team_id": 100,
  "user_id": 1234,
  "username": "jo@acme.example"
}
```

### Get sequence

Get a sequence with its steps, settings and connected mailboxes.

**Inputs**

- Sequence (`sequence_id`, text, required): The sequence. Pick one, or give its id from an earlier step.

**Outputs**: The get sequence result

- `sequence` (object): The sequence

**Example output**

```json
{
  "sequence": {
    "created": "2026-10-01T09:00:00Z",
    "emailAccounts": [
      {
        "email": "jo@acme.example",
        "id": 31
      }
    ],
    "health": "healthy",
    "id": 200,
    "isArchived": false,
    "name": "Q4 outbound",
    "ownerUserId": 1234,
    "scheduleId": 7,
    "settings": {
      "emailsCountPerDay": 100
    },
    "status": "active",
    "steps": [
      {
        "delayInMinutes": 0,
        "executionMode": "automatic",
        "id": 9001,
        "type": "email",
        "variants": [
          {
            "id": 5001,
            "message": "Hi {{FirstName}}",
            "subject": "Quick question"
          }
        ]
      }
    ]
  }
}
```

### Get sequence stats

Get a sequence's email and LinkedIn results (contacted, opened, replied, bounced and more) for a period. Reply.io limits how often this can be asked.

**Inputs**

- Sequence (`sequence_id`, text, required): The sequence. Pick one, or give its id from an earlier step.
- Period (`period`, text): A ready-made period. Last week if you give nothing. One of: `lastWeek` (Last week (default)), `lastMonth` (Last month), `lastYear` (Last year), `allTime` (All time).
- From (`from_date`, date): First day to count. Use instead of a period.
- To (`to_date`, date): Last day to count, included. Use with 'From'.

**Outputs**: The get sequence stats result

- `email` (object): Email results
- `linkedin` (object): LinkedIn results

**Example output**

```json
{
  "email": {
    "bounced": 2,
    "contacted": 120,
    "delivered": 118,
    "opened": 64,
    "replied": 9
  },
  "linkedin": {
    "connectionsAccepted": 12,
    "connectionsSent": 30,
    "messagesSent": 10
  }
}
```

### List contact lists

List contact lists a page at a time, optionally by part of the name.

**Inputs**

- Name contains (`search`, text): Only lists whose name contains this text.
- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The list contact lists result

- `count` (number): How many came back on this page
- `has_more` (true/false): Whether another page follows
- `lists` (list): The contact lists
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "lists": [
    {
      "id": 12,
      "isShared": false,
      "name": "Webinar attendees"
    }
  ],
  "next_skip": 0
}
```

### List contacts in sequence

List the contacts in a sequence with their status, current step and whether they replied or bounced.

**Inputs**

- Sequence (`sequence_id`, text, required): The sequence. Pick one, or give its id from an earlier step.
- Sort by (`sort_by`, text): What to sort by. Newest first unless you say otherwise. One of: `addingDate` (Date added), `email`, `firstName` (First name), `lastName` (Last name), `company`, `statusInSequence` (Status in the sequence).
- Order (`sort_direction`, text): Which end to start from. One of: `desc` (Newest or highest first (default)), `asc` (Oldest or lowest first).
- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The list contacts in sequence result

- `contacts` (list): The contacts in the sequence
- `count` (number): How many came back on this page
- `has_more` (true/false): Whether another page follows
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last

**Example output**

```json
{
  "contacts": [
    {
      "addingDate": "2026-10-15T09:00:00Z",
      "company": "Acme",
      "contactId": 4821,
      "currentStep": {
        "displayName": "Step 1: Email",
        "stepId": 9001
      },
      "email": "jo@example.com",
      "emailAccountId": 31,
      "emailDisposition": {
        "isBounced": false,
        "isReplied": false
      },
      "firstName": "Jo",
      "isOptedOut": false,
      "lastName": "Bloggs",
      "sequenceId": 200,
      "statusInSequence": "active",
      "title": "Head of Sales"
    }
  ],
  "count": 1,
  "has_more": false,
  "next_skip": 0
}
```

### List do-not-contact rules

List the email, domain or exception rules that stop Reply.io contacting people.

**Inputs**

- Rule type (`rule_type`, text, required): Which do-not-contact list: email addresses, domains or exceptions. One of: `email` (Email address), `domain`, `exception` (Email exception (always allowed)).
- Contains (`search`, text): Only rules whose pattern contains this text.
- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The list do-not-contact rules result

- `count` (number): How many came back on this page
- `has_more` (true/false): Whether another page follows
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last
- `rules` (list): The rules

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_skip": 0,
  "rules": [
    {
      "id": 63,
      "isGlobal": false,
      "pattern": "competitor.example"
    }
  ]
}
```

### List email accounts

List the mailboxes connected to Reply.io with their daily limit and whether they are connected.

**Inputs**

- Only my mailboxes (`mine_only`, true/false): On lists only mailboxes you own. Off lists every one you can see. Default: `false`.
- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The list email accounts result

- `count` (number): How many came back on this page
- `email_accounts` (list): The mailboxes
- `has_more` (true/false): Whether another page follows
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last

**Example output**

```json
{
  "count": 1,
  "email_accounts": [
    {
      "connectionStatus": "connected",
      "dailyLimit": 100,
      "email": "jo@acme.example",
      "emailAccountType": "gmail",
      "id": 31,
      "isDefault": true,
      "ownerUserId": 1234,
      "senderName": "Jo Bloggs",
      "tags": [
        "warm"
      ]
    }
  ],
  "has_more": false,
  "next_skip": 0
}
```

### List email templates

List email templates a page at a time, optionally by part of the name.

**Inputs**

- Name contains (`name`, text): Only templates whose name contains this text.
- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The list email templates result

- `count` (number): How many came back on this page
- `has_more` (true/false): Whether another page follows
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last
- `templates` (list): The templates

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_skip": 0,
  "templates": [
    {
      "body": "Hi {{FirstName}}",
      "createdAt": "2026-10-01T09:00:00Z",
      "folderId": 3,
      "folderType": "personal",
      "id": 88,
      "name": "Intro",
      "subject": "Quick question",
      "updatedAt": "2026-10-02T09:00:00Z"
    }
  ]
}
```

### List tasks

List tasks a page at a time, with their type, status, contact and due date.

**Inputs**

- Page size (`limit`, number): How many to return, 1 to 1000. Reply.io's default is 25. From 1 to 1000.
- Skip (`skip`, number): How many to skip, to get a later page. Use 'next_skip' from the last page. At least 0.

**Outputs**: The list tasks result

- `count` (number): How many came back on this page
- `has_more` (true/false): Whether another page follows
- `next_skip` (number): The 'Skip' to use to get the next page, 0 on the last
- `tasks` (list): The tasks

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_skip": 0,
  "tasks": [
    {
      "assignedUserId": 1234,
      "contactId": 4821,
      "createdAt": "2026-10-15T09:00:00Z",
      "creationSource": "user",
      "dueTo": "2026-10-17T09:00:00Z",
      "finishedAt": "2026-10-17T10:00:00Z",
      "id": 777,
      "isScheduled": true,
      "linkedInTaskType": "message",
      "sequenceId": 200,
      "startAt": "2026-10-16T09:00:00Z",
      "status": "new",
      "taskType": "toDo",
      "template": {
        "body": "Call about pricing",
        "subject": "Pricing"
      }
    }
  ]
}
```

### Mark contacts as replied

Record a reply Reply.io did not see (in another inbox or a CRM). It stops further steps for them. Name a sequence to do it for that sequence only, or leave it empty for every sequence they are in.

**Inputs**

- Contact IDs (`contact_ids`, text, required): One contact id, several separated by commas, or a list from an earlier step. Up to 100.
- Only in sequence (`sequence_id`, text): Limit this to one sequence. Leave empty to apply it to every sequence the contacts are in.
- Replied (`replied`, true/false): On marks them as replied. Off clears the replied flag. Default: `true`.

**Outputs**: The mark contacts as replied result

- `not_processed` (list): Contacts Reply.io did not change, with why
- `not_processed_count` (number): How many were not changed
- `replied` (true/false): The state set
- `updated` (list): Ids of the contacts changed
- `updated_count` (number): How many were changed

**Example output**

```json
{
  "not_processed": [],
  "not_processed_count": 0,
  "replied": true,
  "updated": [
    4821
  ],
  "updated_count": 1
}
```

### Remove contact from sequence

Take one contact out of a sequence. They are not deleted.

**Inputs**

- Sequence (`sequence_id`, text, required): The sequence. Pick one, or give its id from an earlier step.
- Contact ID (`contact_id`, text, required): The contact's id, from 'Find contacts' or the step that created it.

**Outputs**: The remove contact from sequence result

- `contact_id` (number): The contact removed
- `removed` (true/false): Always true once removed
- `sequence_id` (number): The sequence they left

**Example output**

```json
{
  "contact_id": 4821,
  "removed": true,
  "sequence_id": 200
}
```

### Set contact status in sequence

Finish, pause or resume contacts in one sequence. Finishing stops all further steps for them.

**Inputs**

- Sequence (`sequence_id`, text, required): The sequence. Pick one, or give its id from an earlier step.
- Contact IDs (`contact_ids`, text, required): One contact id, several separated by commas, or a list from an earlier step. Up to 100.
- Status (`status`, text, required): What to set them to. One of: `finished` (Finished (stop the sequence for them)), `paused`, `active` (Active (resume)), `outOfOffice` (Out of office).

**Outputs**: The set contact status in sequence result

- `not_processed` (list): Contacts Reply.io did not change, with why
- `not_processed_count` (number): How many were not changed
- `status` (text): The status set
- `updated` (list): Ids of the contacts changed
- `updated_count` (number): How many were changed

**Example output**

```json
{
  "not_processed": [],
  "not_processed_count": 0,
  "status": "finished",
  "updated": [
    4821
  ],
  "updated_count": 1
}
```

### Update contact

Change a contact's details. Only the fields you fill in change; the rest stay as they are.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's id, from 'Find contacts' or the step that created it.
- Email (`email`, text): The contact's email address. Leave empty to keep it.
- First name (`first_name`, text): First name. Leave empty to keep it.
- Last name (`last_name`, text): Last name. Leave empty to keep it.
- Phone (`phone`, text): Phone number with the country code. Leave empty to keep it.
- Job title (`title`, text): Job title. Leave empty to keep it.
- Company (`company`, text): Company name. Leave empty to keep it.
- Company size (`company_size`, text): Number of employees. Leave empty to keep it. One of: `Self-Employed`, `2-10` (2 to 10), `11-50` (11 to 50), `51-200` (51 to 200), `201-500` (201 to 500), `501-1000` (501 to 1,000), `1001-5000` (1,001 to 5,000), `5001-10000` (5,001 to 10,000), `10001+` (More than 10,000).
- Industry (`industry`, text): The company's industry. Leave empty to keep it.
- City (`city`, text): City. Leave empty to keep it.
- State (`state`, text): State or province. Leave empty to keep it.
- Country (`country`, text): Country. Leave empty to keep it.
- LinkedIn address (`linkedin_url`, text): The contact's LinkedIn profile address. Leave empty to keep it.
- Notes (`notes`, text): Free-text notes on the contact. Leave empty to keep it.
- Opt-out (`opt_out`, text): Opt the contact out of all emails, or clear their opt-out. Leave empty to leave it as it is. One of: `opt_out` (Opt the contact out of all emails), `clear` (Clear the opt-out).
- Custom fields (`custom_fields`, object): Your own contact fields, each with its name and value, for example {"Lead source": "Webinar"}.

**Outputs**: The update contact result

- `contact` (object): The updated contact

**Example output**

```json
{
  "contact": {
    "accountId": 55,
    "addingDate": "2026-10-15T09:00:00Z",
    "city": "Austin",
    "company": "Acme",
    "companySize": "51-200",
    "country": "United States",
    "createdAt": "2026-10-15T09:00:00Z",
    "customFields": [
      {
        "enrichmentStatus": "none",
        "key": "Lead source",
        "value": "Webinar"
      }
    ],
    "domain": "example.com",
    "email": "jo@example.com",
    "firstName": "Jo",
    "id": 4821,
    "industry": "Software",
    "isOptedOut": false,
    "lastModifiedAt": "2026-10-15T09:00:00Z",
    "lastName": "Bloggs",
    "linkedInUrl": "https://www.linkedin.com/in/jo-bloggs",
    "notes": "Met at a conference.",
    "ownerUserId": 1234,
    "phone": "+15555550100",
    "stage": "New",
    "state": "Texas",
    "timeZoneId": "America/Chicago",
    "title": "Head of Sales"
  }
}
```
