# Salesforce integration for lead forms — Formwink

> Salesforce: On the roadmap, after HubSpot and Pipedrive prove the outcome loop. Method: Native. Direction: Send and receive. Availability: Later.

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

- Later
- Native
- Send and receive

# Formwink + Salesforce

On the roadmap, after HubSpot and Pipedrive prove the outcome loop.

What it does at launch

Lead or contact creation with approved mappings; opportunity-stage outcomes back. Scoped for self-serve customers, not a general sync engine.

What comes back into Formwink

Mapped opportunity outcomes on linked records.

Not implied

That internal Salesforce experience equals a shipped self-serve connector.

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

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

S

On the list, built when beta users ask for it. Listing it here is not a commitment.

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?

Later

## 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) [P Pipedrive A second CRM path for outcomes. Native Planned](/integrations/pipedrive)

## Formwink is in beta.

Connectors ship in the order beta users ask for them.

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