Help Center

Docs

Everything you need to know about using Laureo

Conditions, Waits & Actions

The steps you drop into a flow: three ways to branch, the durable Wait, the Merge, and the actions that change your CRM.

Three ways to branch

Logic steps decide whether, and where, a record continues.

All three read conditions you build against the record’s fields. They differ in what happens next:

Field	Description
Filter	Stop the automation unless every condition is met. A record that fails simply ends here.
If / Else	Split into a true path and a false path. Records that match the conditions take the true branch; everything else takes the false branch.
Switch	Send each record down a lane based on one field’s value, with a default lane for anything that does not match.

A condition is a field, an operator, and a value, for example “stage equals Won”. You can group several conditions with and / or to build exactly the test you need.

On a project automation, conditions and the “when a field changes” trigger can read the project’s stage, its delivery health (on track, at risk, or off track), its archived state, and its start, target end, and actual end dates. Pair a field-change trigger with a health or stage condition to react the moment a project slips or moves forward.

Merge, rejoining branches

Author the steps after a split once, not once per path.

After an If / Else or a Switch sends records down different lanes, a Merge step brings those lanes back together so everything past it continues on a single shared path. The card reads both paths continue from here. Whatever steps you put below the Merge run for records arriving from any branch.

Without a Merge you would have to copy the same closing steps into every lane. With one, you author them once.

The Wait step

Pause the automation, then resume: three flavors for three kinds of timing.

A Wait is durable: the automation genuinely pauses at that step and picks up where it left off when the wait resolves, even days later. There are three flavors:

Field	Description
Wait a fixed amount of time	Resume after a set delay of minutes, hours, or days. Up to 90 days total.
Wait until a date	Resume on a date, read from a field on the record or set explicitly. An optional offset resumes a set time before or after that date.
Wait until a condition is met	Re-check the record on a schedule and resume the moment a condition becomes true. A required timeout decides what happens if it never does, up to 90 days.

Every wait is capped at 90 days. A “wait until a condition” that never becomes true will continue down its timeout path once the timeout you set is reached, so it never gets stuck forever.

Actions

The steps that make a change in the CRM or send something out.

Field	Description
Assign to user	Hand the record to a specific teammate.
Assign round-robin	Distribute records evenly across a team.
Update field	Set a field on the record to a fixed or copied value.
Create task	Create a follow-up task linked to the record.
Log activity	Log a call, email, meeting, or note on the record.
Send notification	Notify a teammate inside the CRM.
Send email	Send a transactional email to the record’s contact.
Call webhook	Call an external URL with the record’s data.
Create project from template	On a deal automation, create the delivery project for the deal, optionally seeded from a project template. Available on deal (opportunity) automations only.

Most action fields accept dynamic values that pull from the record. For example, a Create task step can assign to the record’s owner instead of a fixed person, and a Send email step can address the record’s contact.

The Create project from template action packages the deal handoff: pair it with a “when stage becomes Closed Won” trigger to spin up the delivery project automatically the moment a deal is won. It only ever creates one project per deal, so it is safe to re-run. Leave the template blank to create a plain delivery project from the deal, or pick a template to seed the project’s tasks.

Building an Automation· Add and configure these steps AI Agent Steps· Hand a step to a reasoning agent instead Triggers· Choose what starts the flow Runs & Analytics· See each step recorded per run

Triggers

AI Agent Steps