Moving a card is a signal, and a pipeline automation is what turns that signal into work: the welcome email when an account reaches “Live”, the ticket for the team when something lands in “At risk”.
Pipeline automations are workflows with a pipeline entry as their subject instead of a conversation. They're listed under Pipelines on the Workflows page.
Two routes, same result. From the pipeline's settings, Automations → New automation creates one already scoped to that pipeline and lists the ones it already has, with their Live or Draft state. From the Workflows page, Pipeline automation starts an unscoped one you point at a pipeline yourself.
Like every workflow, it does nothing until you publish it.
There are two.
On entry added to pipeline — something joined the board.
On stage changed — an entry moved. You can watch one stage or any stage.
Several automations can react to the same event. Unlike conversation workflows, they don't compete — every one that matches runs.
A condition narrows things further: the entry's current stage, this pipeline's own fields, office hours, and the attributes of the underlying record — contact attributes on a contact pipeline, company attributes on a company one.
Field and attribute options only appear once the trigger has a pipeline selected, since without one there's nothing to read them from.
Six actions are specific to pipelines:
Move stage — send the entry somewhere else on this board.
Set entry field — write a value into one of this pipeline's fields.
Add to another pipeline — hand the record on, for instance from onboarding to renewals.
Create ticket — raise a conversation, linked back to this entry.
Email contact — send a message to the person behind the entry.
Notify teammate — an internal notification to people or a team, linking to the pipeline.
Alongside those you get the general-purpose steps: Condition, Delay, Custom API action and Pass to workflow. There's no message step, because there's no conversation to send a message into.
On a contact pipeline, Email contact and Create ticket use that contact. On a company pipeline there's no single obvious person, so Gleap uses the company's most recently active contact.
Both steps are skipped when there's nobody to use — a company with no contacts, or a contact with no email address. The automation doesn't fail; it moves on. If a mail didn't arrive, a missing address is the first thing to check.
An automated email doesn't appear as a conversation in your inbox. A reply to it does.
A stage change made by Move stage doesn't set off stage-change automations, so an automation can't retrigger itself or its neighbours by moving a card.
One exception is deliberate: Add to another pipeline does fire the target pipeline's “entry added” automations — that's the point, since it's how a record is handed from one process to the next. Two boards that add records to each other will keep each other busy.
The target has to hold the same record type. A company pipeline can't hand its entries to a contact pipeline; that step is skipped.
The entry panel's Activity section names the automation that ran and says when one failed. It's the fastest way to answer “did this customer get the email?” for a specific account.
