Forms Used by Other Parts of Zyntro
Where else a form can be wired in
A form is not only something you share directly. Several features accept a form to use at a point in their own flow, so the form becomes a component of something larger.
The setting is always on the other feature, not on the form. Nothing in the form builder tells you a form is being used elsewhere — which is worth remembering before you change or delete one.
Warning: A form does not know what is using it. There is no list of where a form has been wired in. Before deleting a form or removing a field, consider whether another feature depends on it — and prefer duplicating a form to experimenting on a live one.
Where a form can be wired in
| Feature | What the form does there | Notes |
|---|---|---|
| Report flows | Collects the detail needed before a report is generated for somebody, so the request and the resulting document are connected. | Configured in that feature's settings. The form still records a normal completion and contact. |
| Property tools | Handles registration and viewing requests where a property flow needs to capture somebody's details. | Several separate settings, each taking its own form. |
| Booking pages | Supplies the questions asked alongside a booking on a public booking page. | Distinct from attaching a calendar to a form, which is the reverse arrangement. |
| Call flows | Associates a form with a voice flow, so a call can reference or direct somebody to it. | Set on the call flow. |
| Workflows | A submission can start a workflow, and a workflow can be scoped to one form or to all of them. | The most flexible route for anything conditional on the answers. |
| Connected AI agents | Agents can be offered your forms, so an agent in a conversation can point somebody at the right one. | Requires the form to be Published and public. |
| Artefacts | A form embedded inside an interactive piece you share with clients. | Requires the form to be Published. Covered in its own article. |
Important: Publishing is what makes a form visible to the rest of Zyntro. A Draft form works at its own address but cannot be seen by Segmentation Intelligence, cannot be offered to AI agents, and will not appear in the pickers these features use. If a form is missing from a list where you expect it, check its status before anything else.
What stays true wherever a form is used
One set of completions
behaviour
required
Every submission lands in the same completions list regardless of which surface or feature it came through.
The same actions
behaviour
required
Follow-up email, SMS, calls, enrichment, webhooks and notifications all run identically.
The same lead allocation
behaviour
required
Ownership is decided the same way wherever the submission originated.
One address
behaviour
required
There is no per-feature copy of a form. Edit it once and every use reflects the change.
No usage list
limitation
optional
A form gives no indication of what depends on it. Treat deletion and field removal with care.
Tip: Name forms that are wired into other features so their role is obvious — CMA Request, Viewing Request, Onboarding Intake. A form called Form 2 is the one somebody will eventually delete.
