Help Center

Docs

Everything you need to know about using Laureo

Actions & Conditions

Configure workflow actions and conditional logic

Action Types

Actions define what a workflow does when it executes.

Each action performs a specific operation on your CRM data or sends a communication. You can add multiple actions to a workflow, and they execute sequentially in the order they appear.

Available Actions

Send Email— Send an email using a predefined template. Select the template, configure the recipient (the record's email, the assigned owner, or a specific address), and customize the subject line. Templates support merge fields that pull data from the triggering record.
Create Task— Automatically create a task and assign it to a user. Configure the task subject, description, due date (relative to the trigger event, e.g., 3 days after), and priority. The task is linked to the triggering record.
Update Field Value— Change the value of a field on the triggering record. Select the field to update and provide the new value. Use this to automatically set status, priority, tags, or any other field based on workflow logic.
Add Tag— Apply one or more tags to the triggering record. Tags help you segment and filter records that have been processed by a workflow.
Assign to User— Assign the triggering record to a specific user or use round-robin assignment to distribute records evenly across a team.
Send Notification— Send an in-app notification to a specific user or the record owner. Notifications appear in the notification bell and can include a link to the triggering record.

Merge fields in emails

When using the Send Email action, insert merge fields like {company_name}, {contact_name}, or {opportunity_value} into your email template. These fields are automatically populated with data from the triggering record when the email is sent.

Condition Types

Conditions control whether a workflow's actions should execute.

Conditions are optional filters that evaluate the triggering record before actions run. If the conditions are not met, the workflow skips its actions for that particular trigger event. Use conditions to target your automations precisely.

Available Conditions

Field Equals— Checks if a field on the triggering record matches a specific value. For example, only run when Status equals "Active" or Type equals "Customer".
Field Contains— Checks if a text field contains a specific substring. Useful for matching partial values in names, descriptions, or notes.
Date Comparisons— Evaluates date fields against relative or absolute values. For example, only run when the Next Follow-up date is within the next 7 days, or when the Created Date is more than 30 days ago.
Numeric Comparisons— Checks if a numeric field is greater than, less than, or equal to a threshold. Use this for value-based routing (e.g., only trigger when the opportunity value exceeds $10,000).
Is Empty / Is Not Empty— Checks whether a field has a value. Useful for ensuring required data exists before sending an email or creating a task.

AND / OR Logic

Combine multiple conditions with logical operators.

When you add multiple conditions to a workflow, you can combine them using AND or OR logic to create precise targeting rules.

AND Logic

All conditions must be true for the workflow to execute. Use AND when you need every criterion to be met. For example: Type equals "Customer" AND Status equals "Active" ensures the workflow only runs for active customers.

OR Logic

At least one condition must be true for the workflow to execute. Use OR when any of several criteria should trigger the workflow. For example: Priority equals "High" OR Value is greater than $50,000.

Combining AND and OR

You can nest AND and OR groups to build complex condition logic. For example: (Type equals "Customer" AND Status equals "Active") OR (Priority equals "High"). This runs the workflow for all active customers and any high-priority records regardless of type.

Action Ordering and Chaining

Control the sequence in which actions execute.

Actions in a workflow execute sequentially from top to bottom. The order matters because earlier actions can affect the data that later actions use. For example, an "Update Field Value" action that sets a status should come before a "Send Email" action that references that status in its template.

Reordering Actions

Drag and drop action blocks in the workflow builder to rearrange their execution order. The visual flow updates automatically to reflect the new sequence.

Action Chaining

Chain actions together to create multi-step automations. A common pattern is: Update Field Value (set status to "Onboarding") → Create Task (assign onboarding checklist) → Send Email (welcome message to the contact) → Send Notification (alert the account manager). Each action completes before the next one begins.

Action failures

If an action fails (e.g., an email cannot be sent because the recipient address is missing), the workflow logs the error and continues to the next action. Review the workflow execution history to identify and resolve failed actions.

Trigger Types— Configure triggers for entities and events Building a Workflow— Build automation workflows step by step Workflows List— View and manage your automation workflows Reports Gallery— Browse built-in reports and analytics

Trigger Types

Reports Gallery