ASDK and Pipedrive: send website leads to your CRM
How ASDK will send qualified website leads to Pipedrive with the visitor's answers and a summary, why the connection is coming soon, and what works today.
- Status
- Not available yet. This page explains what you can use in the meantime.
- Plan
- CRM sync: from the Pro plan
- Vendor
- Pipedrive website
Agents that work with Pipedrive
Every agent answers from the same knowledge base about your website. Statuses come from the ASDK catalog: early-access agents work today, coming-soon agents do not yet.
How it works with Pipedrive
On this page
Pipedrive users plan their work around deals and the next step on each one. A website conversation that ends with "sure, call me next week" is exactly the kind of next step that gets lost when it lives in a chat transcript. ASDK is meant to put it straight into Pipedrive. The connection is built and is coming soon; this page explains what it does, why it is not switched on yet, and how to get leads into Pipedrive today.
What ASDK and Pipedrive do together
The Sales agent (early access, from the Pro plan) talks to visitors who show buying intent, such as questions about pricing, a demo or whether you are a fit. It answers their question first from your own pages, then asks the qualifying questions you wrote in plain language, one at a time. Each lead gets a score from your rules, with a reason.
When the Pipedrive connection is live, each lead is meant to arrive like this:
- A person, created or updated by email address, so a returning visitor does not become a duplicate.
- A note on the person with the answers to your qualifying questions, the lead score and a short summary of the conversation, so whoever picks up the lead can skip the questions the visitor already answered.
Leads that Chat captures when it cannot answer a question count too. They carry the visitor's question, which tells your team what to say first.
An example: from a website question to a Pipedrive lead
Picture an IT services firm that sells managed support to companies with 20 to 200 employees. A visitor asks whether the firm supports offices in two cities. The Sales agent answers from the service-area page, then asks the firm's two qualifying questions: the number of employees and the current support setup. The visitor says 60 employees and an outgoing provider, which fits the firm's rules, so the agent offers a call.
With the Pipedrive connection, the visitor becomes a person in Pipedrive, and a note holds the answers, the score and a short summary of the conversation. The salesperson who picks up the lead already knows the size, the situation and the reason for the call.
Until the connection is switched on, the same lead can reach Pipedrive through a webhook and an automation tool, as described below.
Why it is coming soon
Pipedrive requires OAuth 2.0 for apps that connect to customers' accounts, and every new public app has to pass Pipedrive's approval process before it is listed in the Pipedrive Marketplace. Pipedrive's documentation on OAuth authorization and the app approval process describes both; reviewers test the installation flow, the requested scopes and token handling (checked October 2026).
The ASDK connection is built to those rules and is waiting for approval. Until it is approved, the connect button stays off. We will not ask for your personal API token as a shortcut: OAuth shows you exactly what the app may access, and you can remove it from Pipedrive at any time.
Get leads into Pipedrive today
ASDK can send each new lead to a webhook, available in early access from the Starter plan. Zapier and Make both connect that webhook to Pipedrive.
Create a webhook trigger
In Zapier, start a Zap with Webhooks by Zapier and the Catch Hook event. In Make, start a scenario with the Custom webhook module. Either gives you a URL.
Add it to ASDK
Add the URL as a webhook destination in ASDK. Then leave a test lead by chatting on your own site, so the automation tool receives a sample and learns the fields.
Add the Pipedrive steps
Zapier's Pipedrive integration offers actions such as Find or Create Person, Create Lead and Create Note, and a note can be linked to a person, a lead or a deal (checked October 2026). Make's Pipedrive app has comparable modules. A common setup: find or create the person by email, create a lead for them, and add a note with the conversation fields.
Turn it on and test again
Switch the automation on, start a chat on your own site, leave your details and check that the person and the lead appear in Pipedrive.
When the native connection ships, you can switch to it and turn the automation off, or keep the automation for other steps, such as an alert in a team channel.
What is available and what is coming soon
| Item | Status |
|---|---|
| Native Pipedrive connection (OAuth) | Coming soon |
| New leads to a webhook, then to Pipedrive via Zapier or Make | Available in early access |
| Sales agent: qualifying questions and lead score | Early access, from the Pro plan |
| Chat agent: contact capture when it cannot help | Early access, from the Free plan |
Before you connect: tidy your Pipedrive side
- Decide where website leads start. Pipedrive keeps leads separate from deals. A lead suits a visitor who still needs a first call; a deal in your first pipeline stage suits a visitor who already booked a meeting. Pick one rule and stick to it.
- Label the source. A label or a custom field for "website chat" lets you report on how many deals the website produces.
- Make the first next step automatic. Whoever owns website leads should see a follow-up task the same day. Our guide to speed to lead explains why the first hour matters.
- Keep the questions few. Two or three qualifying questions you actually use for routing beat a long list. See how to qualify inbound leads with AI.
- Tell visitors where their details go. Your privacy notice should mention that contact details from the chat go to your CRM.
Try the Sales agent in early access
Qualifies visitors, books meetings and sends leads to your CRM through webhooks and Zapier.
Sources
Pages we read for this page, with the date we checked each one.
- OAuth authorization — Pipedrive Developer Documentation · checked October 21, 2026
- App approval process — Pipedrive Developer Documentation · checked October 21, 2026
- Oauth — Pipedrive API v1 reference · checked October 21, 2026
- Pipedrive integrations — Zapier · checked October 21, 2026
- Pipedrive integration — Make · checked October 21, 2026
Frequently asked questions
Something else? Write to hello@asdk.com
Can I connect ASDK to Pipedrive today?
Not directly yet. The Pipedrive connection is built and waits for Pipedrive's approval of the ASDK app. Until then, a webhook through Zapier or Make can create Pipedrive persons and leads from ASDK leads.
What will ASDK send to Pipedrive?
For each lead, a person created or updated by email address, plus a note with the answers to your qualifying questions, the lead score and a short summary of the conversation.
Will ASDK ask for my Pipedrive API token?
No. The connection uses Pipedrive's OAuth sign-in, which Pipedrive requires for Marketplace apps. You approve access in Pipedrive and can remove the app there at any time.
Which ASDK plan includes CRM sync?
CRM sync is part of the Pro plan and above, together with the Sales agent that qualifies the leads it sends.