This article explains how to set up a workflow that fires automatically when a form is submitted in HappyFox Workflows, and how to use the submitted field values and metadata as trigger data in your workflow.
Prerequisites
- A form must already exist in HappyFox Workflows. To create one, navigate to Manage > Forms and click +.
- The form's public link must be enabled. Open the form, click Share Link, and toggle Enable to make the link Accessible on. Forms shared via this link — or via the Generate Form Link action in a workflow — are the sources the Form Submitted trigger listens to.
Note: The Form Submitted trigger does not capture submissions from forms embedded or submitted through channels other than the shareable public link.
Setting up the trigger
-
Click + Create Workflow in the top-right corner of HappyFox Workflows.
The Create New Workflow dialog.
-
Enter a name in the Workflow Name field. Optionally, toggle Enable email notification for failed workflows on.
-
Click Create Workflow.
-
On the workflow canvas, click the trigger block — it appears as the first numbered node on the canvas — to open the trigger selector.
-
Under Workflows, select Form Submitted.
The trigger selector showing Workflows triggers, including Form Submitted.
-
In the Select the Form dropdown, choose the form you want this workflow to watch.
The Form Submitted trigger configuration panel with the form dropdown expanded.
Step 1: Submit a test form response
- Open the form's public link in a browser and submit a test response with representative field values.
Note: HappyFox Workflows needs at least one real submission to populate the trigger data list. If no submissions exist yet, the Received Trigger Information panel is empty until you complete this step.
-
Return to the trigger configuration panel and click Refresh next to "Last refreshed." Your test submission appears in the trigger data list, identified by its submission ID and timestamp.
The Received Trigger Information panel showing a recent test submission.
-
Select the test submission from the list.
Form identification fields:
| Field | Description |
|---|---|
triggered_form_id |
The numeric ID of the form that was submitted. |
triggered_form_name |
The display name of the form. |
form_link_id |
The UUID of the specific form link used to submit the form. |
source |
How the form link was generated. Common values: form_detail_page (link shared manually from the form detail page), workflow (link generated by a workflow step such as Send Email or Generate Form Link). |
submitted_at |
ISO 8601 timestamp of when the form was submitted. |
Form field answers: All field responses from the submitted form are included directly as top-level keys in the event data. The key name for each answer matches the field's label (or internal name) as configured on the form.
Parent workflow context (only present when source is workflow):
| Field | Description |
|---|---|
workflow |
The name of the parent workflow that generated the form link. |
workflow_id |
The ID of the parent workflow. |
workflow_step_id |
The ID of the workflow step in the parent workflow that generated the form link. |
step_type |
The step type of the parent workflow step that generated the link (for example, send_email, generate_form_link). |
metadata |
A dictionary of key-value metadata passed through from the parent workflow step, populated from the Include Metadata field on the Send Email or Generate Form Link action. |
Step 2: Review trigger data and proceed
-
Review the trigger details panel. It shows every field value submitted with the form — including individual field responses, the Triggered Form Id, Triggered Form Name, Source, Submitted At timestamp, and Form Link Id.
The trigger details panel showing form field values and submission metadata.
Note: Multi-option fields expose both their selected IDs and their display values as separate variables. For example, a multiple-option field named "locations" provides 3671 Multiple Option Field Values (the text labels) alongside 3671 Multiple Option Field Ids (the numeric IDs). Use the Values variables in message text; use the IDs when passing data to actions that require identifiers.
-
Optionally, click Add Trigger Condition to filter which submissions fire the workflow. Trigger conditions on the Form Submitted trigger work the same as on any other trigger type — use Search Details to find a specific field, then set the condition value and logic.
-
Click Proceed to confirm the trigger and continue building your workflow. All form field values and metadata from Step 10 are now available as variables in every subsequent action.
Next steps
Your workflow is now configured to fire on every submission of the selected form. Next, add actions to route or process the form data — for example, creating a ticket, sending a notification, or writing the response to a connected app.