# Calendly integration for lead forms — Formwink

> Calendly: From “completed the form” to “booked a discovery call.” Method: Native. Direction: Receive. Availability: Planned.

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

- Planned
- Native
- Receive

# Formwink + Calendly

From “completed the form” to “booked a discovery call.”

What it does at launch

Link bookings, cancellations, and reschedules to the inquiry. Webhook access has Calendly plan requirements shown in setup.

What comes back into Formwink

Booked, cancelled, rescheduled. Booked is not attended; attended is not won; a link click is none of these.

Not implied

Meeting attendance or revenue.

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

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

C

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

Receive

Available?

Planned

## More in CRM & outcomes

[H HubSpot Send inquiries to HubSpot. Bring their outcomes back. Native Private beta](/integrations/hubspot) [P Pipedrive A second CRM path for outcomes. Native Planned](/integrations/pipedrive) [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 Calendly](/beta) [All integrations](/integrations)