How leads reach Zyan

Every route a lead can take into your workspace — Zyan forms, the capture API, connected form providers, website visitors, prospecting and manual entry.

Every lead your agency captures lands in one place: Lead Manager. What changes is how it got there. Zyan has six intake routes, and most agencies end up using three or four of them at once. This page shows what each one is for and where to go to set it up.

Before you start

Lead Manager needs the Leads plan feature and the leads permission — view to read the queue, edit to change anything. Owners have both. Hosted forms additionally need a verified domain under SettingsDomains.

A Zyan form

Hosted link, iframe, or the script loader

The capture API

Your own form POSTs JSON to a public endpoint

A third-party form

Typeform, Webflow, Tally or Fillout, via webhook

Website visitor identification

Anonymous traffic resolved to a person

AI Prospecting

Sourced prospects promoted to leads

Typed in by hand

A call, an email, a conversation at an event

The Lead Manager queue

Every path lands in the same queue, with the same statuses, tags and SLA.

The six routes

Route	Use it when	Set it up
Hosted Zyan form	You want Zyan to own the form — build it, style it, share a link or embed it	Create a lead form
Capture API	You already have a form you like and only want the leads	Post leads from your own form
Connected form provider	Your form lives at Typeform, Webflow, Tally or Fillout	Connect an external form
Website visitor identification	You want the people browsing a client site, not just the ones who fill something in	Website visitors
AI Prospecting	You are going outbound and need to find businesses in the first place	AI Prospecting
By hand	Someone called, or you have a spreadsheet	Add lead, Quick add or Import CSV in the queue

Hosted Zyan forms

You build the form in LeadsForms, choose its fields, style it, and publish it. It then serves from your own verified domain at /client-portal/forms/<slug>. You can share that link directly, drop the form into one of your pages with an iframe, or use the script loader so the form sizes itself to its content.

Hosted forms are the only route that gives you field mapping, dedupe, a visitor auto-reply, a consent note and per-form automation triggers in one place.

Published is not the same as live

Hosted form pages depend on a platform-level switch that ships off. Until Zyan arms hosted pages for your workspace, a published form's link and embed still show a neutral not available page and the Share tab reads “Published — waiting for hosted pages”. Check that pill before you send a link to a client.

See Create a lead form and Embed a form on your website.

Your own form, posting to the capture API

If you already have a contact form you are happy with, keep it. Generate a capture token in LeadsLead ManagerLead settingsIntegration and have your form POST JSON to the public capture endpoint. The lead lands in the same queue.

Two things to know before you choose this route:

Name, email, subject and message are all required. A missing one is a 400.
Every request carries two credentials, not one: your workspace publishable key in the headers, and the capture token in the body. Miss the headers and the call is rejected before the token is read.
These leads carry no form id, so an automation scoped to a specific form will never match them. Use an unscoped lead created trigger instead.

See Post leads from your own form.

Connected form providers

Typeform, Webflow, Tally and Fillout connect once per workspace under SettingsIntegrationsLead capture. You pick the form, map each provider field onto a lead field, and turn Receive on. Zyan installs the webhook at the provider for you — and retires it again when you pause.

The provider owns the fields. You cannot edit them in Zyan, and there is no hosted page or embed for an external form.

See Connect Typeform, Webflow, Tally or Fillout.

Website visitor identification

This is the only route where the person never filled anything in. With your own LeadPost account connected, identified visitors to your client sites are delivered to Zyan and wait in a triage inbox at LeadsVisitors. You keep the ones worth working and discard the rest; only the kept ones become leads.

See Website visitors.

AI Prospecting

The outbound side. You describe who you want in chat, narrow with the filter rail, and push the results into the CRM, a campaign, or a voice agent. Prospected leads arrive tagged and show up under the Cold outreach view in the queue.

See AI Prospecting.

By hand

Three options, all in LeadsLead Manager:

Add lead — the full form, for one lead with detail.
Quick add — a compact inline row for name, email, phone and company.
Actions → Import CSV — a spreadsheet. Rows are matched by email, so a file containing addresses you already hold updates those leads instead of duplicating them.

Where everything lands

All six routes feed the Lead Manager queue. The queue splits them into two views:

Local — leads you entered, and leads that arrived through your own inbound channels.
Cold outreach — prospected leads and identified website visitors.

Each lead's Attribution tab records which route it came from, including the capturing form where there was one.