Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
SuperSaaS
Pipedrive CRM

Connect SuperSaaS and Pipedrive CRM

Explore ready-made SuperSaaS and Pipedrive CRM templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate SuperSaaS with Pipedrive CRM and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

SuperSaaS
Trigger: Changed appointment
Pipedrive CRM
Action: Select an action
1. Select a trigger

  • Triggers each time an appointment changes on your schedule. A new appointment also counts as a change.

  • Triggers for each change to a user in your SuperSaaS account. A new user also counts as a change.

  • Triggers when a user buys something in your shop

  • Triggers each time an email is generated. Can be used to send notifications from your own email account. Note that the SuperSaaS mail server will stop sending mail when this webhook exists.

  • Triggers for each new appointment on your schedule.

  • Triggers each time a user submits a new stand-alone form. Does not trigger for forms that are filled out as part of an appointment or user sign up.

  • Triggers each time a new user registers on your SuperSaaS account.

  • Triggers on a reminder or a follow up. Note that SuperSaaS will stop sending the reminder or follow up while this web hook exists.

2. Select an action

  • Add follower to an object of selected type (deals, organizations, persons).

  • Add follower to an object of selected type (deals, organizations, persons).

  • Adds a participant to a deal.

  • Adds a product to the deal.

  • Adds a new recurring subscription to a deal.

  • Adds a new installment subscription.

  • Adds an installment to a deal.

  • Cancels a recurring subscription.

  • Creates a deal.

  • Creates a deal.

  • Creates a new deal field.

  • Creates a lead.

  • Creates a new lead label.

  • Creates a note.

  • Creates a person.

  • Creates a person.

  • Creates a product.

  • Creates a product.

  • Creates a new project.

  • Creates a new task.

  • Creates an activity.

  • Creates an activity.

  • Creates an organization.

  • Creates an organization.

  • Deletes a deal.

  • Deletes a deal field by its ID.

  • Delete a follower from a deal.

  • Delete a follower from a deal.

  • Deletes a lead.

  • Deletes lead label by its ID.

  • Marks mail thread as deleted.

  • Deletes a note.

  • Deletes a person.

  • Deletes a product.

  • Deletes or archives a project by its ID.

  • Marks an installment or a recurring subscription as deleted.

  • Deletes task by its ID.

  • Deletes an activity.

  • Deletes a product attachment from a deal.

  • Deletes an installment.

  • Deletes an organization.

  • Downloads a file.

  • Returns details of a specific deal.

  • Returns details of a specific deal.

  • Gets a Deal field.

  • Gets filter by its ID.

  • Gets a lead.

  • Returns specific mail thread.

  • Returns data about specific mail message.

  • Returns details about a specific note.

  • Returns details of a person.

  • Returns details of a person.

  • Returns data about a specific product.

  • Returns data about a specific product.

  • Gets a project by its ID.

  • Returns details of an installment or a recurring subscription.

  • Gets task by its ID.

  • Returns data about a specific user within the company.

  • Returns details of a specific activity.

  • Returns details of a specific activity.

  • Returns details of an organization.

  • Returns details of an organization.

  • Gets deals summary.

  • Performs an arbitrary authorized API call.

  • Performs an arbitrary authorized API call.

  • Updates a deal.

  • Updates a deal.

  • Updates Deal field by its ID.

  • Updates a lead.

  • Updates lead label by its ID.

  • Updates the properties of a mail thread.

  • Updates a note.

  • Updates a person.

  • Updates a person.

  • Updates a product.

  • Updates a product.

  • Updates project by its ID.

  • Updates a recurring subscription.

  • Updates task by its ID.

  • Updates an activity.

  • Updates an activity.

  • Updates an installment added to a deal.

  • Updates an installment subscription.

  • Updates an organization.

  • Updates an organization.

  • Updates an organization field value.

  • Updates product attachment details of the deal-product (a product already attached to a deal).

  • Lets you upload a file, and associate it with a Deal, a Person, an Organization, an Activity or a Product.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between SuperSaaS and Pipedrive CRM.

Add a Follower
Add follower to an object of selected type (deals, organizations, persons).
Action
Add a Follower (Deprecated)
Add follower to an object of selected type (deals, organizations, persons).
Action
Add a Participant to a Deal
Adds a participant to a deal.
Action
Add a Product to a Deal
Adds a product to the deal.
Action
Add a Recurring Subscription (Deprecated)
Adds a new recurring subscription to a deal.
Action
Add an Installment Subscription (Deprecated)
Adds a new installment subscription.
Action
Add an Installment to a Deal
Adds an installment to a deal.
Action
Cancel a Recurring Subscription (Deprecated)
Cancels a recurring subscription.
Action
Changed appointment
Triggers each time an appointment changes on your schedule. A new appointment also counts as a change.
Trigger
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.