Overview
This node is a Form Trigger that starts an n8n workflow when a form is submitted. It is designed to listen for incoming HTTP POST requests containing form data and trigger the workflow execution with that data.
Common scenarios where this node is beneficial include:
- Automating processes based on user-submitted forms, such as contact forms, surveys, or registration forms.
- Collecting and processing form data in real-time without needing external polling.
- Integrating custom forms into workflows for notifications, data storage, or further automation.
For example, you could use this node to start a workflow that sends a confirmation email whenever a user submits a signup form on your website.
Properties
| Name | Meaning |
|---|---|
| Form Fields | Defines the fields expected in the form submission. Each field includes: |
| - Field Type: The type of the form field (loaded dynamically from available field types). | |
| - Field Name: The name/key of the form field. | |
| - Required: Whether the field must be present in the submission. | |
| - Hidden: Whether the field is hidden in the form UI. | |
| - Disabled: Whether the field is disabled in the form UI. |
The "Form Fields" property supports multiple entries, allowing you to define several fields that the form will contain. The field types are loaded dynamically via a method that fetches available field options.
Output
The node outputs the form submission data as JSON under the json property of the output item. Specifically, the entire body of the incoming HTTP POST request (the form data) is passed through as-is in the output.
Output structure example:
{
"json": {
// key-value pairs representing submitted form fields and their values
}
}
There is no binary data output by this node.
Dependencies
- This node requires no external services or API keys.
- It listens for incoming HTTP POST requests on a webhook path configured internally.
- No additional environment variables or credentials are needed.
Troubleshooting
- Webhook not triggering: Ensure that the form submission is sent as an HTTP POST request to the correct webhook URL provided by the node.
- Missing form fields: If required fields are not present in the submission, the workflow may not behave as expected. Verify that the form sending data matches the defined "Form Fields".
- Unknown field type error: If a field type is specified that does not exist in the field registry, an error will be thrown. Make sure to select valid field types from the available options.
- Empty payload: If the incoming request body is empty or malformed, the node will output empty JSON. Check the form submission source to ensure it sends proper data.