# Adding records to a pipeline and sending them Source: https://listplus.ai/en/help/pipelines/send-records-to-a-pipeline Last updated: 2026-09-28 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". ## Add records 1. **From a list:** select the rows, then in the selection bar click **Add → Send to pipeline → (pipeline name)**. 2. **From Saved:** select contacts and use **Add → Send to pipeline** the same way. 3. **From the contact drawer:** for a saved contact, use **Add → Send to pipeline** in the drawer. 4. **From the Inbox:** select recognized contacts and use **Add → Send to pipeline**; they are saved to Saved first, then added. 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 Saved) 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. ## Data check ("Only send with") A pipeline can require fields, for example an e-mail address, under **Data check → Only send with**. Some targets add their own requirement (HubSpot, for instance, always needs an e-mail). Records missing a required field wait under Entries with the status **Check** and show "Missing: …". They are not sent and nothing is written to the History. Enrich or fill the missing field, then click Send again: they are checked again and go out if complete. ## 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 **Flow** tab. Pick a sample record **From a list** or **From Saved** 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. 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 · selecting-rows · saved-contacts. ## FAQ ### How do I add records to a pipeline? Select rows in a list or contacts in Saved, then click Add → Send to pipeline and pick the pipeline. For a single saved contact, use Add → Send to pipeline in its contact drawer. The records wait under the pipeline's Entries tab until someone clicks Send. ### 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 saved to Saved 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. ### I added records, why haven't they been sent yet? Pipelines never send on their own. Open the pipeline on the Pipelines page, go to Entries and click Send for selected entries or Send all. If nothing goes out, check that the pipeline isn't Paused. ### What does the status "Check" or "Missing" mean on an entry? The pipeline's data check (Only send with) requires a field this record doesn't have, for example an e-mail address, so it waits and is not sent. Fill or enrich the missing field and click Send again; the record is checked again and goes out when complete. ### 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 Saved. ### How do I test a pipeline before sending real records? Open the Flow tab, expand Test connection at the bottom and pick a sample record From a list or From Saved. A webhook gets one real request marked "test": true, Slack gets one real message and Email mails only you; 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.