# Automatic release — sending without a click

Source: https://listplus.ai/en/help/pipelines/automatic-release
Last updated: 2026-10-01

Every pipeline has a **Release** setting on its Flow tab: **Manual**
(the default) waits for you to click Send, **Automatic** sends waiting
entries by itself. This article covers Automatic; see "Pipelines — send
records on to your CRM, Slack, e-mail or API" for the rest of a pipeline's
setup.

## Turning it on

Open the pipeline, go to the **Flow** tab and click the pencil on the
**Release** step. Choose **Automatic** — optionally with **At most … records
per day** (leave it empty for no limit) — and click **Save**. Entries
already waiting are sent within moments of saving.

## Who it sends as

An automatic pipeline sends in the name of the person who created the
pipeline. If that person later leaves the workspace, it sends as the
workspace owner instead.

## The daily limit

With a daily limit set, a run stops for the day once it's reached and the
rest of the waiting entries continue the next day. The person it sends as
gets one e-mail the first time in a day a run hits the limit, so nothing
goes quiet without a reason. The button still ignores the limit: clicking
Send yourself always goes out.

## Pausing on failures

An automatic pipeline that keeps failing pauses itself — after 5 failed
attempts in a row for most targets, or on the very first failure for a
target that sends one batch for everyone (Email) — and e-mails the person
who set it up. Fix the cause (for example, reconnect an expired account),
then switch the pipeline back to Active; nothing is retried by itself, so
failed entries need the Send button afterwards.

## What happens to entries held by the data check

On a manual pipeline, an entry held as "Check" waits until you click Send
again. An automatic pipeline rechecks those entries itself on every run —
after first trying the ones that are simply waiting — so a record that
becomes complete later (an e-mail gets enriched, say) goes out on its own,
without anyone clicking anything.

## Switching back to Manual

Switching Release back to Manual leaves every entry exactly where it is;
nothing is sent until someone clicks Send. A daily limit you had set stays
stored, so it's there again if you switch back to Automatic.

**Related topics:** pipelines-overview · send-records-to-a-pipeline ·
pipeline-data-check · pipeline-marks · enrich-pipeline · list-triggers.

## FAQ

### What's the difference between Manual and Automatic release?

Manual (the default) holds every entry under Entries until someone clicks Send or Send all. Automatic sends waiting entries by itself, right away, optionally capped by a daily limit you set when switching it on.

### How do I switch a pipeline to automatic sending?

Open the pipeline's Flow tab, click the pencil on the Release step, choose Automatic, optionally set a daily limit, and save. Entries already waiting go out within moments.

### Whose name does an automatic pipeline send under?

The pipeline's creator. If that person later leaves the workspace, the pipeline sends as the workspace owner instead, so it keeps working.

### What happens when a pipeline reaches its daily limit?

Sending stops for the rest of that day and the remaining entries continue the next day. The person the pipeline sends as gets one e-mail the first time a run hits the limit, so you know why it slowed down.

### Why did my automatic pipeline pause itself?

It failed 5 times in a row (or once, for a target like Email that sends one batch for everyone) and paused to stop wasting attempts, e-mailing the person who set it up. Fix the cause shown on the failed entries, then set the pipeline back to Active.

### Does automatic release retry failed entries?

No. Failed entries stay under Entries as Error and need the Send button, exactly like on a manual pipeline; only entries held by the data check are rechecked automatically on each run.

### Can I still send manually while a pipeline is set to Automatic?

Yes, clicking Send or Send all yourself always goes out immediately and ignores the daily limit — the limit only applies to what the pipeline sends by itself.

### If I switch a pipeline back to Manual, what happens to entries that were waiting?

Nothing changes for them — they stay under Entries exactly as they were, and nothing is sent until someone clicks Send. Any daily limit you had set stays stored for if you switch back to Automatic.