# Send landing-page quote requests to Pipedrive

> Plan a workflow that finds or creates a Pipedrive person, then adds the intended lead or deal. Verify mappings, duplicate handling, and partial failures.

- Canonical: https://pageree.com/integrations/pipedrive/
- Published: 2026-09-15. Updated: 2026-09-15.
- Collection: Integrations (https://pageree.com/integrations.md)
- Site index for agents: https://pageree.com/llms.txt

**The short answer.** Use an automation to receive Pageree submissions, find or create the person, and link a separate lead or deal. One contact POST does not complete the sales workflow. Configure credentials securely and verify the final records in your own account.

## Create the contact and the opportunity deliberately

To send a Pageree quote request to Pipedrive, use an automation that receives the submission, finds or creates the person, and then creates the intended lead or deal. Those are separate records. Creating a contact alone does not give your sales team a project to qualify.

This is a documented configuration recipe to implement in your own accounts. It is not a native Pageree Pipedrive app or a claim that we tested your CRM. Start with a dedicated test workflow and the [quote-request template](https://pageree.com/templates/request-a-quote-landing-page/) so the incoming fields have a clear business purpose.

## Decide what a new enquiry should become

For an unqualified renovation enquiry, a person plus a lead can be appropriate. A deal may fit when your process puts every accepted enquiry directly into a sales pipeline. Confirm that choice, its owner, and any pipeline or stage IDs before configuring the workflow.

Pipedrive's current [Persons reference](https://developers.pipedrive.com/docs/api/v1/Persons) documents `GET /api/v2/persons/search` and `POST /api/v2/persons`. Search by email with an exact match, then use the returned person ID or create a person with `name` and an `emails` array. Separately, [lead creation](https://developers.pipedrive.com/docs/api/v1/Leads) uses `POST /api/v1/leads` with a title and a linked person or organization. Do not replace that endpoint with a guessed v2 route.

| Incoming value | Destination decision |
| --- | --- |
| `data.name` | Person `name` |
| `data.email` | Person `emails` entry with `value` and appropriate primary flag |
| Returned person ID | Lead `person_id`, or the selected deal relationship |
| Project description | Approved lead/deal custom field or a separately created note |
| Page URL | Approved source field or enquiry note |
| Quote-request title | Lead `title`, assembled by the automation |

Field names under `data` must match your published form. Do not assume a generic `notes` property is available on every person: the current reference limits some contact-sync fields. Use an explicitly supported note action or approved custom field for the project narrative.

## Use automation for branching and typed data

Pageree HTTP delivery sends one request. Its dot-path mapping can rename fields into nested objects, but it does not perform a search, branch on the result, construct typed arrays, or use one response ID in a second request. A Make scenario or Zapier workflow can perform those steps.

Configure the receiving webhook with Pageree's default JSON payload, then connect Pipedrive through the automation service's authorized connection. For a reviewed custom integration, use the account-specific base URL and current [authentication instructions](https://pipedrive.readme.io/docs/core-api-concepts-authentication). API-token integrations use the `x-api-token` header. Keep that value in secure server-side settings, never in public HTML or a chat prompt.

## Copy this setup prompt

```text
Route quote requests from Pageree page [page ID] to Pipedrive
through [approved Make/Zapier/custom workflow].
Read the published form schema. Confirm whether requests become
leads or deals, the owner, and any pipeline/stage or custom-field IDs.

Receive the default payload, find a person by exact email, create
one only when needed, then create the agreed opportunity linked
to that person. Preserve a separate enquiry when the same person
asks about a different project. Map only actual approved fields.
Keep credentials in secure settings. Show the configuration for
review and explain how partial failures and duplicates are handled.
Do not claim completion until I verify the final records.
```

## Test new contacts, repeat enquiries, and partial failures

After publication, submit a marked test using an address you control. Inspect the person, the lead or deal, their relationship, the owner, and the full project description. Submit a second enquiry from the same address with a different project. Decide whether your team expects a new opportunity or an update; email alone is not an enquiry identifier.

If person creation succeeds but lead creation fails, repair and resume the failed step rather than blindly recreating everything. Record the CRM IDs in the automation run. Pageree's `submittedAt` is generated during delivery and should not be treated as a stable retry identifier.

An accepted webhook does not prove Pipedrive wrote the records. Monitor failed automation runs. Failed Pageree HTTP delivery can fall back to owner email; that successful fallback is not retried automatically to the CRM. Accepted submissions have a 30-day recovery backup. Use the [Make guide](https://pageree.com/integrations/make/) for workflow checks or [email delivery](https://pageree.com/guides/landing-page-form-to-email/) while you resolve the integration.

## Related
- [Send landing-page enquiries to HubSpot](https://pageree.com/integrations/hubspot.md): Connect Pageree form delivery to a HubSpot contact workflow. Choose an API or automation route, map properties, handle existing contacts, and verify delivery.
- [Send landing-page leads into a Make scenario](https://pageree.com/integrations/make.md): Build a Make webhook workflow for Pageree leads. Define the data structure, secure authentication, destination mapping, error handling, and verification.
- [Request-a-quote landing page template](https://pageree.com/templates/request-a-quote-landing-page.md): Ask the right questions for a useful estimate. Explore an original quote page, field checklist, confirmation copy, and AI prompt for your service business.

## Build it with your agent

Pageree is an MCP server. Add https://mcp.pageree.com/ to an MCP client that supports Streamable HTTP and OAuth, sign in, and the agent can build, publish and measure the page. Setup for every supported client: https://pageree.com/docs.md. Sign up: https://console.pageree.com/signup.