> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/products/web-data/conversational-webforms-1.md).

# Webform Listener

Some operators already have existing website forms, such as HubSpot, WordPress, or custom forms, that they do not want to rebuild right away. In many cases, those forms do not automatically flow into Further, may sit outside of Further reporting, and can require separate CRM handling unless they are mapped into the platform.

Further’s Webform Listener is a legacy tool that captures submissions from existing website forms and routes them into Further without changing the on-page experience.

## What it is and what it does

Webform Listener can:

* Capture submissions from designated website forms and map key fields into Further.
* Create or update leads in Further so they can be managed alongside other lead sources.
* Help unify downstream workflows such as CRM sync, notifications, and analytics once the form is mapped correctly.

When Webform Listener is enabled and configured correctly, webform leads can:

* Appear in All Conversations.
* Follow the same CRM submission logic as other Further lead sources.
* Support notifications, marketing attribution, and downstream engagement workflows in Further.

## Why customers use it

Webform Listener helps operators who:

* Cannot change existing forms immediately, but still want lead data in Further.
* Want a more unified view of webform leads in Further and their CRM.
* Need a bridge solution while moving from legacy forms to more modern Further experiences.

## Key value

The main value of Webform Listener is operational continuity: teams can keep existing forms in place while bringing lead capture, CRM workflows, and reporting into Further.

## How it fits in the Further ecosystem

Once mapped, webform leads can work alongside the rest of the Further platform:

* Leads can appear in Further for review and follow-up.
* Sales teams can use Further communication tools and scheduling workflows with those leads.
* Marketing teams can use Further analytics to understand source, campaign, and performance data tied to those submissions.

## Important notes

* Webform Listener is considered a legacy tool and is generally the older predecessor to Static Webforms.
* The VSA must be live on the page where the webform lives for the listener feature to work.
* For new builds, Static Webforms or Conversational Webforms are the recommended path. Webform Listener is best used as a bridge for existing, hard-to-change forms.

## Setup overview

#### Prerequisites

* Further script installed on the site.
* VSA live on the page where the form exists.
* A clear list of form URLs, fields to capture, and target communities for routing.

#### Enable or access it

For legacy listener setups, work with your CSM or Support team to configure the form mapping and any required selectors or hooks for the existing form.

#### Required setup steps

* Enable webform capturing for the relevant communities or users.
* Confirm whether webform leads should also be submitted to the CRM.
* Map the form fields and verify the lead preview looks correct.
* Confirm community routing and source labeling are correct.

## How to test it

* Submit a test form with test credentials so the submission can be reviewed safely.
* Confirm the lead appears in Further and is labeled correctly.
* Confirm CRM behavior and notifications match the intended setup.

## FAQ

**Should we use Webform Listener or Static Webforms for new pages?**

For new builds, Static Webforms or Conversational Webforms are recommended. Webform Listener is best for bridging existing forms that are difficult to replace right away.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.talkfurther.com/products/web-data/conversational-webforms-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.