[Go to site: main page, start]
Skip to main content
Pipedrive is a sales CRM for managing deals, contacts, activities, leads, and pipelines. The Pipedrive connector lets your Lovable app read and manage CRM data through the Pipedrive API. It’s designed for sales dashboards, customer portals, workflow automation, and internal tools that need access to Pipedrive records. Pipedrive is available as an app + chat connector: one shared connection that works in the chat while you build and in your published apps. With Pipedrive, your app can:
  • Create, update, and list deals across sales pipelines
  • Manage people, organizations, leads, and activities
  • Read pipeline, stage, field, and user metadata for CRM workflows
  • Build dashboards and automations around Pipedrive CRM data
  • Register webhooks when your app needs to react to Pipedrive changes
Pipedrive is a good fit when your team manages sales activity in Pipedrive and wants a custom Lovable app for reporting, operations, customer handoffs, or sales workflows.

​
Common use cases and example apps

​
How to connect Pipedrive

Who can create Pipedrive connections depends on your plan and workspace settings. App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: Who can create connections and clients defaults to No one until an admin changes it in Connectors → Admin settings → App + chat connectors. When adding a connection, you can choose between:
  • Connect with Pipedrive: sign in with your Pipedrive account in one click (OAuth)
  • Use your own credentials: bring your own Pipedrive API token
You can create multiple Pipedrive connections using different accounts or API tokens, which is useful for separating environments (for example, development and production), connecting different Pipedrive accounts, or managing access for different teams. When the connection is created, you can link it to the projects where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it.

​
Prerequisites

Before connecting Pipedrive, make sure you have:
All API requests made through this connector count toward your Pipedrive plan limits. Billing and quota are handled directly by Pipedrive, not Lovable.
Follow the setup steps below based on how you want to connect Pipedrive.
Choose this option for the fastest setup. You authorize Lovable’s Pipedrive app with your Pipedrive account, and no API token is needed. In the connection form, this option is labeled Connect with Pipedrive.
1

Open Pipedrive in Connectors

Open Connectors and select Pipedrive. For the other places to open the catalog from, see Where to find connectors.
2

Add a connection

Click Add connection.
3

Name the connection

In Display name, name the connection (for example, Pipedrive Prod). This name is only used inside Lovable to identify the connection.
4

Choose Pipedrive authentication

Under Authentication, select Connect with Pipedrive. This is the OAuth option.
5

Choose who can use this connection

Under Who can use this connection, decide who in your workspace can use the connection. You start as the only person with access:
  • Only you (default): leave the access list as is; only you can use the connection and its associated data.
  • Invite specific people: add workspace members by email; only you and the people you add can use the connection and its associated data.
  • Invite entire workspace: click Invite entire workspace to make the connection available to everyone in your Lovable workspace.
See Who can use connections and clients for more information.
6

Connect to Pipedrive and authorize

Click Connect. The Pipedrive authorization window opens, so make sure your browser doesn’t block pop-ups. If it does, Lovable redirects you instead.Sign in to Pipedrive if prompted, review the requested permissions, and authorize the app.You’ll be redirected back to Lovable with a confirmation. API calls are routed to your company’s own Pipedrive domain automatically.
When connected, anyone building in a project can ask Lovable in chat to link their project to Pipedrive (based on configured connection-level access). Your Lovable apps can then read and manage Pipedrive CRM data.

​
Working with Pipedrive data and webhooks

Each connection represents one Pipedrive user, whether it connects with OAuth or an API token, and API calls use that user’s Pipedrive permissions. If your app needs to react to CRM changes, ask Lovable to set up Pipedrive webhooks for the events you care about, such as deal creation, deal stage changes, or lead updates. Pipedrive sends webhook events to a public endpoint in your app. For critical workflows, combine webhooks with periodic API checks because webhook deliveries are not guaranteed by Pipedrive. When prompting Lovable, be specific about the records and operations your app needs. For example, mention whether the app should work with deals, leads, people, organizations, activities, pipelines, or stages.

​
Limitations

The Pipedrive connector cannot:
  • Create a Pipedrive account for you
  • Manage Pipedrive billing, plans, roles, or API access settings
  • Support per-end-user Pipedrive login. Each connection represents a single Pipedrive user account shared across projects linked to it.
  • Rotate API tokens automatically. For connections that use your own API token, generate the new token in Pipedrive and update the Lovable connection. OAuth connections refresh their credentials automatically.
  • Create a webhook receiver automatically without app code. Ask Lovable to build the public endpoint and register the webhook for the events your app needs.
If Pipedrive authorization is revoked from the Pipedrive side, you’ll need to reconnect the integration in Lovable before API calls can succeed again.

​
Manage your connection

Connections are managed from Connectors: select , then open the connection.
  • Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
  • Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.