Trigger Form
Description
Section titled “Description”The FormTrigger module is a specialized trigger that initiates the workflow when a user submits a form. It extends the Webhook functionality by adding form-specific metadata (ID, name, fields). Data can arrive in two ways: via standard webhook (when the form is submitted from the frontend) or via direct invocation (for example, in OTP flows). The module extracts the form payload and passes it to the next node along with the request metadata and the configured form information.
Configuration
Section titled “Configuration”Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
| form_id | form_trigger_selector | Yes | Selects the form that will activate this workflow. You can create a new one if it doesn’t exist. |
| url_webhook | webhook_generator | No | Automatically generated URL to receive form submissions. |
Output
Section titled “Output”{ "nextModule": "siguiente_modulo", "data": { "campo_formulario_1": "valor1", "campo_formulario_2": "valor2", "_request": { "method": "POST", "timestamp": "2026-03-23T10:00:00.000Z", "source": "form", "isDev": false }, "_form": { "form_id": "123", "form_name": "Formulario de contacto", "form_fields": ["nombre", "email", "mensaje"] } }}Usage Example
Section titled “Usage Example”Basic case
Section titled “Basic case”{ "label": "Trigger Form", "form_id": "mi_formulario_contacto", "url_webhook": {}}- The webhook URL is automatically generated when saving the workflow.
- Form data is expanded at the root level of
data. - Form metadata is available in
data._formfor use in subsequent nodes. - Compatible with OTP flows (code verification), where data arrives via direct invocation with
_request.source = 'form_otp'. - Supports legacy formats with
{ params: { result: [...] } }structure. - It only has an output connection; it acts as a start node.
Related Nodes
Section titled “Related Nodes”- Webhook (generic HTTP request trigger)
- Start (basic trigger)
- decision (to validate form fields)