If no stage is specified, the trigger will fire on any deal who's stage was updated.

Requires Admin access to Pipedrive account

Select user who will be marked as the owner of this deal. If omitted, the authorized user will be used.

Organization this deal will be associated with.

Person this deal will be associated with.

The user you want to assign as a follower.

Supports some HTML formatting.

Note must be associated with at least one deal, person, organization, or lead.

Note must be associated with at least one deal, person, organization, or lead.

Note must be associated with at least one deal, person, organization, or lead.

Note must be associated with at least one deal, person, organization, or lead.

Format must be HH:MM

Accepts HTML format

Select user who will be marked as the owner of this lead.

Organization this lead will be associated with.

Person this lead will be associated with.

This field is required if a Lead Value amount is provided.

Will overwrite current email addresses.

Will overwrite current phone numbers.

API docs for Pipedrive are located here https://developers.pipedrive.com/docs/api/v1

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

If no, a fuzzy match result can be returned. For example, if searching for a deal titled Zapier when this field is set to yes, the search will NOT return a deal named Zapier Deal, but it would return a deal named Zapier or zapier.

If no, a fuzzy match result can be returned. For example, if searching for Zapier when this field is set to yes, the search will NOT return an org named Zapier Inc, but would return an org named Zapier or zapier.

If no, a fuzzy match result can be returned. For example, if searching for a deal titled Zapier when this field is set to yes, the search will NOT return a deal named Zapier Deal, but it would return a deal named Zapier or zapier.

Requires Admin access to Pipedrive account

Select user who will be marked as the owner of this deal. If omitted, the authorized user will be used.

Organization this deal will be associated with.

Person this deal will be associated with.

If no, a fuzzy match result can be returned. For example, if searching for Zapier when this field is set to yes, the search will NOT return an org named Zapier Inc, but would return an org named Zapier or zapier.

Defaults to account's currency settings if not specified.

A currency must be specified in order to set a price.

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request data below will be overridden with the raw data from the previous step (you are still responsible for headers though, like Content-Type). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data Content-Type. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Lead must be associated with at least one person or organization.

Lead must be associated with at least one person or organization.

Select user who will be marked as the owner of this lead. If omitted, the authorized user will be used.

Supports some HTML formatting. Defaults as an unpinned note unless specified below.

If true, the note in the field above will be pinned to the top of this lead.

This field is required if a Lead Value amount is provided.

Defaults to account's currency settings if not specified.

A currency must be specified in order to set a price.

Select user who will be marked as the owner of this deal.

Organization this deal will be associated with.

Person this deal will be associated with.

Determines which App Extensions will appear in the dropdown below.

Partial sentences are ok, we'll try to find the best match.

If you have a lot of activities (thousands), try using a Pipedrive filter to narrow down the results.

Note that "Not Done" is set as the default when no option is picked.

If no, a fuzzy match result can be returned. For example, if searching for a deal titled Zapier when this field is set to yes, the search will NOT return a deal named Zapier Deal, but it would return a deal named Zapier or zapier.

If no, a fuzzy match result can be returned. For example, if searching for the name Zap Zaplar when this field is set to yes, the search will NOT return a person named Zap Zaplar Jr., but would return a person named Zap Zaplar or zap zaplar.

Partial sentences are ok, we'll try to find the best match.

If omitted, the activity will be assigned to the user of the connected account.

If you have a lot of activities (thousands), try using a Pipedrive filter to narrow down the results.

Note that "Not Done" is set as the default when no option is picked.

Format must be HH:MM

Accepts HTML format

If no, a fuzzy match result can be returned. For example, if searching for a deal titled Zapier when this field is set to yes, the search will NOT return a deal named Zapier Deal, but it would return a deal named Zapier or zapier.

Lead must be associated with at least one person or organization.

Lead must be associated with at least one person or organization.

Select user who will be marked as the owner of this lead. If omitted, the authorized user will be used.

Supports some HTML formatting. Defaults as an unpinned note unless specified below.

If true, the note in the field above will be pinned to the top of this lead.

This field is required if a Lead Value amount is provided.

If no, a fuzzy match result can be returned. For example, if searching for the name Zap Zaplar when this field is set to yes, the search will NOT return a person named Zap Zaplar Jr., but would return a person named Zap Zaplar or zap zaplar.

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: [{"id":1234},{"id":1235}]

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the id key. If the id key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with id in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given {"contact": {"name": "Mike"}}, add "contact" here to only return {"name": "Mike"}. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

We recommend not putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. Note: If you specify nothing for this field, we will automatically encode and include every field from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Only used if As JSON.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.