Workflow triggers define when an automation starts.

In Dalil, a workflow always begins with a trigger. When a specific event happens in your CRM or sales activity, the workflow activates and executes the actions you defined.

Triggers allow Dalil to respond automatically to events such as new leads being created, deals moving across pipeline stages, or scheduled tasks running at specific times.

Understanding triggers is the first step to building powerful automation in Dalil.

What is a workflow trigger

A trigger is an event that starts a workflow.

When the trigger condition occurs, Dalil immediately executes the workflow logic and actions connected to it.

For example:

Trigger: Record created (Person)

Automation actions:

• Assign a sales owner

• Add the person to the pipeline

• Enroll the contact in a sequence

This ensures that every new lead automatically enters the correct sales process.

Record triggers

Record triggers activate workflows when CRM records are created, updated, or deleted.

These triggers work across Dalil entities such as:

• People

• Companies

• Opportunities

• Task

• Notes

Available record triggers include:

• Record created

• Record updated

• Record deleted

• Record created or updated

These triggers are commonly used for lead routing, CRM data management, and sales automation.

Example

Trigger
Record created (Person)

Automation
Add person to onboarding sequence

In this example, every time a new person is added to the CRM, Dalil automatically enrolls them in an onboarding workflow.

Pipeline Triggers

Pipeline triggers respond to changes in opportunity records inside a sales pipeline.

These triggers allow workflows to react when deals progress through the sales process.

Available pipeline triggers include:

• Pipeline record created

• Pipeline record updated

• Pipeline record deleted

• Pipeline stage updated

These triggers are often used to automate follow-ups, deal management, and customer onboarding.

Example

Trigger
Opportunity stage updated

Condition
Stage = Closed Won

Automation actions
Create a task for the customer success team
Add the contact to a customer onboarding sequence

This ensures that every closed deal automatically enters the onboarding process.

Manual triggers

Some workflows are designed to be started manually.

Manual triggers allow users to launch workflows when needed without waiting for a CRM event.

Example

Trigger
Launch manually

Automation
Generate a customer report

Manual workflows are useful for operational tasks that need to be executed on demand.

Scheduled triggers

Scheduled triggers run workflows at specific times or recurring intervals.

This allows teams to automate periodic processes such as reporting, data updates, or reminders.

Example

Trigger
On schedule (every Monday)

Automation
Generate and send weekly sales report

Scheduled workflows help automate routine operations across the CRM.

Webhook triggers

Webhook triggers allow workflows to start when external systems send data to Dalil.

This enables integrations with third-party tools and external automation platforms.

Example

Trigger
Webhook event received

Automation
Create new lead record in Dalil

Webhooks are commonly used when connecting Dalil with external tools or APIs.

Sequence triggers

Sequence triggers activate workflows when events occur inside outreach sequences.

For example, a workflow can react when a contact enters or exits a sequence.

Example

Trigger
Contact exits sequence

Automation
Create follow-up task for sales rep

This allows teams to automate actions based on outreach campaign behavior.

How triggers work with workflow logic

Triggers only define when a workflow starts. Most workflows also include logic that determines what actions should run.

For example:

Trigger
Opportunity stage updated

Condition
Stage = Closed Won

Action
Send onboarding message

Conditions, filters, and branching logic allow workflows to respond differently depending on the data.

Key outcome

Workflow triggers allow Dalil to automatically react to events happening across your CRM, pipelines, conversations, and integrations.

By using triggers such as record updates, pipeline stage changes, scheduled events, or external webhooks, teams can automate sales processes and ensure that important actions always happen at the right time.