Assign Pipedrive deals by criteria using Workflow Automation

low complexityCost: $0 (included on Growth+)

Prerequisites

Prerequisites
  • Pipedrive account on Growth plan or higher ($24/seat/mo+)
  • Slack workspace with permissions to install apps
  • Admin access in Pipedrive (required to install marketplace apps and create automations)
  • A documented set of routing rules mapping deal criteria to owners (e.g., web leads to Rep A, referrals to Rep B)

Why Workflow Automation?

Workflow Automation is the zero-dependency option — everything runs inside Pipedrive with no external tools, API keys, or hosting. You define a trigger ("Deal created"), add a condition (source, pipeline, value range), and set the action to update the owner field. Dealbot for Slack handles notifications. Setup takes under 10 minutes per routing rule, and there's no ongoing cost beyond your existing Pipedrive license.

The trade-off is significant: Pipedrive Workflow Automation has no built-in round-robin. It cannot rotate through a list of reps or maintain a counter. Each automation assigns to one specific owner based on matching criteria. This works well when your routing rules are deterministic (all inbound demo requests go to Rep A, all partner referrals go to Rep B), but it does not distribute deals evenly across a team the way a true round-robin does.

This is criteria-based routing, not round-robin

Pipedrive Workflow Automation assigns deals to a fixed owner per rule — it cannot cycle through a rep roster. If you have 4 reps and want equal distribution regardless of deal attributes, this approach won't achieve that. For true round-robin rotation, use the n8n approach instead, which persists a counter between executions and cycles through your rep list automatically.

How it works

  • "Deal created" trigger fires when a new deal is added to any pipeline
  • Condition filters for deals matching specific criteria (lead source, pipeline, deal value, custom field)
  • Action updates the deal's owner field to the designated rep for that criteria
  • Slack notification action sends a Dealbot message to a channel with deal name, value, and assigned owner
  • One automation per routing rule — if you have four criteria-to-owner mappings, you create four automations

Step 1: Plan your routing rules

Before creating automations, map out which criteria route to which rep. Each rule becomes its own automation.

CriteriaConditionAssigned Owner
Web leadsLead source = "Web"Alice Smith
ReferralsLead source = "Referral"Bob Jones
Enterprise dealsDeal value > $50,000Carol Chen (senior AE)
Partner pipelinePipeline = "Partners"Dave Kim

You can use any deal field as a condition: lead source, pipeline, deal value, custom fields, organization, or contact person fields. The key constraint is that each automation maps to exactly one owner — you cannot rotate within a single rule.

Handle the 'catch-all' case

Deals that don't match any of your criteria-based automations will keep whatever default owner Pipedrive assigns (usually the user who created the deal). Consider creating a final automation with broad conditions that assigns unmatched deals to a team lead or shared queue owner for manual triage.

Step 2: Create your first Workflow Automation

Navigate to Automations > Create (or Automations > + Automation depending on your UI version).

Configure the trigger

  • Trigger type: Event-based
  • Event: Deal created
  • Entity: Deal

This trigger fires once when a new deal is added to Pipedrive — either manually, via API, or through a web form.

Add a condition

Click Add condition after the trigger to filter for your first routing rule:

  • Field: Select the field that defines your rule (e.g., Lead source, Pipeline, Deal value)
  • Operator: Equals, Contains, Greater than, etc.
  • Value: The specific value to match (e.g., "Web", "Partners", or a value threshold)

For example, to route web leads:

  • Field: Lead source
  • Operator: Equals
  • Value: Web

Pipedrive supports AND conditions within a single automation. If your rule requires multiple criteria (e.g., web leads AND deal value under $10,000), add additional condition rows — all must match for the automation to proceed.

Add the assignment action

Click Add action after the condition:

  1. Select Update existing deal
  2. Field to update: Owner
  3. New value: Select the rep from the dropdown (e.g., Alice Smith)

This sets the deal's owner_id to the designated rep the moment the deal is created and the condition matches.

'Deal created' does not fire for deals converted from leads

