How to Find Deal ID in Pipedrive (w/Examples) + FAQs

Every deal in Pipedrive is assigned a unique numeric identifier the moment it is created. This number — the Deal ID — acts as a permanent fingerprint for that specific deal record. Whether you are connecting Pipedrive to Zapier, pulling data through the API, or updating thousands of records through a spreadsheet reimport, the Deal ID is the single most reliable way to reference an individual deal without confusion.

According to Pipedrive’s own sales report, 81% of sales and marketing professionals already use CRM software with automation features built in. That means millions of deal records are flowing between apps every day — and a misidentified Deal ID can send the wrong proposal to the wrong client or overwrite critical pipeline data.

Here is what you will learn in this article:

• 🔍 How to locate a Deal ID using five different methods inside Pipedrive — from the URL bar to the API
• ⚙️ How to use Deal IDs in Zapier, Make.com, and webhook automations with step-by-step examples
• 🛡️ How GDPR and CCPA rules apply to Deal IDs and what compliance steps you must take
• 📊 How Pipedrive Deal IDs compare to HubSpot Record IDs and Salesforce Object IDs
• ❌ The most common mistakes people make with Deal IDs — and their real consequences

What Is a Pipedrive Deal ID?

A Pipedrive Deal ID is a system-generated numeric code that Pipedrive automatically assigns to every deal at the moment of creation. You cannot change it, delete it, or reassign it. It stays with that deal for its entire lifecycle, whether the deal is open, won, lost, or even deleted.

Pipedrive uses these system IDs for more than just deals. Every lead, activity, person, organization, and product also receives its own unique numeric ID. The one exception is leads — lead IDs are technically UUIDs (a long alphanumeric string like 55ebb4c0-536e-11ea-87d0-d1171b17f6a0), not simple numbers.

Deal IDs serve three core purposes. First, they provide a permanent reference point for every deal record. Second, they allow you to update data in bulk by exporting a spreadsheet, making changes, and reimporting it with the ID column intact. Third, they serve as the primary identifier when connecting Pipedrive to third-party tools like Zapier, Make.com, or custom API integrations.

Method 1: Find the Deal ID in the URL Bar

This is the fastest and most common method. Open any deal inside Pipedrive by clicking on it from your pipeline view or list view. Once the deal detail page loads, look at your browser’s address bar.

The URL follows this pattern:

The number at the very end of the URL — in this case, 222 — is the Deal ID. According to Pipedrive’s API tutorial, this is the simplest way to locate any deal’s ID without needing admin permissions or technical skills.

This method works on every Pipedrive plan, from Essential ($14/user/month) all the way up to Ultimate ($89/user/month). It also works on the mobile app — though the URL may not be as visible depending on your phone’s browser.

Real-World Scenario: Sarah’s Quick Lookup

Sarah manages 40 active deals in her sales pipeline. A client calls asking about their proposal status. Sarah searches the client name in Pipedrive, clicks on the deal, and sees the URL reads https://sarahco.pipedrive.com/deal/1847. She notes 1847 as the Deal ID and uses it to log the call in her team’s project management system.

Method 2: Find Deal IDs in the List View

If you need to see Deal IDs for multiple deals at once, the list view is a much faster approach than clicking into each deal one at a time. According to Pipedrive’s support documentation, you can add the ID column directly to any list view.

Here is how:

1. Navigate to your Deals section in the left sidebar
2. Switch to the list view (the table icon at the top of the page)
3. Click the gear icon to open column settings
4. Select ID from the available fields
5. Click Save

The Deal ID now appears as a visible column in your list view. You can sort by it, filter by it, and scan hundreds of deals at once. This column also carries over if you export the filter results as a CSV or Excel file.

Real-World Scenario: Marcus Needs IDs for a Report

Marcus is preparing a quarterly sales report. His manager wants a spreadsheet that includes each deal’s unique ID alongside its value, stage, and owner. Marcus opens the deal list view, adds the ID column, applies a filter for “All deals created this quarter,” and clicks Export filter results as CSV. The exported file contains every Deal ID he needs.

Method 3: Export Deal IDs in Bulk

Sometimes you need Deal IDs for every deal in your entire Pipedrive account — not just filtered results. Pipedrive offers two export paths for this, and both include the Deal ID field automatically.

Global Data Export (Admin Only)

Only users with global admin permissions can access this option. Navigate to the account menu (top right corner) → Tools and apps → Export data. Select “Deals” as the data type and choose either CSV or Excel format. Pipedrive generates the file in the background, and once it is ready, a green Download button appears.

