- 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
Common use cases and example apps
| Example app | Example prompt | Description |
|---|---|---|
| Sales pipeline dashboard | Use Pipedrive and build a dashboard that shows open deals by stage, owner, and expected close date. | Track pipeline health from live CRM data. The app reads deals, stages, and users from Pipedrive so sales managers can review pipeline movement in one place. |
| Account handoff tracker | Use Pipedrive and build a handoff tracker for won deals that shows the customer, deal value, notes, and next activity. | Turn closed-won deals into operational handoffs. The app pulls deal, person, organization, and activity data so customer-facing teams can pick up the right context. |
| Lead intake queue | Use Pipedrive and build a lead intake queue where new leads can be reviewed, assigned, and moved into the right pipeline. | Manage lead qualification from a custom interface. The app lists leads and related contacts from Pipedrive, then updates records when a lead is ready for follow-up. |
| Activity follow-up assistant | Use Pipedrive and build an app that lists overdue sales activities and lets reps mark them complete after follow-up. | Keep sales teams focused on overdue work. The app reads activities by owner and due date, then updates Pipedrive after reps complete calls, emails, or meetings. |
| Customer lookup portal | Use Pipedrive and build an internal portal where support can search people and organizations before responding to customers. | Give support teams quick CRM context. The app searches Pipedrive contacts and organizations so teams can see account details without switching tools. |
| Deal-change notifications | Use Pipedrive and build a notification workflow that alerts the team when a high-value deal changes stage. | React to important CRM changes. The app uses Pipedrive webhooks or polling to detect deal updates and notify the right team members. |
How to connect Pipedrive
Workspace admins and owners can connect Pipedrive. You can create multiple Pipedrive connections using different 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, Pipedrive becomes available across all projects in the workspace. Anyone building in a project can ask Lovable in chat to link their project to it.Prerequisites
Before connecting Pipedrive, make sure you have:- A Pipedrive account
- Access to your Pipedrive API token
- Lovable workspace owner or admin role
All API requests made through this connector count toward your Pipedrive plan limits. Billing and quota are handled directly by Pipedrive, not Lovable.
Step 1: Get a Pipedrive API token
A Pipedrive API token lets your Lovable app authenticate with the Pipedrive API as the Pipedrive user who owns the token. To find your Pipedrive API token:Open your Pipedrive account
Sign in to Pipedrive with the account you want your Lovable app to use.
Open the API tab
Select the API tab. If you do not see an API tab, check that your Pipedrive plan and role allow API access.
Step 2: Connect Pipedrive to Lovable
You can create multiple connections using different API tokens.Configure the connection
- Display name: name the connection, for example
Pipedrive Prod. - API token: paste your Pipedrive API token.
Choose who can access this connection
Under Who can access this connection, decide who in your workspace can use the connection:
- Only you (default): only the person creating the connection can use it and its associated data.
- Invite specific people: only you and explicitly added workspace members 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.
Working with Pipedrive data and webhooks
The connector uses Pipedrive’s API token authentication. Each connection represents one Pipedrive user, 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. To rotate a token, generate or copy the new token in Pipedrive and update the Lovable connection.
- 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.
How to unlink projects from a connection
Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects. To unlink projects:
When unlinked, those projects will no longer have access to through this connection. If a project needs again, you can link it to any available connection.