If your team uses Pipedrive's Leads Inbox and converts leads into deals, the "Deal created" trigger fires — but any lead source data must be mapped to the deal during conversion. If custom fields aren't carried over, your conditions won't match. Test the full lead-to-deal conversion flow to verify your routing conditions work with converted deals, not just manually created ones.

Step 3: Add a Slack notification action

If you haven't already installed Dealbot, navigate to Settings > Tools and apps > Marketplace apps, search for Slack, and install Dealbot for Slack. Authorize access to your Slack workspace and select which channels Dealbot can post to.

Back in your automation, add a second action after the owner update:

  1. Select Send Slack channel message
  2. Choose the target Slack channel from the dropdown (e.g., #sales-inbound)
  3. Configure the message content using merge fields:
New Deal Assigned
Deal: [Deal Name]
Value: [Deal Value]
Pipeline: [Pipeline]
Assigned to: [Deal Owner]

Insert merge fields using Pipedrive's field picker (the {+} icon in the message editor) rather than typing field names manually.

Dealbot sends plain text only

Dealbot messages use a fixed format — no Block Kit, no buttons, no rich formatting. The message includes the merge fields you select but cannot link directly to the Pipedrive deal record. If you need formatted Slack messages with clickable links, use the n8n approach with an Incoming Webhook instead.

Step 4: Create additional automations for other routing rules

Repeat Steps 2-3 for each row in your routing table. Each automation handles one criteria-to-owner mapping.

Name each automation clearly so they're easy to manage:

  • "Route Web Leads to Alice"
  • "Route Referrals to Bob"
  • "Route Enterprise Deals to Carol"
  • "Route Partner Pipeline to Dave"

You can point all automations to the same Slack channel (e.g., #sales-inbound) or use different channels per rule (e.g., enterprise deals to #enterprise-deals).

Automation evaluation order

If a deal matches conditions in multiple automations, all matching automations will fire. The last one to execute wins for the owner field update. Ensure your conditions are mutually exclusive (e.g., don't overlap "value > $25K" and "value > $50K" unless you want cascading updates). Use specific, non-overlapping conditions to avoid conflicts.

Step 5: Activate all automations

  1. Open each automation and toggle it to Active
  2. Test by creating a deal that matches each rule — verify the owner updates and the Slack message appears
  3. Create a deal that matches no rules to confirm your catch-all automation (if you created one) handles it correctly

After activation, all automations run concurrently. Any new deal that matches a condition gets routed immediately.

Troubleshooting

Common questions

Can I approximate round-robin by splitting criteria evenly across reps?

Partially. If your deals come in through multiple sources in roughly equal volume, you can assign each source to a different rep — effectively distributing deals. But if 80% of your deals come from one source, that rep gets 80% of the load. This approach only works when deal volume is naturally balanced across your routing criteria. For workload-balanced distribution regardless of source, you need true round-robin logic via n8n.

What happens to deals that don't match any automation condition?

They keep whatever owner Pipedrive assigns by default — usually the user who created the deal. If deals are created via API or web forms, the default owner is typically the API token holder or the form's configured owner. Create a catch-all automation with broad conditions (or no conditions beyond "Deal created") and set it to assign to a team lead for manual redistribution.

Can I use Workflow Automation to reassign existing deals, not just new ones?

Yes. Use the "Deal updated" trigger instead of "Deal created" to reassign deals when specific fields change. For example, you could reassign a deal when its value crosses a threshold (value updated to over $50,000 triggers reassignment to a senior AE). However, be cautious — the owner change itself is a deal update, which could re-trigger other automations in a loop. Use conditions carefully to prevent cascading updates.

Cost

$0 additional — Workflow Automations and Dealbot for Slack are included on Growth ($24/seat/mo), Advanced ($44/seat/mo), Professional ($64/seat/mo), Power ($79/seat/mo), and Enterprise ($99/seat/mo) plans. No external tools, API keys, or hosting required.

Looking to scale your AI operations?

We build and optimize automation systems for mid-market businesses. Let's discuss the right approach for your team.