The exported file remains available for 28 days before it expires. After that, you must generate a new export.

List View Export (Filtered)

Any user with export permissions can use this method. From the deal list view, apply a filter (e.g., “All open deals”), click the three dots menu, and select Export filter results. You choose between XLS and CSV formats. The advantage here is that you get a targeted dataset instead of everything in the system.

Detail View Export

You can also export a single deal’s full details. Open the deal detail view, click the “…” menu in the top right corner, and select Export as XLSX. This spreadsheet includes the deal’s details and any linked person or organization data.

Method 4: Retrieve Deal IDs Through the API

For developers, automation engineers, or anyone building custom integrations, the Pipedrive REST API is the most powerful way to access Deal IDs programmatically. Every API response for deal-related endpoints includes the id field.

Getting All Deal IDs

The endpoint GET /api/v2/deals returns a list of all non-archived deals. Each deal object in the response includes its id, title, value, status, pipeline_id, stage_id, and dozens of other fields. You can filter results by owner_id, person_id, org_id, pipeline_id, stage_id, and status.

According to the Pipedrive API reference, you can fetch up to 500 deals per request using the limit parameter. For accounts with thousands of deals, use the cursor parameter for pagination.

Getting a Single Deal by ID

If you already know the Deal ID, use GET /api/v2/deals/{id} to pull that deal’s full details. For example, GET /api/v2/deals/222 returns everything about deal #222. This is the approach described in Pipedrive’s deal details tutorial.

Searching for a Deal

The search endpoint GET /api/v2/deals/search lets you find deals by title, notes, or custom fields. The search requires a minimum of 2 characters (or 1 character with exact_match enabled). Each result includes the deal’s id, which you can then use in subsequent API calls.

PHP Example

Here is a simplified version of what the API tutorial demonstrates:

php$api_token = 'YOUR_API_TOKEN';
$company_domain = 'YOUR_COMPANY_DOMAIN';
$url = 'https://' . $company_domain . '.pipedrive.com/api/v2/deals?limit=500&api_token=' . $api_token;

This request returns up to 500 deals, each containing its id field. You can iterate through the response to extract every Deal ID in your account.

API Authentication

You need a Pipedrive API token to make any request. Each user has their own token, found in Personal preferences → API. Treat this token like a password — anyone who has it can read and modify your Pipedrive data.

Method 5: Deal IDs in Webhooks and Automations

Pipedrive’s built-in automation engine can send webhook requests whenever a deal changes. These webhooks include the Deal ID as a data point, making it possible to trigger actions in external systems automatically.

According to a guide from BLC-Conseil, a typical webhook automation in Pipedrive works like this:

1. Go to Automations and create a new one
2. Choose a trigger event (e.g., “Deal stage changed”)
3. Add a Webhook action
4. In the key-value pair settings, enter: id → Deal ID
5. Set the method to POST and paste the destination URL

When the trigger fires, Pipedrive sends a POST request to your endpoint containing the Deal ID and any other key-value pairs you configured. This is how tools like HelloSend automatically send SMS or WhatsApp messages tied to specific deals.

Using Deal IDs with Third-Party Integrations

Zapier

Zapier is one of the most popular no-code automation platforms, and its Pipedrive integration supports over 8,000 connected apps. Deal IDs are central to how Zapier interacts with Pipedrive.

The Find Deal action in Zapier searches for a deal by a specific field — including the Deal ID. If found, the action returns the deal’s data for use in subsequent steps. The “Create Pipedrive Deal if it does not exist already” option first searches for a match. According to a Zapier community thread, this option still requires a search value — if you leave the Deal ID blank, you will get an error reading “Required field ‘ID’ (term) is missing.”

Workarounds for handling missing Deal IDs in Zapier include:

• Use Paths to create separate branches for “Deal ID exists” and “Deal ID does not exist”
• Use a Formatter/Text step to set a default Deal ID value that you know does not exist, forcing Zapier to create a new deal
• Create two separate Zaps — one for updating existing deals and one for creating new ones

Make.com (Formerly Integromat)

Make.com uses modules to interact with Pipedrive. The Watch Deals module triggers when a new or updated deal appears. The Get a Deal module requires a Deal ID as input. As shown in a Make community discussion, when the “Get a Deal” module prompts you for a Deal ID, you can find it by logging into Pipedrive and checking the number at the end of the URL after https://your-host.pipedrive.com/deal/.

