Pipelines — send records on to your CRM, Slack, e-mail or API

Updated Markdown

A pipeline hands records from ListPlus on to another tool: your CRM, a sequencer, a Slack channel, a Google Sheet, your own webhook or API, another list, or an e-mail to your team. You pick the records, they wait in the pipeline, and you send them with one click. A record is a row of a list, a contact on the Watchlist, or a company on the Watchlist (see "Pipelines to Slack, a CRM or a webhook" for what the targets do with a company).

Where to find it#

Click Flows in the left navigation bar. Every pipeline of your workspace is in the column at the left twice, and each has two pages:

  • Activity → Pipelines opens the pipeline's Activity: one filter at the page's left edge, To review · Running · Done. To review holds the records waiting to be sent and any that need attention — one row per record with a checkbox, 50 at a time with Show N more below — Running what an automatic pipeline is sending by itself, Done every send attempt with its result ("Kept for 30 days." at the bottom). With nothing waiting, a small icon and one sentence say so, with How do entries get here? to open the steps.
  • Pipelines (with a + for a new one; the pipelines are plain rows there) opens the pipeline's Setup: three steps as cards — the optional Data check, Release (manual or automatic) and the target step, with Test connection at the end of the target step. Click a card to open or close it; several can be open at once. A choice under Release is saved right away; the other two show Save and Cancel once you change something.

The two pages link each other at the right of the pipeline's subtitle: Setup → and Activity →.

The number on Flows in the left bar is everything that waits for you under Activity → To review, including pipeline entries to release and entries that failed; the number on a pipeline's row is what waits in that pipeline.

Create a pipeline#

  1. On the Pipelines page, click Create pipeline (or pick one of the suggestions on the empty Pipelines page, such as "Contacts into your CRM" or "Notify your team in Slack").
  2. Choose what should happen to each contact, for example HubSpot — Create or update contact or Slack — Post a message to a channel.
  3. Fill in the target's settings (account, channel, campaign, URL …) and, under Data & advanced settings, which fields to send and the optional data check.
  4. Click Create pipeline, then run Test connection with a real record before you send anything for real.

What a pipeline can send to#

  • Within ListPlus: Another list, Email (a digest mail to members of your workspace).
  • External: Webhook (n8n, Make, Zapier or your own API), Slack, HubSpot, Attio, Salesforce, Pipedrive, Lemlist, Instantly, Google Sheets, Email draft (a draft in your own mailbox), and Other app for further tools.

See "Pipelines to Slack, CRMs, sequencers, Sheets and webhooks" for what each target does, "Sending entries by e-mail to your team" for the Email target, and "Enrich in a trigger" for enriching (an action of a list's trigger, not a target). "Enrichment by a trigger" follows one record through it — from the trigger to the result under Done, and why a manual one needs a second Send.

Release: manual or automatic#

Every pipeline has a Release setting, on its Setup page. Manual (the default): entries wait under To review in the pipeline's Activity until someone in your workspace clicks Send for the selected ones or Send all. Automatic: waiting entries are sent right away, optionally capped by a daily limit (records per day) — the rest waits for the next day. See "Automatic release — sending without a click" for pausing on repeated failures, the limit e-mail, and what happens to entries held by the data check. The Active / Paused switch at the top right still controls whether a pipeline can send at all, in either release mode: a paused pipeline keeps collecting entries but sends nothing until you activate it again.

Who can do what#

Pipelines belong to the workspace, so everyone in it sees the same pipelines, entries and history. Owners and admins create, change, pause, duplicate and delete pipelines; every member can add records, send entries, remove entries and run a test. Members see the hint "Owners and admins of this workspace set up and change pipelines. You can add and send entries."

Cost and limits#

Adding records to a pipeline costs no credits. A delivery costs a fixed number of credits per record that arrived — the price is shown on the target's tile and differs by kind of target (CRM, sequencer, Slack, Sheets, Webhook); all prices are in the price list. ListPlus checks your balance before the send and before each record, and charges a record only once it arrived. A target that reaches a connected tool (Slack, HubSpot, Salesforce, Pipedrive, Attio, Google Sheets, Lemlist, Instantly, Email draft or Other app) needs Pro (or Basic's one connected tool). A Slack, Webhook or Email draft test really delivers and costs one record's price; a CRM, sequencer, Sheets, Other app or Another list test only checks (writes nothing) and costs nothing. Webhook, Team email and Another list need no plan; Team email and Another list cost nothing. Enriching is not a target but a trigger's action, with its own per-record budget (see "Enrich in a trigger — fill a record's own missing fields"). The tool you send to may have its own costs (for example, Lemlist or Instantly credits for their own e-mail checks). Limits: 50 pipelines per workspace, 5,000 entries waiting in one pipeline, and 1,000 records per add.

