- Design preview
- Native
- Send and receive
Formwink + Webhooks + outcome API
Events out. Authenticated outcomes in. Configured separately.
What it does at launch
Send submission and qualification events outward; accept authenticated outcome updates through a separate inbound interface. Signed payloads, retries, delivery history.
What comes back into Formwink
Whatever supported outcomes you deliberately send back.
Not implied
That an accepted webhook means everything downstream succeeded.
A failed integration never becomes a lost submission. Every inquiry is saved first; delivery history shows receipt separately from any confirmed outcome.
Designed and specified. Nothing is connected in this prototype and no data is sent.
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?
Design preview
What teams send to Webhooks + outcome API with Formwink
Keep exploring
Formwink is in beta.
Connectors ship in the order beta users ask for them.