- 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.
A failed integration never becomes a lost submission. Every inquiry is saved first; delivery history shows receipt separately from any confirmed outcome.
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
Formwink is in beta.
Connectors ship in the order beta users ask for them.