Skip to main content

Update

Updates an existing object in Pipedrive CRM (Activity, Deal, Note, Organization, Person, or Lead).

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

  • Connection Id - The connection ID returned by the Connect node.
  • Object Id - The ID of the object to be updated.
  • Data - An object containing the updated data for the object.

Options​

  • Type - The type of object to update (Activity, Deal, Note, Organization, Person, or Lead).

Output​

  • Result - The response from the Pipedrive API containing details of the updated object.

How It Works​

The Update node modifies an existing object in Pipedrive CRM. When executed, the node:

  1. Validates the provided Connection Id
  2. Validates the Object Id input
  3. Validates the Data input
  4. Uses the selected Type option to determine what kind of object to update
  5. Calls the appropriate Pipedrive API endpoint to update the object
  6. Returns the API response as the result

Requirements​

  • A valid connection to Pipedrive established using the Connect node
  • The ID of the object to be updated
  • Properly formatted data object with the fields to be updated
  • Appropriate permissions in Pipedrive to update the selected object type

Error Handling​

The node will return specific errors in the following cases:

  • Empty or invalid Connection Id
  • Empty or invalid Object Id
  • Empty or invalid Data object
  • Invalid Type selection
  • Pipedrive API errors (e.g., insufficient permissions, object not found, invalid data format)

Usage Notes​

  • The Object Id should be obtained from a previous operation (e.g., Create or Get)
  • The Data input should be an object with properties matching the fields of the object type being updated
  • Only the fields specified in the Data input will be updated; other fields remain unchanged
  • The Connection Id must be obtained from a previous Connect node
  • The result contains the full response from the Pipedrive API with the updated object details