Workflow triggers determine when automations start in Dalil. They activate automatically when specific CRM or sales events occur, enabling the system to execute predefined actions at the right moment.

Every workflow has exactly one trigger, which you configure as the first node when building or editing the workflow in the visual editor.

Record Triggers

Record triggers activate when CRM records change on the entity you choose: People, Companies, Opportunities, Tasks, Notes, or any custom entity. Four event types are available:

Record is created: runs when a new record is created
Record is updated: runs whenever a record is updated
Record is deleted: runs when a record is deleted
Record created or updated: runs on either event

Common uses include lead routing, data hygiene, and score-based follow-ups. When configuring an update trigger, you can respond to changes in specific fields. For example, only when the Stage field changes.

Pipeline Triggers

Pipeline triggers respond to changes in pipeline records, with the same four event types:

Pipeline record is created: a record is added to a pipeline
Pipeline record is updated: a pipeline record changes, such as when its stage changes
Pipeline record is deleted: a record is removed from a pipeline
Pipeline record is created or updated

They are useful for automating follow-ups and deal management as records move through stages.

Launch Manually

Manual workflows are started on demand rather than by an automatic event, ideal for operational tasks requiring deliberate execution. When configuring a manual trigger you choose its availability:

Global: launch it from anywhere, without selecting a record
Single: launch it on one selected record of the chosen entity
Bulk: launch it on multiple selected records at once

You can also pin a manual workflow so it appears as a quick action on the entity's page.

On a Schedule

Scheduled workflows run automatically at intervals you define:

Every N days (at a set time)
Every N hours
Every N minutes
A custom cron expression for advanced schedules

Use these for periodic tasks like data updates, cleanups, and recurring checks.

Webhook Triggers

External systems can start a workflow by calling its unique webhook URL. You can configure:

HTTP method: GET or POST
Authentication: none, or an API key the caller must supply

The request payload is available to later steps as variables (see Variable Expressions), enabling third-party integrations and cross-platform automation.

Sequence Triggers

A sequence-triggered workflow runs as a step inside an outreach sequence. When a contact reaches that step of the sequence, the workflow executes with that contact's data, useful for mid-sequence CRM updates, task creation, or calling external systems while a campaign runs. See Configuring communication steps.

Enrichment Triggers

Enrichment-triggered workflows run when a record is enriched, based on the enrichment outcome:

Found: enrichment discovered new data (for example, an email address)
Not found: enrichment completed but found nothing
Already present: the data was already on the record
Already attempted: enrichment was skipped because it had already been tried

For example: when enrichment finds an email for a person, a workflow can immediately add them to a sequence.

How Triggers Work

Triggers define the starting point for workflows. Combined with filters, conditions, and branching, they enable intelligent automation that responds differently based on CRM data. The trigger's output (the record that changed, the webhook payload, the enriched field) is available to every later step as variables.

Triggering workflows in Dalil