You can keep the flexibility of Webflow for design while using Full Fabric as your single source of truth for student data.
How it works
All Webflow integrations are based on Full Fabric Forms:
You create or configure a form in Full Fabric and obtain its endpoint URL.
You either:
Configure Webflow forms to POST directly to that endpoint, or
Embed Full Fabric forms directly inside your Webflow pages.
Both approaches ensure submissions end up in Full Fabric, where they create or update person records, applications and related objects according to your form configuration.
Key benefits:
Real-time capture of website leads into Full Fabric
Centralised form logic and validation in Full Fabric
Automatic trigger of confirmation emails and workflows
Consistent tracking of website as a source/channel
Freedom to keep using Webflow’s visual design tools
Prerequisites
You’ll need:
Full Fabric admin access to manage forms and endpoints
Webflow access with permission to edit forms and site settings
A plan for which website forms should create records in Full Fabric (e.g. general enquiry, open day registration, brochure download, application start)
A mapping between Webflow form fields and Full Fabric form fields
Getting your Full Fabric form endpoint
Open Apps > Forms in Full Fabric.
Create a new form for website submissions (e.g. “Website Enquiry”) or open an existing one.
Include all required fields: name, email, phone, programme of interest, consent, source, etc.
Publish the form.
Open the form’s Endpoint settings.
Copy the endpoint URL.
Option 1: Webflow forms posting to Full Fabric
In this option, you keep Webflow’s native forms, and configure them to post submissions to Full Fabric.
In Webflow, open the page and form you want to integrate.
Open the form’s Settings and locate the Action/POST URL field.
Paste the Full Fabric form endpoint URL into that field.
Ensure each form field has a unique Name attribute that matches the corresponding Full Fabric form field name.
Add hidden fields (if needed) for programme code, intake, or source.
Publish your Webflow site.
Submit test entries to ensure data arrives in Full Fabric as expected.
This approach is best when:
You want Webflow to remain the primary form container.
You have simple forms and only need basic mapping.
You may also want Webflow to store submissions as a backup.
Option 2: Embedding Full Fabric forms in Webflow
In this option, Full Fabric forms are embedded directly on Webflow pages.
In Full Fabric, open the form you want to embed.
Copy the provided embed script or code snippet.
In Webflow, go to the page where you want the form.
Add an Embed (custom code) component.
Paste the Full Fabric embed script into the component.
Publish your Webflow site.
Test the form on the live page.
This option is best when:
You want Full Fabric to handle all form logic and storage.
Your forms are complex (multi‑step, conditional logic, heavy validation).
You prefer to maintain form configuration only in Full Fabric.
Testing
For either option:
Use a test page (staging environment if possible).
Submit a few test entries with clearly identified test data.
In Full Fabric, open the corresponding form’s Submissions list and verify the entries.
Check People for the new or updated records.
Confirm:
Correct personal data
Correct programme/intake, if applicable
Correct source/campaign values (e.g. “Webflow” or “Website”)
Expected automations (emails, workflows) have triggered
If entries don’t arrive:
Confirm the endpoint URL is configured correctly in Webflow (for Option 1).
Ensure the Full Fabric form is published.
For embedded forms (Option 2), check the browser console for JavaScript errors.
After go‑live
Once you launch:
Monitor website submissions in Full Fabric regularly.
Review and refine your website‑specific workflows and communications.
Use Full Fabric reporting to track website enquiry volume and conversions.
Update forms and mappings as you add new programmes, events or campaigns.
When you change anything in Webflow that touches forms:
For Option 1, verify that field names and endpoint settings remain correct.
For Option 2, re‑test embedded forms after significant design or code changes.
Troubleshooting
Issue: No submissions from Webflow in Full Fabric
Verify the endpoint URL, including protocol (https) and path.
Check that the Full Fabric form is published and active.
For Option 1, confirm there are no CORS or network issues blocking POSTs.
For Option 2, check the embed code is intact and not modified by Webflow.
Issue: Fields not mapping correctly
Check Webflow field Name attributes versus Full Fabric field names.
Adjust either the Webflow names or the form mapping.
Re‑test after each change.
Issue: Form not displaying (embedded)
Confirm the embed script is pasted exactly as provided.
Check for JavaScript errors in the browser console.
Ensure your content security policies allow loading the embedded script.
Issue: Duplicates created for returning visitors
Ensure email (or other identifier) is always captured.
Configure the form to update existing records when the identifier matches.
Review any additional custom logic that might be creating new records.
Getting support
For support, provide:
The Webflow site and page URLs that contain the form
Whether you are using Option 1 (Webflow posts) or Option 2 (embedded form)
Endpoint URL or embed snippet (redacted if necessary)
A sample test submission (email and timestamp)
Any error messages seen in Webflow or the browser console
This information helps quickly pinpoint where the problem lies.