- Private beta
- Native
- Send and receive
Formwink + HubSpot
Send inquiries to HubSpot. Bring their outcomes back.
What it does at launch
Create or update a contact using approved mappings; link the inquiry; bring back selected qualification and associated deal-stage changes. No automatic deal creation; no overwriting without a clear policy.
What comes back into Formwink
CRM-recorded qualification and deal outcomes, where reliably linked to the inquiry and form version.
Not implied
A universal two-way sync, or that every deal on a contact came from the latest submission.
A failed integration never becomes a lost submission. Every inquiry is saved first; delivery history shows receipt separately from any confirmed outcome.
Being built with a small number of beta workspaces. Not generally available.
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?
Private beta
What teams send to HubSpot with Formwink
Product
Lead qualification
Understand which inquiries deserve attention, and why.
Solutions · For your workflow
Client intake form
Structure the first conversation so the right clients get a fast, informed reply.
Solutions · For your workflow
Project inquiry form
Ask about the problem first, branch on the answer, and know which projects fit before the call.
Keep exploring
Product
Lead qualification
Understand which inquiries deserve attention, and why.
Solutions · For your workflow
Client intake form
Structure the first conversation so the right clients get a fast, informed reply.
Integrations
Slack
A structured brief in your channel, with one-tap feedback.
Integrations
Webhooks + outcome API
Events out. Authenticated outcomes in.
Formwink is in beta.
Connectors ship in the order beta users ask for them.