Webflow API Requests & Enhancements 🚀
1. fieldElementId
in Forms Data API
Impact: Very High
Current Status: fieldElementId
is included in webhook payloads.
Request: Extend support to the Forms Data API so we can ensure case-insensitive mapping and data stability, even when users rename fields.
How this Helps Us
fieldElementId is already included in webhook payloads, but without support in the Forms Data API, we can’t reliably track field changes.
Enables case-insensitive mapping, preventing broken connections when users adjust field names across Webflow and their destinations.
Reduces manual remapping and troubleshooting, ensuring a frictionless experience for users managing complex forms.

2. Form Fields & Forms Data in Designer API
Impact: High
Request: Enable Form Connector to access form structures and data directly via the Designer API, allowing us to fetch form details without requiring users to publish their site.
How this Helps Us
Eliminating the need for users to publish their site just to sync form structures removes friction and speeds up setup, making updates effortless.
Real-time access to form fields and schema ensures stable mappings, preventing breakages when users modify their forms.
Right now, a significant part of our UI is dedicated to reminding users to refresh and update manually—removing this need frees up space for new features that enhance the overall user experience.

3. Renaming Form Titles & Field Names via Designer API
Impact: Medium
Request: Allow Form Connector to rename form titles and field names directly via the Designer API, enabling users to manage their form structures without needing to update them manually inside Webflow.
How this Helps Us
Form Connector helps users easily locate and manage forms; allowing them to rename fields directly improves clarity and makes automation more intuitive.
Poorly named fields can cause mapping issues, especially when changed without publishing—renaming them from our app ensures consistency and prevents errors.
Giving users full control over form naming within our app enhances their experience, making Webflow’s form management more flexible and scalable.

4. Custom Element Inputs in Forms API
Impact: Medium
Current Status: Webflow form webhooks capture custom input data.
Request: Extend Forms API schema to support custom element inputs field data, ensuring Form Connector users can easily locate and map fields like: date, month, color, and range.
How this Helps Us
While custom input data is included in webhook payloads, the lack of support in the Forms API schema limits how we can manage and sync these fields.
Prevents data inconsistencies and workarounds, ensuring these fields are treated like any other standard input within Webflow.
Strengthens data consistency across different Webflow Gives Webflow users more flexibility in form design while keeping automations intuitive and scalable.

5. Form Published or Change Event Webhook
Impact: Medium
Request: Extend webhook events to support a new trigger for form changes and publishing updates, allowing Form Connector to react in real time.
How this Helps Us
Enables real-time tracking of form changes, helping us detect and prevent broken form mappings before they cause issues.
Allows us to automatically disable affected forms, reducing error messages and failed submissions for users.
Helps identify recent form updates, ensuring users are promptly notified when they need to adjust their mappings.

Stronger Together
We’re grateful for the Webflow team’s collaboration in pushing Form Connector forward.
As we move ahead, we’re committed to aligning with Webflow’s WXP go-to-market efforts, solving key workflow challenges, and driving greater adoption—especially among enterprise clients. Let’s keep building! 🚀
Why This Matters to

💛
Enterprise Growth, Without the Overhead
By enabling third-party apps like ours to fill key gaps, Webflow strengthens its enterprise ecosystem—without stretching internal resources.
Stronger Enterprise Appeal
Enhancing Form Connector’s capabilities makes Webflow a more viable choice for enterprise clients, reducing friction in high-value deals.
More Reliable Integrations
API improvements ensure stable, predictable form handling—critical for teams that depend on automation at scale.
Stronger Data Integrity
Ensures scalable, error-free form handling—even when fields are renamed or customized.
🎉
Thank You for Your Continued
Support!
We’re incredibly proud of the progress we’ve made and energized by the opportunities ahead in 2025. Our focus remains on building tools that empower Webflow users and align with WXP’s go-to-market vision. Together, we can drive more innovation, unlock new possibilities, and elevate the Webflow experience for teams and businesses.
Here’s to an exciting year of collaboration and growth!
Let’s keep collaborating! 🚀
Early previews of upcoming features to gather your insights.
Feedback from client testing to refine solutions for Webflow users.
Joint opportunities to drive adoption and success in 2025.
We’re excited to grow alongside Webflow and make next year truly transformational!