Pipedrive CRM

with pipedrive crm modules in , you can manage deals, products in deals, persons in deals, participants in deals, files in deals, activities in deals, leads, organizations, products, persons, notes, activities, mails, followers, users, files, subscriptions, filters, pipelines, stages, and items in your pipedrive crm account pipedrive api v1 modules are now deprecated existing scenarios using these modules will continue to run until july 31, 2026 for more information, see pipedrive api v1 to v2 transition by july 31, 2026 docid\ si dgznjom7wjyrss 8sq to get started with pipedrive crm, create an account at pipedrive com/register https //www pipedrive com/en/register refer to the pipedrive crm api documentation https //developers pipedrive com/docs/api/v1 for a list of available endpoints establish a connection with pipedrive oauth to establish the connection log in to your make account, add a pipedrive crm module to your , and click create a connection optional in the connection name field, enter a name for the connection optional switch on advanced settings to enter your custom app client credentials for more information regarding creating a custom app and retrieving client credentials, refer to the pipedrive creating an app documentation https //pipedrive readme io/docs/marketplace creating a proper app if requested, use the following redirect uri when creating your custom app https //www integromat com/oauth/cb/pipedrive auth click save if prompted, authenticate your account and confirm access you have successfully established the connection you can now edit your and add more pipedrive crm modules if your connection requires reauthorization at any point, follow the connection renewal steps here docid\ so88fm6pkt0g adkddfzz the date and time values are converted to the utc time zone for input and returned in output as a value in the user's time zone migrate from pipedrive api v1 to v2 pipedrive api v2 introduces changes to how records are structured, validated, and returned if your scenarios use pipedrive modules built on v1, some mappings and field references will need to be updated this guide covers what changed and what to do in each case for more information about the underlying api changes, see the pipedrive api v2 migration guide https //pipedrive readme io/docs/pipedrive api v2 migration guide response structure changes related records return ids, not objects in v1, modules like get a deal returned embedded data for related records — for example, the deal owner's name and email appeared directly in the response in v2, those fields return only a numeric id ( owner id , person id , org id , creator user id ) if your scenario mapped the owner's name or a person's email directly from a deal response, that data is no longer included by default to retrieve it, either add a second module to look up the related record by id, or enable the extend output option in the get a deal , get a person , or get an activity module enabling extend output will require additional api calls this consumes more operations and counts against your pipedrive daily api limit option fields return ids, not labels in v1, single and multiple option custom fields returned both the option id and its readable label in v2, they return only the id the get a deal module includes a show labels option to retrieve the human readable label alongside the id like extend output , enabling show labels triggers an extra request and a small additional credit cost custom fields are grouped under a single object in v1 , custom fields and their sub fields were spread across the top level of the record, sometimes with separate keys for example, a currency field had a standalone currency key in v2 , all custom fields sit under a single custom fields object, with related properties nested together { "value" 500, "currency" "usd" } update any mappings that referenced the old flat keys directly calculated and convenience fields have been removed v2 dropped fields that v1 computed automatically the following are no longer returned owner name , person name , org name , deal title weighted value , formatted value , quantity formatted , sum formatted fetch the related record to retrieve its name compute formatted or weighted values in your scenario if needed counts and secondary metrics require explicit opt in activity counts, follower counts, and similar metrics are no longer returned by default you must opt in using the include fields parameter pass this parameter as a comma separated string — passing it as an array means the extra fields don't return addresses are now nested objects address and location data moved from multiple flat fields (for example, address route , address locality ) into a single nested object with sub properties update any mappings that pointed at the old flat address keys field name changes several fields were renamed in v2 update your mappings where you reference the following v1 field name v2 field name user id owner id created by user id creator user id deleted / active flag is deleted (logic is inverted) phone / email phones / emails (now arrays) label label ids (now an array of integers) labels the label field changed from a comma separated string (for example, "3,7" ) to an array of integers ( \[3, 7] ) when mapping labels, provide integer ids in array form supplying a comma separated string or non integer values returns a this value should be of type integer or label not found error custom field names in module output where field labels were used as parameter names, use the underlying field code instead renaming a custom field in pipedrive won't break your mapping when the field code is used validation changes v2 validates request data more strictly than v1 numbers must be real numbers option ids and numeric custom fields must be sent as numbers, not strings if a mapped value arrives as a string, v2 rejects it with an error such as "expected 'number' as option id for multi options custom field " use parsenumber() where a mapped value comes through as text booleans are true / false , not 1 / 0 empty values are rejected you can't leave a custom field blank v2 refuses an empty string with an error like "expected non empty 'string' as short text custom field value " for number fields, null , ifempty( ; ignore) , and erase are all rejected — and sending 0 is accepted but treated as the value zero, not as empty to avoid errors, don't send empty string values for custom fields apply a formula to conditionally include the field only when it has a value for example date and time fields all timestamps in v2 use rfc 3339 format with an explicit timezone (for example, 2024 01 01t00 00 00z ) for activities, the single due date and time concept split into two separate string fields due date and due time treat these as distinct values in your mappings pagination v1 used offset based pagination ( start and limit ) v2 uses cursor based pagination ( cursor and limit ) this is handled inside the modules if you built custom pagination logic around page offsets using make an api call , update that logic to use cursor based pagination update endpoints now use patch v1 update endpoints used http put v2 uses patch if you send update requests through make an api call , verify the method is set to patch search parameter changes the item search endpoint renamed several parameters in v2 v1 parameter v2 parameter field key field field type entity type exact match match (accepts exact , beginning , or middle ) update these parameter names in any custom api calls that drive search endpoints that remain on v1 not every pipedrive resource has a v2 equivalent the following remain on v1 leads and projects — modules for these still call v1 archived leads — not available through the standard v2 list path retrieving archived leads requires a separate dedicated endpoint subscriptions — deprecated in v2 use the installments modules (list, add, update, delete) instead connection issues with v2 modules if a v2 module fails where the v1 module worked on the same connection, the cause is likely one of the following v2 requires an accept application/json header without it, the api can return an html page that surfaces as a 404 undefined error some v2 endpoints require oauth scopes that weren't present on connections created before v2 shipped if you encounter unexplained 404 errors on a v2 module, reconnect the pipedrive account and try again build pipedrive crm after connecting the app, you can perform the following actions triggers watch new events watch deals watch leads watch organizations watch persons watch products watch notes watch activities watch emails deals search deals list deals list deals for a product list deal fields get a deal get a deal field get deals summary create a deal field create a deal update a deal update a deal field delete a deal field delete a deal leads search leads list leads get a lead create a lead update a lead delete a lead lead labels list lead labels create a lead label update a lead label delete a lead label products in a deal add a product to a deal update product attachment details delete an attached product list products in a deal participants in a deal list participants of a deal add a participant to a deal files in a deal list files in a deal organizations search organizations list organizations get an organization create an organization update an organization update an organization field value delete an organization persons persons are the customers you are doing deals with — not users search persons list persons get a person create a person update a person delete a person products search products list products get a product create a product update a product delete a product notes list notes get a note create a note update a note delete a note activities list activities get an activity create an activity update an activity delete an activity mail list mail threads list messages in a thread get a mail thread get a message update a mail thread details delete a mail thread followers list followers add a follower delete a follower users get a user search users files upload a file download a file filter list filters get a filter other make an api call search for items list pipelines list stages