Send landing-page quote requests to Pipedrive

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 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 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 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. 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

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 for workflow checks or email delivery while you resolve the integration.