- Planned
- Via webhook
- Send and receive
Formwink + Clay
Run an inquiry through your Clay table, and read the result on the brief.
What it does at launch
Send the submission to a Clay webhook source so your existing table can enrich and route it, then send selected fields back through the outcome API to appear on the lead brief. Your Clay workspace, your credits, your enrichment providers.
What comes back into Formwink
Whatever columns you deliberately map back, each labelled with its source and the date it was fetched.
Not implied
A native Clay app, or that anything Clay returns is verified. Enrichment adds context a reviewer reads; it never sets a fit label, never disqualifies an inquiry, and is never treated as something the respondent told you. Clay plan and credit costs are yours, not part of a Formwink subscription.
A failed integration never becomes a lost submission. Every inquiry is saved first; delivery history shows receipt separately from any confirmed outcome.
Queued, not built. There is no date.
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
Via webhook
Data moves
Send and receive
Available?
Planned
Keep exploring
Integrations
People Data Labs
Company context on a brief, from the work email they already gave you.
Integrations
Webhooks + outcome API
Events out. Authenticated outcomes in.
Integrations
HubSpot
Send inquiries to HubSpot. Bring their outcomes back.
Product
Lead qualification
Understand which inquiries deserve attention, and why.
Formwink is in beta.
Connectors ship in the order beta users ask for them.