Frequently asked questions

Multi-step forms can be built in Webstudio, but currently require some manual setup. You can use button navigation between form steps, though this isn't as seamless as Typeform-style automatic progression. The Webstudio team is planning to add a component editor soon which will enable creating customized, reusable UI elements like advanced multi-step forms. For now, you can also embed external widgets like Typeform or use third-party JavaScript libraries.

Currently, there's no built-in multi-step form component, but you can build one using JavaScript and Webstudio's components. For conditionals, you'll need custom JavaScript. The team is planning to add a component editor soon which will enable creating reusable UI elements like multi-step forms. For now, you can embed external widgets like Typeform or use third-party JavaScript libraries.

Webstudio webhook forms do not currently support file uploads. If you need file upload functionality, you can use a regular HTML form element (not webhook form) or create the entire form using HTML Embed. HTML forms with file inputs work fine when using POST method with multipart/form-data encoding to external services like n8n.

Webhook forms have limitations when self-hosting. Email sending is a cloud-only feature, so for self-hosting you need to implement your own backend or use services like n8n or Make.com. Currently, only JSON format is supported for webhook forms in self-hosted setups - URL-encoded format is not yet supported.

Currently, Webstudio is primarily designed for receiving data rather than sending API requests directly from the frontend. For triggering actions like sending requests to third-party services (Postmark, etc.), you would need to implement custom JavaScript in an HTML Embed component or use a webhook form that connects to a backend service like n8n or Make.com to handle the API calls.

When working with n8n workflows and Webstudio webhook forms that include file uploads, ensure your n8n workflow can handle multipart/form-data requests. Test the webhook endpoint outside of Webstudio first to verify it processes files correctly. In Webstudio, set the form action to your n8n webhook URL and method to POST. For file inputs, make sure the form has enctype='multipart/form-data'. Consider implementing error handling in your n8n workflow to provide meaningful feedback to users. Also, be aware of file size limitations both in Webstudio and your n8n hosting environment.

For forms that need to both submit data and perform actions (like scrolling or redirecting), you have several options:

1. Use Webstudio's built-in webhook forms for data submission,
2. Combine with custom JavaScript in HTML Embed for additional actions,
3. Set up proper redirect URLs in your form settings,
4. For complex workflows, consider using external automation tools like n8n or Make.com to handle form processing and subsequent actions.

Some email providers may block emails from Webstudio's form service. If you're not receiving form submissions to your custom domain email (but Gmail works fine), try whitelisting Webstudio's email service with your email provider. This is common with providers like Strato and other regional email services that have strict spam filtering.

The most likely reason you can't see form submissions is missing 'name' attribute values on each input field. Make sure every form input has a proper 'name' attribute set. You can test this by using the default form that's inserted when you click on the webhook form component - if you fill that out with proper name attributes, you should see the submitted information.

If webhook forms are showing 'something went wrong' errors even on blank pages and this affects multiple websites that previously worked, it could be a service-wide issue or a browser-specific problem. Try testing in different browsers (Safari, Chrome) and check if you're using the default action or a custom webhook. Contact support if the issue persists across multiple sites and browsers.