# Adding records to a pipeline and sending them

Source: https://listplus.ai/en/help/pipelines/send-records-to-a-pipeline
Last updated: 2026-10-17

Records get into a pipeline through the **Add** menu, wait under
**Entries**, and go out when you click **Send**. This article covers that
day-to-day flow. Setting up a pipeline is covered in "[Pipelines — send
records on to your CRM, Slack, e-mail or API](https://listplus.ai/en/help/pipelines/pipelines-overview)".

## Add records

1. **From a list:** select the rows, then in the selection bar click
   **Add → Send to pipeline → (pipeline name)**.
2. **From the Watchlist:** select contacts and use **Add → Send to pipeline** the
   same way.
3. **From the contact drawer:** for a contact on the Watchlist, use **Add → Send to
   pipeline** in the drawer.
4. **From the Inbox:** select recognized contacts and use **Add → Send to
   pipeline**; they are put on the Watchlist first, then added.
5. **From an alert, by itself:** a Watchlist contact with alerts
   enters the pipeline chosen under **Send news to** in its alert dialog
   as soon as a job change or new post is found — with the new company and
   title; a change shown as **Held back – not certain enough** goes there
   only after you click **Take it over anyway** (see "[The Watchlist (saved
   contacts)](https://listplus.ai/en/help/inbox-and-saved/saved-contacts)").
6. **Companies from the Watchlist:** in **Watchlist → Companies** tick
   companies and use **Add → Send to pipeline**; they go in as company
   records. A company with an alert enters the pipeline chosen under
   **Send news to** by itself when its alert finds something (see
   "[Companies on the Watchlist and company alerts](https://listplus.ai/en/help/inbox-and-saved/watch-companies)").
7. **From a list trigger, by itself:** a trigger with the action **Hand
   over to pipeline** adds every record that meets its conditions (see
   "[Triggers — hand records on automatically](https://listplus.ai/en/help/working-in-a-list/list-triggers)").

A confirmation shows how many contacts were added, how many were already in
the pipeline, and how many are held for the data check; click it to open
the pipeline. At the bottom of the pipeline menu, **New pipeline** starts a
new one. Paused pipelines still appear in the menu (with a pause icon) and
collect entries.

Pipelines take stored records only. A result in Person Search, Segment
Search or AI Research has to be saved or added to a list first.

## Send entries

Open the pipeline on the Pipelines page. The **Entries** tab lists every
waiting record with its origin (List or Watchlist) and when it was added.
Select some and click **Send (number)**, or click **Send all**. Progress
shows as "Sending 10 / 40 …". Sent entries leave the Entries tab and appear
under **History**. If you close the tab while sending, the rest simply keeps
waiting.

Each record is read **at the moment it is sent**, so edits and enrichment
you made after adding it are included.

## Records from a "Deleted record" trigger

A list trigger set to **a record is deleted from the list** (its card
says "Deleted record") can hand a deleted record to a pipeline (see "[Triggers — hand records on automatically](https://listplus.ai/en/help/working-in-a-list/list-triggers)"). The
pipeline sends the record as it was at the moment it was deleted. ListPlus
keeps a copy for that, and removes it once the pipeline has sent the
record or you remove the entry from the pipeline. A copy that no pipeline
has sent is removed after 30 days at the earliest, so send such entries
within that time. A pipeline that writes into another list cannot be
chosen for this. The record no
longer exists in the list, so a link back to it, for example in a Slack
message, does not open it.

## Data check

A pipeline can require records to meet conditions before they go out, set
under **Data check** on the Configuration tab — the same field · operator · value
conditions as list triggers. Some targets also add their own requirement
(HubSpot, for instance, always needs an e-mail) shown as a fixed tag.
Records that don't meet the check wait under Entries with the status
**To review**, showing "Missing: …" for an empty required field or "Not met:
…" for an unmet condition. They are not sent and nothing is written to the
History. Enrich or fix the record, then click Send again: it is checked
again and goes out if it now passes. See "[The data check — only send
records that meet your conditions](https://listplus.ai/en/help/pipelines/pipeline-data-check)" for how to build the conditions.

## When sending fails

A failed entry stays under Entries as **Error** (with the number of
attempts), and the reason is shown, for example "The Slack connection
expired – reconnect the account." Fix the cause and send it again; nothing
is retried automatically. Use the **Errors** filter to see only those. To
drop entries you don't want to send, select them and remove them; the
History records them as **Removed**.

## Test before you send

**Test connection** sits at the bottom of the **Configuration** tab. Pick a sample
record **From a list** or **From watchlist** to see exactly what would be sent,
then:

- **Webhook:** sends one real request, marked `"test": true`, and shows the
  response.
- **Slack:** posts one real message to the channel.
- **Email:** sends a test mail to you only.
- **All other targets** (CRMs, sequencers, Sheets, Another list, Other
  app): **Check (writes nothing)** looks the record up in the target and
  reports what would happen, without writing anything.

A Webhook or Slack test is a real delivery and costs that target's price
per record.

The test uses the saved setup, so save your changes first.

## History

The **History** tab lists every attempt with its result (Sent, Failed,
Removed), the time, and for each one the data that was sent and the
target's answer. Filter by Sent or Failed. History is kept for 30 days.

**Related topics:** pipelines-overview · pipeline-marks · email-pipeline ·
pipelines-crm-slack-and-webhook · automatic-release · pipeline-data-check ·
enrich-pipeline · selecting-rows · saved-contacts.

## FAQ

### How do I add records to a pipeline?

Select rows in a list or contacts on the Watchlist (or open a single contact's drawer), then click Add → Send to pipeline and pick the pipeline. The records wait under the pipeline's Entries tab until someone clicks Send (or go out by themselves if the pipeline's Release is set to Automatic). A list trigger can also add records by itself.

### Can I send contacts straight from Person Search or the Inbox to a pipeline?

From the Inbox, yes: select recognized contacts and use Add → Send to pipeline, and they are put on the Watchlist first. Results in Person Search, Segment Search or AI Research must be saved or added to a list first, because pipelines only take stored records.

### Can a contact with alerts enter a pipeline by itself?

Yes. When you set an alert for a contact on the Watchlist, pick a pipeline under "Send news to" in the alert dialog: the contact enters it with the new company and title as soon as a job change or new post is found, and then waits or goes out according to the pipeline's release mode. A change held back as not certain enough enters only after you click "Take it over anyway".

### I added records, why haven't they been sent yet?

On a pipeline with Release set to Manual (the default), entries wait until someone opens the pipeline, goes to Entries and clicks Send or Send all; with Release set to Automatic they go out by themselves. If nothing goes out, check that the pipeline isn't Paused and look for entries marked Check or Error.

### What does the status "To review" or "Missing" mean on an entry?

The pipeline's data check requires a field or condition this record doesn't meet yet, for example an e-mail address, so it waits and is not sent. Fill or enrich the record and click Send again; it is checked again and goes out once it meets the check.

### Does the pipeline send the data as it was when I added the record?

No, each record is read at the moment it is sent. Edits and enrichment results you added after putting it into the pipeline are included.

### What happens if I add the same record twice?

It stays in the pipeline once. The confirmation counts it as "already in", and the existing entry keeps its state.

### A pipeline entry failed, how do I retry it?

Failed entries stay under Entries as Error with the reason shown, for example an expired connection or a missing e-mail. Fix the cause and click Send again; ListPlus does not retry automatically. The Errors filter shows only the failed ones.

### How do I remove an entry from a pipeline without sending it?

On the pipeline's Entries tab, select the entries and remove them. They are logged as Removed in the History, and the record itself stays untouched in your list or on the Watchlist.

### How do I test a pipeline before sending real records?

Open the Configuration tab, expand Test connection at the bottom and pick a sample record From a list or From watchlist. A webhook gets one real request marked "test": true, Slack gets one real message and Email mails only you (a Webhook or Slack test costs one record's delivery price); CRMs, sequencers, Sheets and the other targets use Check (writes nothing) and only report what would happen.

### What does the History tab show and how long is it kept?

Every send attempt with its result (Sent, Failed or Removed), the time, the data that was sent and the target's answer. History is kept for 30 days.

### What happens to a record that reaches a pipeline through a "Deleted record" trigger?

The pipeline sends it as it was at the moment it was deleted, and the kept copy is removed once the pipeline has sent the record or the entry is removed from the pipeline. A pipeline that writes into another list cannot be chosen for this trigger. The record no longer exists in the list, so a link back to it (for example in a Slack message) does not open it.