Triggers — hand records on automatically

A trigger watches one list and acts on its own: "when a record meets these conditions, do this." It's the way to hand records to a pipeline, change their status, or tag them without doing it by hand every time.

Where to find it#

Open a list and click Triggers in the list header (the lightning icon, next to Analyze, Record and Enrich). Setting up or changing a trigger is for the workspace's owner and admins; other members can see the triggers and what they've handed over, but not change them.

When#

Every trigger has conditions built the same way as a pipeline's data check — field, operator, value, grouped with AND and OR — but with more to choose from, since a trigger belongs to one list: any of that list's own columns, an evaluation goal, the record's status, its e-mail verification, or whether it's already in another pipeline. Choose when they're checked:

• New record — only records that are new in the list.
• Conditions met — every record, checked again whenever it's added or changed.

Leaving the conditions empty with "New record" fires on every new record.

Then#

Add up to 5 actions, run in this order — a step that fails stops the ones after it, but what already happened stays done. Choose from:

• Hand over to pipeline — adds the record to one of your pipelines.
• Set status — sets one of the list's own statuses.
• Hide — a shortcut for setting the record's built-in hidden status.
• Set tag — adds a tag, kept if the record has it already.
• Enrich — a shortcut that hands the record to one of your Enrich-target pipelines.

A record the trigger already acted on isn't acted on again for the same trigger, so re-saving or a later change never duplicates a hand-over.

When triggers run#

An active trigger checks matching records automatically, usually within moments of a record being added or changed — there's nothing to click. Only active triggers run; pause one with the switch on its card to stop it without losing its setup.

Records already in the list#

While building a trigger with "Conditions met", tick Include records that already match to also run it once, immediately on save, for records already in the list. It's unavailable once there's nothing left to include, and it never repeats — later changes are covered by the trigger running as usual.

Starting from a template#

New lists with no triggers yet offer ready-made ones to start from and adjust: hand over decision-makers or "ready" records to a pipeline, hide unusable records, tag your ICP, or sort out freemail and disposable addresses before spending credits on them. Pick one with Use, then change its conditions or actions to fit.

Limits#

Up to 20 triggers per list, up to 5 actions per trigger, and up to 5 OR-groups of up to 12 conditions each in the "When".

Problems shown on a trigger#

A trigger's card names why its last run couldn't act, for example "The pipeline no longer exists" (it was deleted — choose another one), "The pipeline is full" (send or remove some of its entries first), or "A condition uses a column this list no longer has" (nothing is handed over until you fix it). Review trigger opens the editor on the exact problem.

Related topics: pipelines-overview · send-records-to-a-pipeline · enrich-pipeline · list-statuses · segments-and-tags · roles-and-permissions.

FAQ#

What is a trigger in ListPlus?#

A trigger watches one list and acts automatically when a record meets your conditions: hand it to a pipeline, set a status, hide it, or add a tag. Open a list and click Triggers in the side panel to set one up.

What can a trigger do when a record matches?#

Up to 5 actions in order: hand the record to a pipeline, set one of the list's own statuses (Hide is a shortcut for the built-in hidden status), or add a tag. There's also an Enrich shortcut that hands the record to a pipeline set up to fill its missing fields.

What fields can a trigger's conditions check?#

Any column of that list, an evaluation goal, the record's status, its e-mail verification, or whether it's already in another pipeline — more than a pipeline's own data check can see, since a trigger belongs to one specific list. Build them with AND inside a group and OR between groups.

What's the difference between "New record" and "Conditions met"?#

New record only fires for records that are new to the list; Conditions met checks every record again whenever it's added or changed, so it also catches records that become a match later. Pick New record for "do this once, on arrival" and Conditions met for anything that should stay true over time.

Do I need to click something for a trigger to run?#

No, an active trigger checks matching records by itself, usually within moments of a record being added or changed. Pause it with the switch on its card if you want to stop it without deleting its setup.

Can a trigger also act on records already in my list?#

Yes, tick Include records that already match while saving it (only available with Conditions met) and it runs once, immediately, for the records already there. It's a one-time pass — after that, the trigger runs as usual on new and changed records.

Why does my trigger's card show a warning?#

It names why the last run couldn't act — commonly that the pipeline it hands records to was deleted, is full, or that a condition uses a column the list no longer has. Click Review trigger to open the editor on the exact problem.

What happens to records a trigger already handed over if I delete it?#

They stay exactly where the trigger put them — in their pipeline, with their status or tag. Deleting a trigger only stops it from acting on future records; it never undoes past hand-overs.

How many triggers can one list have?#

Up to 20 triggers per list, each with up to 5 actions and up to 5 OR-groups of up to 12 conditions. If you're close to the limit, combine similar triggers into one with an OR group instead of adding another.