Connect an external form
Receive submissions from Typeform, Webflow, Tally or Fillout, and install the LeadPost delivery webhook so identified visitors reach Zyan.
If your forms already live somewhere else, you do not have to rebuild them in Zyan. Connect the provider once, choose which forms you want, map their fields onto lead fields, and submissions land in Lead Manager alongside everything else. The same page covers LeadPost, which delivers identified website visitors over a webhook of its own.
Before you start
External form capture needs the Leads plan feature, and an owner or admin to connect the provider account once for the whole workspace. LeadPost needs your own LeadPost account — you pay LeadPost directly for the sites you register.
Typeform, Webflow, Tally and Fillout
The four providers work the same way and live together under SettingsIntegrationsLead capture.
Open the provider card
SettingsIntegrationsLead capture, then Typeform, Webflow, Tally or Fillout.
Connect the provider account
Webflow asks for the site first, then the form. The others go straight to the form list.
Pick the form you want
It is added paused. Nothing is received yet, which is deliberate — you map first.
Map the fields
Point each provider field at one lead field: Name, Email, Phone, Company, Website or Message.
Turn Receive on
Zyan installs the webhook at the provider for you. Submissions start arriving.
You cannot turn Receive on until Email or Phone is mapped
At least one provider field has to map to Email or Phone. Without one the lead cannot be contacted or matched against an existing lead, so Zyan refuses to start receiving.
Receive is the lifecycle switch
External forms have no Publish button. Receive is the whole lifecycle: on installs the provider hook, off retires it.
Pausing cleans up after itself
Turning Receive off retires the webhook at the provider. There is nothing left behind in Typeform or Webflow to go and delete by hand, and no orphaned hook quietly firing at an endpoint that no longer listens.
You also must pause a form before editing its mapping or refreshing its field list. The controls are locked while it is receiving.
Reading the status pill
| Pill | Means |
|---|---|
| Receiving submissions | Working. The hook is installed and live |
| Not receiving | The connection is fine, but the matching form in Lead Manager is not published |
| Needs attention | Something about the form or its mapping needs a look |
| Reconnect required | The provider account connection has lapsed. Reconnect it |
| Paused | You turned Receive off |
What you cannot change in Zyan
The provider owns the form. In Zyan its field rows are locked, there is no hosted page and no embed, and the Share tab has nothing to offer. In the forms list the row carries an External chip and reads Captured from an integration instead of a link.
Tally and Fillout deliveries are read back from the provider before they are landed. Where a provider does not sign its deliveries, the card says so — worth reading once when you connect.
Using an external form in an automation
A form-submission trigger can be narrowed by Submission source — hosted, embed, Typeform, Webflow, Tally or Fillout — and scoped to one Form. Every submission also fires the general lead created trigger.
The LeadPost delivery webhook
LeadPost identifies anonymous visitors on a website and pushes them to you. Zyan mints one webhook URL per site you register, and that URL is revealed exactly once.
Open the LeadPost card
SettingsIntegrationsLeadPost, then Add site.
Enter the Website URL and add the site
The webhook URL appears. Copy it now — it is shown once and cannot be read back.
Paste it into LeadPost
In LeadPost, go to CampaignsLead DeliveryPush Leads via Webhook, click Configure, paste the URL, and map every field to the same field name.
Activate the site in Zyan
Back on the LeadPost card, click I've installed it / Activate on the site row. The status flips from Pending install to Active.
Only now, test in LeadPost
Click Test Webhook in LeadPost, then Enable.
The order of the last two steps is not negotiable
Zyan refuses deliveries to a site that is still Pending install. If you run LeadPost's Test Webhook before clicking Activate in Zyan, the test is dropped as paused and LeadPost reports that nothing was stored — which looks exactly like a broken webhook and is not one.
Site states
| State | Means |
|---|---|
| Pending install | The site exists in Zyan but deliveries are refused |
| Active | Deliveries are accepted |
| Paused | Deliveries are refused for now |
| Canceled | The site is finished |
Re-mint webhook issues a new URL and invalidates the current one immediately — update LeadPost straight after, or deliveries stop. Refresh reloads the site list and statuses. Removing a site stops its webhook and takes it off the list; leads it already captured stay in Lead Manager.
Identified visitors do not become leads on their own — they wait for you in Website visitors.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Receive will not turn on | No provider field is mapped to Email or Phone | Map one, then try again |
| The mapping controls are locked | The form is receiving | Pause it, edit the mapping, turn Receive back on |
| The card reads Not receiving | The matching form in Lead Manager is not published | Open Leads → Forms and check it is not Draft or Archived |
| The card reads Reconnect required | The provider account connection lapsed | Reconnect the account on the provider card |
| Submissions stopped after you edited the form at the provider | The field list changed under the mapping | Pause, refresh the fields, re-map, turn Receive back on |
| LeadPost's Test Webhook reports nothing stored | The site is still Pending install | Click I've installed it / Activate in Zyan first, then test |
| The LeadPost webhook URL is gone | It is shown exactly once | Use Re-mint webhook, copy the new URL, and update LeadPost |
| Deliveries stopped right after a re-mint | The old URL died the moment the new one was issued | Paste the new URL into LeadPost |