A Make.com automation tutorial demonstrates how Deal IDs flow between modules. When a deal moves to a “Needs Defined” stage, Make captures the Deal ID, creates a task in ClickUp with that ID stored as a custom field, and then uses that custom field to sync updates back to Pipedrive. Without the Deal ID as the common thread, this two-way sync would be impossible.

Real-World Scenario: Automated Proposal Workflow

A digital agency uses Make.com to automate their proposal process. When a deal reaches the “Proposal” stage in Pipedrive, Make.com captures the Deal ID and creates a task in ClickUp. The ClickUp task stores the Deal ID in a custom field. When the team marks the ClickUp task as “Ready,” Make.com reads the Deal ID from the custom field and updates the Pipedrive deal’s stage to “Proposal Sent.” The Deal ID is the glue that keeps both systems in sync.

GDPR and CCPA Compliance for Deal IDs

A Deal ID is a number, but the data attached to that number can include personal information — names, email addresses, phone numbers, company details, and notes about private conversations. That makes Deal IDs subject to data privacy regulations.

GDPR Requirements

The General Data Protection Regulation applies to any business handling personal data of EU residents. According to Simple Analytics’ review of Pipedrive’s GDPR compliance, Pipedrive acts as a GDPR-ready data processor. The platform provides a self-service Data Processing Addendum (DPA) incorporating EU/UK Standard Contractual Clauses (SCCs), EU-hosted data centers, and certifications including ISO 27001, ISO 27701, and SOC 2/3.

However, compliance is a shared responsibility. Pipedrive gives you the tools, but you must configure consent fields in forms, enable tracking safeguards, manage data deletion timelines, and align internal processes with GDPR principles. A Deal ID that links to a person’s contact details is considered personal data under GDPR because it can be used to identify an individual indirectly.

CCPA Requirements

For businesses handling personal information of California residents, the California Consumer Privacy Act applies. Pipedrive’s Data Processing Addendum confirms that all personal information subject to the CCPA is disclosed to Pipedrive for one or more Business Purposes only. Pipedrive will not sell this data or use it outside the scope of those Business Purposes.

What This Means for Deal IDs

Pipedrive provides privacy and security features including data encryption, API-based data export and deletion, and a dedicated data protection officer. The platform complies with the EU-US Data Privacy Framework and adheres to SOC 2, SOC 3, and ISO/IEC 27001:2013 standards.

How Pipedrive Deal IDs Compare to Other CRMs

If you are migrating between CRMs or integrating multiple systems, understanding how each platform handles deal identification is critical. The three platforms take fundamentally different approaches.

Pipedrive

Pipedrive uses simple, auto-incrementing numeric IDs. The first deal created in your account might be 1, the next 2, and so on. These IDs are permanent and visible in the URL, the list view, API responses, and all exports. There is no prefix or suffix — just a plain integer. According to Pipedrive’s system ID documentation, this applies uniformly to deals, persons, organizations, activities, and products.

HubSpot

HubSpot uses a Record ID as the default unique identifier for every object. According to a HubSpot community discussion, “Deal ID” is not a default HubSpot field — it is sometimes created by users or integrations and is not guaranteed to exist. The Record ID is the correct and reliable identifier. It is automatically generated, numeric, and present on every deal record.

Salesforce

Salesforce uses 15-character or 18-character alphanumeric IDs. Each ID includes a prefix that identifies the object type — for example, 006 for Opportunities (Salesforce’s equivalent of deals). According to a RevBlack integration guide, HubSpot’s native Salesforce connector automatically pulls the 18-character case-insensitive version. Salesforce IDs contain encoded information about the record type, which makes them longer but self-describing.

Pipedrive Plans and Deal ID Access

The ability to find and use Deal IDs is available on every Pipedrive plan. There is no paywall blocking access to this fundamental feature. However, the methods available to you can vary depending on your role and plan.

According to Capterra’s pricing breakdown and Pipedrive’s own pricing page, the current plan tiers are:

• Essential ($14/user/month billed annually): URL method, list view, detail view export, basic API access
• Advanced ($39/user/month): All Essential features plus workflow automation with up to 30 active automations
• Professional ($49/user/month): Enhanced automation (up to 60 active automations), revenue forecasting, AI-powered features
• Power ($64/user/month): Larger team collaboration tools, phone support, project planning
• Ultimate ($89/user/month): Unlimited automations, security alerts and rules, sandbox testing account

The URL method and list view method work on every plan. The global data export requires global admin permissions regardless of plan. API access is available on all plans, but rate limits may differ. Webhook automations require the Advanced plan or higher because automations are not included in the Essential plan.

Mistakes to Avoid

