Triggers when a new project is created.

Triggers when an existing person is updated.

Adds an existing label to an existing person.

Add product variation to a product.

Creates a new deal.

Adds a follower to a deal, organization, person or product.

Creates a new note.

Creates a new person in Pipedrive with support for multiple email addresses, phone numbers, custom fields, and comprehensive contact information.

Creates a new project.

Add or remove labels from a deal.

Updates an existing deal.

Updates an existing organization in Pipedrive with new values for selected fields, allowing partial updates to organization properties and custom fields.

Updates an existing product.

Updates an existing task.

Finds activities by subject, owner, and other criteria. Returns multiple results.

Finds deals by any field.

Retrieves a specific activity type by ID, or returns all activity types if no ID is provided.

Retrieves a specific lead by its ID.

Retrieves a specific person by their ID.

Retrieves a specific stage by its ID.

Finds leads based on your search criteria.

Finds notes by Deal, Lead, Person, User, or Organization.

Finds persons by ID or field search.

Retrieves a specific project by its ID.

Find tasks by title, description, or other criteria.

Finds activities by subject, owner, type, dates, and other criteria, or creates one if none is found.

Finds an organization by name, or creates one if none is found.

Finds a product by field search, or creates one if none is found.

Finds a task by search criteria, or creates one if none is found.

Make a call to this endpoint when a user adds a product to their shopping cart.

Make a call to this endpoint for any event-based data representing user actions.

Get Custom Attributes for a User

Make a call to this endpoint to subscribe a user to subscriptions. Note that when a user is subscribed programmatically, it must include

Make a call to this endpoint when a user views a product.

Creates or updates a single user record, including associated attributes, subscriptions, and identifiers. If a user with the provided identifiers already exists, their information will be updated; otherwise, a new user will be created. There is a limit of 100 of custom attributes that can be created. If intending to update an existing attribute, the name of the key must match the name of the existing attribute. If an existing attribute does not exist, a new attribute will be created with the given key as the name. Attributes with enumerated values must have a value that matches an existing enum value; new enum values will not be created. Attempting to pass custom attributes as an array or a map such as ["New York City] or {"favorite city": "Boston"} will result in a 400 error.

Triggers when a person newly matches a Pipedrive filter for the first time.

Triggers when a deal's stage is updated.

Adds a discount to an existing deal.

Adds one or more products to a deal. You can add a single product or multiple products at once. (with line item support)

Creates a new activity in Pipedrive with comprehensive options for scheduling, participants, and associations.

Uploads a file and attaches it to a deal, person, organization, activity, product or note.

Creates a new lead.

Creates a new organization in Pipedrive with support for custom fields and comprehensive address information.

Creates a new product.

Creates a new task.

Updates an existing activity in Pipedrive with new values for selected fields, allowing partial updates to activity properties.

Updates an existing lead.

Updates an existing person in Pipedrive with new values for selected fields, supporting email and phone number management, field clearing with "null" values, and comprehensive custom field updates.

Updates an existing project in Pipedrive.

This is an advanced action which makes a raw HTTP request that includes this integration's authentication.

Finds deals associated with a person with enhanced data.

Finds all variations for a specific product.

Retrieves a specific deal by its ID.

Retrieves detailed organization data with optional related entities. Supports line items for processing multiple organizations.

Retrieves a specific product by its ID.

Retrieves a specific user by their ID.

Retrieves a specific note by its ID.

Finds organizations by ID or field search.

Finds products by name, ID, or product code.

Finds a project or projects by title or other fields.

Find users by name, email, or ID.

Finds a deal by field search, or creates one if none is found.

Finds a person by field search, or creates one if none is found.

Finds a project by name, or creates one if none are found.

Make a call to this endpoint for any attribute-based data.

You can use the Privacy Request API in order to comply with

Make a call to this endpoint to get recent catalog uploads with their statuses to gain visibility into the ingestion workflow in order of creation. See the POST of this endpoint for details.

Use the Identity API to manage user identifiers. With this API, you can programmatically add a client user identifier or custom identifier(s) to a user. You should only use clientUserId and customIdentifiers to send Attentive your system-assigned unique identifiers (even when testing).

Make a call to this endpoint to unsubscribe a user from a subscription type or channel. If no subscriptions are present in the request, the user is unsubscribed from all subscriptions. If subscriptions are present in the request, the user is unsubscribed from the requested type or channel combination. By default, if a subscription exists, but the user is already unsubscribed, it records the attempt to unsubscribe the subscription again. For TEXT subscriptions, a message is sent to the person indicating that they are unsubscribed.

Make a call to this endpoint when a user generates an order or purchase.

Make a call to this endpoint to list all subscription types and channels a user is subscribed to. You can query for a subscriber using either their phone number or email. One of the query parameters is required in order to look up a subscriber. As an example, you can use this endpoint to check if a subscriber is eligible to receive SMS or email campaigns, and then send them a message based on that eligibility.