# Pipedrive integration for lead forms — Formwink

> Pipedrive: A second CRM path for outcomes. Method: Native. Direction: Send and receive. Availability: Planned.

Source: https://formwink.ai/integrations/pipedrive

- Planned
- Native
- Send and receive

# Formwink + Pipedrive

A second CRM path for outcomes.

What it does at launch

Deliver relevant lead/contact information and receive mapped deal-stage outcomes.

What comes back into Formwink

Mapped deal-stage changes on linked records.

Not implied

Universal sync.

[Join the beta to set up Pipedrive](/beta)

A failed integration never becomes a lost submission. Every inquiry is saved first; delivery history shows receipt separately from any confirmed outcome.

P

Queued, not built. There is no date.

Delivery is not an outcome. An accepted webhook, a posted message or a created contact means the send succeeded — never that the inquiry became a customer. Receipt, human qualification and recorded outcome stay three separate facts.

How it connects

Native

Data moves

Send and receive

Available?

Planned

## More in CRM & outcomes

[H HubSpot Send inquiries to HubSpot. Bring their outcomes back. Native Private beta](/integrations/hubspot) [C Calendly From “completed the form” to “booked a discovery call.” Native Planned](/integrations/calendly) [S Salesforce On the roadmap, after HubSpot and Pipedrive prove the outcome loop. Native Later](/integrations/salesforce)

## Formwink is in beta.

Connectors ship in the order beta users ask for them.

[Join the beta to set up Pipedrive](/beta) [All integrations](/integrations)