Integrations · Automation
Webhooks + outcome API
Events out. Authenticated outcomes in. Configured separately.
- Method: Native
- Direction: Send and receive
- Availability: Design preview
Designed and specified. Nothing is connected in this prototype and no data is sent.
What it does
Send submission and qualification events outward; accept authenticated outcome updates through a separate inbound interface. Signed payloads, retries, delivery history.
What comes back
Whatever supported outcomes you deliberately send back.
Not implied
That an accepted webhook means everything downstream succeeded.
Delivery is not an outcome
An accepted webhook, a posted Slack message, or a created CRM contact means the send succeeded. It does not mean anything downstream worked, and it certainly does not mean the inquiry became a customer. Formwink keeps receipt, human qualification, and recorded outcome as three separate facts.
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.