Getting a Deal ID wrong can cascade into serious problems — broken automations, corrupted data, or compliance violations. Here are the most common mistakes and their consequences.

Mistake 1: Confusing Deal ID with Lead ID

Pipedrive treats leads and deals as separate entities. A lead has a UUID (a long alphanumeric string), while a deal has a short numeric ID. If you convert a lead to a deal, the lead ID does not become the Deal ID. According to Pipedrive’s system ID article, the deal gets a brand new numeric ID upon creation. Referencing the old lead UUID in a deal-focused automation will return a “not found” error.

Mistake 2: Assuming Deal IDs Are Sequential with No Gaps

Deal IDs auto-increment, but they are not guaranteed to be sequential. If a deal is created and then immediately deleted, that ID is consumed. The next deal gets the following number. If you build logic that assumes “the last Deal ID plus one equals the next deal,” your code will break.

Mistake 3: Hardcoding Deal IDs in Automations

Some users enter a specific Deal ID directly into a Zapier step or Make.com module instead of dynamically mapping it from a previous step. This means the automation only ever affects that one deal. When the automation triggers for a different deal, it still references the hardcoded ID and either fails or updates the wrong record.

Mistake 4: Ignoring Permissions When Exporting

The global data export function is restricted to global admins. According to Pipedrive’s export documentation, regular users can only export data visible to them based on their visibility group. If a non-admin user tries to access the Export Data section, the option is not available — leading to frustration and wasted time.

Mistake 5: Sharing API Tokens That Expose Deal IDs

Your API token grants full read and write access to your Pipedrive data, including all Deal IDs and their associated records. Sharing this token in a public GitHub repository, a shared Zapier account, or an insecure webhook endpoint exposes every deal in your account. Under GDPR, this could constitute a reportable data breach if personal data is involved.

Do’s and Don’ts

Do’s

• Do use the list view ID column for quick visual reference across multiple deals. It is the fastest way to scan IDs without clicking into individual records.
• Do map Deal IDs dynamically in Zapier and Make.com. Pull the ID from the trigger step so the automation works for every deal, not just one.
• Do include the ID column in every export you plan to reimport later. This is how Pipedrive matches rows in your spreadsheet to existing records.
• Do store your API token securely. Use environment variables or a secrets manager — never paste it into client-side code or public repositories.
• Do document which integrations use Deal IDs. If an integration breaks, knowing which systems reference Deal IDs helps you troubleshoot faster.

Don’ts

• Don’t manually assign or edit Deal IDs. Pipedrive generates them automatically and they cannot be changed. Attempting to import a spreadsheet with fabricated IDs will create new records instead of updating existing ones.
• Don’t confuse the Deal ID with the Pipeline ID or Stage ID. A deal’s URL shows the Deal ID, but API responses include pipeline_id and stage_id as separate fields. Using the wrong ID type in an API call returns unexpected results.
• Don’t assume Deal IDs are the same across Pipedrive accounts. If you manage multiple Pipedrive accounts (e.g., for different business units), Deal ID 100 in Account A is a completely different deal than Deal ID 100 in Account B.
• Don’t skip GDPR considerations when sharing Deal IDs externally. A Deal ID linked to personal data is an indirect identifier under GDPR. Sharing it with a third party without a proper data processing agreement can violate the regulation.
• Don’t forget to check webhook logs. When an automation fires and sends a Deal ID via webhook, verify in the webhook history that the correct ID was sent. A misconfigured key-value pair can send a blank or incorrect ID.

Pros and Cons of Pipedrive’s Deal ID System

Pros

• Simplicity. A plain numeric ID like 222 is easy to read, communicate verbally, and use in spreadsheets. There is no need to decode object-type prefixes like in Salesforce.
• Universal visibility. The Deal ID appears in the URL, list view, API responses, exports, and webhooks. You are never locked out of accessing it regardless of your plan tier.
• Permanent and immutable. Once assigned, the ID never changes. This makes it a reliable anchor for long-running integrations and historical reporting.
• Integration-friendly. Because it is a simple integer, nearly every third-party tool can handle it without data type conversion. No special formatting is required.
• Bulk update capability. The import/export workflow using Deal IDs lets you update thousands of records at once by editing a spreadsheet and reimporting it.

Cons

