Knowledge CenterAPI ReferencesDalil MCPClaude Skills

Working with pipelines

Create custom pipelines for any process (sales, fundraising, onboarding) with their own stages, fields, views, and automation.

Updated August 6, 20263 min read

Pipelines are how Dalil models any staged process. The classic example is a sales pipeline (Discovery → Proposal → Negotiation → Closed), but a workspace can run any number of pipelines (fundraising, recruiting, customer onboarding, partnerships), each with its own stages, fields, views, and automation.

Your pipelines are listed in the sidebar under the Pipelines section.

What a pipeline is

A pipeline is a dedicated space where records move through stages:

  • Each pipeline defines its own stages: the steps of your process
  • Each pipeline has its own fields: the data you track for records in that process (e.g., Kick-off Date and CSM for onboarding; Round Size and Lead Investor for fundraising)
  • Pipeline records connect back to your core CRM records, so a company can simultaneously sit in your sales pipeline and your onboarding pipeline with different stages and data in each

Because pipelines are full entities, everything that works on People and Companies works on them: views, custom fields, filters, and automation.

Viewing a pipeline

Pipelines support multiple views:

  • Kanban: one column per stage; drag a card to move a record between stages
  • Table: rows and columns, ideal for editing data and bulk operations, with optional grouping by stage

Create different views of the same pipeline for different jobs: a Kanban board for the weekly pipeline review, a table sorted by amount for forecasting.

Adding records to a pipeline

  • From the pipeline: create a record directly in a stage column
  • From a record page: link a person or company into a pipeline from their record
  • From the inbox: use Link a Pipeline / Opportunity on any conversation, and update the stage right from the thread (see Linking conversations)
  • From workflows: the Create/Update Pipeline Record action adds records automatically, e.g. every qualified lead

Pipeline highlights

On a pipeline record's page, Highlights surface the fields that matter most for that process, and you can edit which fields appear, so the record view always leads with what your team actually checks.

Automating pipelines

Pipelines have first-class automation support in Workflows:

Triggers

  • Pipeline record is created / updated (e.g., a stage change) / deleted / created-or-updated

Actions

  • Create/Update Pipeline Record, Update Pipeline Record (move stage), Delete, Find, Bulk Update, Bulk Delete

Typical patterns: enroll a contact in an onboarding sequence when their record reaches Closed Won; create a task for the owner when a deal enters Negotiation; exit a contact from outreach when a pipeline record is created for them.

Pipelines and the rest of the system

  • Scoring: opportunities carry a Dalil Score that reflects deal momentum
  • Analytics: stage-based charts (funnels, stage movement) are built on pipeline data; see Analytics & dashboards
  • Notifications: get notified when teammates change pipeline stages
  • API: pipelines are dynamic entities; integrations discover them via the metadata API before reading or writing records

Key outcome

Pipelines turn Dalil from a contact database into a process engine: every staged motion your team runs (selling, onboarding, fundraising) gets its own stages, data, views, and automation, while staying connected to the same People and Companies.

Was this article helpful?

Your feedback helps us improve our documentation.