> 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/static-webforms.md). # Static Webforms ### What It Is Static Forms in Further are customizable webforms that allow you to capture lead information directly from your website or landing pages. They use the same intuitive drag-and-drop builder as emails and landing pages, making them simple to create and manage. Static forms can be embedded: * Inside a Further landing page * On non-Further webpages using a target selector They also integrate directly with Community Events, allowing leads to RSVP to events through an events picker field, and pull in dynamic content from the Content Hub so just one form template can adapt to every community. *** ### How It Helps You Static forms help you: * Capture RSVPs for events * Gather contact information from new prospects * Allow leads to express interest in specific care types or communities * Schedule tours for leads not using conversational forms or VSA Every form submission enriches the lead profile inside Further and your CRM. This enables automation workflows, re-engagement campaigns, and personalized follow-ups — completing the loop from first click to final conversion. *** ### How It Works #### 1. Create the Form * Use the drag-and-drop builder * Choose applicable communities * Add form fields (each field syncs designated tags back to the lead profile) Each field automatically maps data into Further and your CRM, enriching lead records. *** #### 2. Configure Settings You can: * Add a Success Message (shown after submission) * Add a Redirect URL (optional) * Toggle “Use on Landing Page” if the form is only for a specific landing page * Add Target Selector code (only if embedding on a non-Further webpage) If different communities require different embed locations, you can assign different selectors per community — no cloning required. *** #### 3. Add Community Events (Optional) To capture event RSVPs: * Add a Form Content Block * Click “Manage Fields” * Add: * **Community Events Picker** * Optional: Guest Invitation Fields This dynamically pulls in all community events assigned to that community. Further will track every RSVP, allowing you to filter and automate campaigns based on event attendance. *** #### 4. Add to a Further Landing Page (If Needed) To insert a static form into a Further landing page: * Open the landing page builder * Add a **Dynamic Content** block * Select your form Important: You cannot insert a static form via a saved row. Always use the Dynamic Content block. *** #### 4. Add to a Non-Further Landing Page (If Needed) When a **Static Form** is created, Further automatically generates a ready-to-use HTML embed snippet in the **Integrations** tab — no manual configuration required. To add the static form to your community webpage, you simply copy the snippet and paste it into the website’s HTML inside the `` tag, exactly where the form should appear. *** ### In Closing Static forms turn website engagement into actionable lead data. Whether capturing RSVPs, job inquiries, or general interest, they enrich profiles automatically and power personalized automation. They are simple to build, flexible to deploy, and deeply integrated into Further’s marketing ecosystem — ensuring no opportunity is missed. --- # 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/static-webforms.md?ask=&goal= ``` `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.