• No object-type encoding. Unlike Salesforce’s prefixed IDs, a Pipedrive Deal ID does not tell you what kind of record it is. The number 222 could be a deal, a person, or an organization — you need context to know which.
• No human-readable information. The ID tells you nothing about the deal itself. You cannot glance at 1847 and know it belongs to “Acme Corp — Enterprise License.”
• Cross-account confusion. The same numeric ID can exist in different Pipedrive accounts for completely different deals. If your company operates multiple accounts, you must track which account an ID belongs to.
• No built-in checksum. There is no validation digit or error-detection mechanism. Transposing two digits (e.g., typing 1874 instead of 1847) silently references a different deal with no warning.
• Gap potential in numbering. Deleted deals consume their ID permanently. Over time, the numbering develops gaps that can confuse users who expect unbroken sequences.

Key Entities and Their Roles

Understanding how Deal IDs interact with other Pipedrive entities helps you build more effective workflows.

Pipedrive (the Platform): The CRM that generates and stores Deal IDs. It provides the web interface, API, and automation engine. Pipedrive is ISO 27001 and SOC 2 certified, meaning the infrastructure storing your Deal IDs meets enterprise-grade security standards.

Zapier: A no-code automation platform that connects Pipedrive to 8,000+ apps. Zapier uses Deal IDs in its “Find Deal” and “Update Deal” actions. It is SOC 2 and GDPR compliant.

Make.com: A visual automation platform (formerly Integromat) that uses modules to interact with Pipedrive. Modules like “Watch Deals” and “Update a Deal” require or output Deal IDs as their primary reference point.

The Pipedrive API: The RESTful interface at api.pipedrive.com that developers use to programmatically create, read, update, and delete deals. Every endpoint that touches deals uses the Deal ID as the path parameter (e.g., /api/v2/deals/{id}).

Global Admins: The only users in a Pipedrive account who can access the global data export function. Regular users are limited to list view exports and detail view exports based on their visibility permissions.

Step-by-Step: Updating Deals in Bulk Using IDs

One of the most practical uses of Deal IDs is bulk updating. Instead of editing deals one at a time inside Pipedrive, you can make changes in a spreadsheet and reimport them.

1. Add the ID column to your list view. Click the gear icon and select ID.
2. Apply a filter to narrow down the deals you want to update (e.g., “All open deals in Pipeline X”).
3. Export the filtered results as CSV or Excel. The file includes the ID column.
4. Open the spreadsheet in Excel or Google Sheets. Make your changes — update deal values, change stages, modify custom fields.
5. Keep the ID column intact. Do not modify, delete, or rearrange the Deal IDs.
6. Reimport the spreadsheet into Pipedrive using the import tool. During the mapping step, map the ID column to the Pipedrive “ID” field.
7. Pipedrive matches each row by Deal ID and updates the corresponding records.

If you remove the ID column or change the IDs, Pipedrive treats each row as a new deal instead of an update. This creates duplicates instead of modifying existing records.

FAQs

Can I change a Deal ID in Pipedrive?

No. Deal IDs are system-generated and permanent. You cannot edit, reassign, or reset them. They are assigned at the moment of deal creation and remain fixed for the deal’s entire lifecycle.

Does every Pipedrive plan include Deal IDs?

Yes. Deal IDs are a core system feature available on every plan, from Essential through Ultimate. No upgrade is needed to view or use them.

Is the Deal ID the same as the Pipeline ID?

No. The Deal ID identifies a specific deal record. The Pipeline ID identifies which pipeline the deal belongs to. They are separate fields in API responses and exports.

Can two deals have the same Deal ID?

No. Within a single Pipedrive account, every Deal ID is unique. However, the same number can exist in a different Pipedrive account for a completely different deal.

Do deleted deals keep their IDs?

Yes. When a deal is deleted, its ID is consumed permanently. It is never reused for a new deal. Deleted deals remain recoverable for 30 days before permanent deletion.

Can I find a Deal ID on the Pipedrive mobile app?

Yes. Open a deal on the mobile app and check the URL or the deal details screen. The ID may appear differently depending on your device, but it is accessible.

Are Deal IDs considered personal data under GDPR?

Yes, if the Deal ID can be linked to an identifiable person — which it almost always can, since deals are typically associated with contacts and organizations.

Can Zapier create a deal and return the new Deal ID?

Yes. When Zapier’s “Create Deal” action runs, Pipedrive generates a new Deal ID and returns it in the response. You can use this ID in subsequent Zap steps.

Does the Deal ID appear in email tracking?

No. The Deal ID is an internal system identifier. It does not appear in emails sent to clients or tracked through Pipedrive’s email integration.

Can I search for a deal by its ID in Pipedrive?

Yes. Use the global search bar at the top of Pipedrive and type the Deal ID number. Pipedrive returns matching results. You can also use the API search endpoint with the exact_match parameter.