Related topics: send-records-to-a-pipeline · pipeline-marks · email-pipeline · pipelines-crm-slack-and-webhook · automatic-release · pipeline-data-check · enrich-pipeline · enrichment-in-pipelines · list-triggers · roles-and-permissions · crm-credentials.

FAQ#

What is a pipeline in ListPlus?#

A pipeline hands records from your lists or the Watchlist on to another tool, such as HubSpot, Salesforce, Slack, Lemlist, Google Sheets, a webhook for n8n/Zapier/Make, another list, or an e-mail to your team. You add records (or a list trigger hands them over), they wait under To review in the pipeline's Activity, and they are sent when you click Send.

Where do I find pipelines?#

Click Flows in the left navigation bar; your pipelines are listed in the column at the left, under Activity and again under Pipelines. Under Activity a pipeline opens its Activity with the filter To review (waiting records), Running (what an automatic pipeline is sending) and Done (send results, kept 30 days); under Pipelines it opens its Setup (data check, release, target and Test connection). Setup → and Activity → beside the pipeline's subtitle switch between the two.

Which tools can a pipeline send records to?#

Webhook (n8n, Make, Zapier or your own API), Slack, HubSpot, Attio, Salesforce, Pipedrive, Lemlist, Instantly, Google Sheets, Email draft (a personal email to each contact, as a draft in your own mailbox) and Other app, plus two targets within ListPlus: Another list and Team email. Enriching is not a target but an action of a list's trigger. You choose the target when you create the pipeline with Create pipeline.

Do pipelines send records automatically or on a schedule?#

Only if you set a pipeline's Release to Automatic on its Setup page: then waiting entries go out right away, optionally capped by a daily limit, with no delayed or date-based sending either way. Left on Manual (the default), records wait under To review until someone clicks Send or Send all. A paused pipeline keeps collecting entries but sends nothing until it's activated again.

Do pipelines cost credits or need a paid plan?#

Each record that arrives at the target costs credits — the price is on the target's tile and in the price list; Team email and Another list cost nothing. Targets that reach a connected tool (Slack, HubSpot, Salesforce, Pipedrive, Attio, Google Sheets, Lemlist, Instantly, Email draft, Other app) need Pro (on Basic: one connected tool for 50 credits per 30 days); Webhook, Team email and Another list work on every plan. After a downgrade the connected accounts stay connected, but a send answers that the plan is needed.

Who can create or change a pipeline?#

Only the owner and admins of the workspace can create, edit, pause, duplicate or delete pipelines. Every member can add records to a pipeline, send or remove its entries and run a test.

Are pipelines shared with my team?#

Yes. Pipelines belong to the workspace, so every member sees the same pipelines, waiting entries and history, and anyone can send what a colleague added. If you have several workspaces, each one has its own pipelines; switch workspaces to see the others.

How do I create a pipeline?#

In Flows, click the + beside Pipelines (or Create pipeline on the Pipelines page), choose what should happen to each contact (for example HubSpot, Slack or Webhook), fill in the target's settings and click Create pipeline. Then open Test connection on the pipeline's Setup page and try it with a real record before sending entries.

What happens when I pause a pipeline?#

Records can still be added and wait under To review, but nothing is sent; Send shows "The pipeline is paused – activate it to send." Use the Active / Paused switch at the top right of the pipeline to change it (owners and admins only).

How many pipelines and entries can I have?#

Up to 50 pipelines per workspace, up to 5,000 entries waiting in one pipeline, and up to 1,000 records per add. If a pipeline is full, send or remove some entries first; for larger selections, add them in several steps.

Can I copy or delete a pipeline?#

Yes, owners and admins can open More actions (the ⋮ button in the head of the pipeline's Setup, beside Pause) and choose Duplicate or Delete. A copy is created without its secrets (keys, tokens, signing secret), so set them again before you activate the copy. Deleting removes the setup and its secrets and cannot be undone.