FluentForms Integration: Trigger, Setup, and Automation Examples
Krom Automation Pro connects to FluentForms, a fast and lightweight WordPress form builder.
When a visitor submits a FluentForms form successfully, Krom Automation fires the trigger and passes all submitted field data into the workflow as merge tags — ready to use in email actions, CRM syncing, Slack notifications, Google Sheets logging, and more.
No API key or configuration is required. Krom Automation detects FluentForms automatically when the plugin is active.
Requirements #
- Krom Automation Pro installed and activated
- FluentForms (free or Pro) installed and active
Available trigger #
Form Submitted
Fires when a FluentForms submission is processed and inserted successfully into the database.
| Data field | Description |
|---|---|
form_id | The FluentForms form ID |
form_title | The form title |
entry_id | The unique ID of the submission entry |
page_url | URL of the page where the form was submitted |
user_id | WordPress user ID of the submitter (only present if the user is logged in) |
| All field values | Every submitted field is available as a merge tag using the field name |
About field merge tags: FluentForms field values are accessible using the field’s input name attribute. After your first real submission, open the Krom Automation execution log for that run and look at the input data on the trigger step. You’ll see the exact field keys as Krom Automation captured them — use those keys as your merge tag names.
Setting up your first FluentForms workflow #
- Go to Krom Automation > Workflows and click Add New Workflow.
- Click Add Trigger and select Form Submitted under the FluentForms category.
- If you have multiple FluentForms and only want this workflow to run for one, add a Condition node. Set the field to
form_id, operator toequals, and the value to your specific form ID. - Add your actions below the trigger or condition.
- Use field name merge tags in your action fields.
- Simulate the workflow to confirm tags resolve correctly, then activate.
Screenshot: FluentForms Form Submitted trigger on the canvas with a Send Email action below it.
Real-world automation examples #
Auto-responder to the submitter Trigger: Form Submitted (filtered by form_id) Action: Send Email to the submitter’s email field with a personalised confirmation using their name field as a merge tag.
Add new contact to FluentCRM Trigger: Form Submitted Action: FluentCRM Create or Update Contact using the email and name fields from the submission.
Notify the team in Slack Trigger: Form Submitted (filtered by form_id to your contact form) Action: Slack Send Message to your #inquiries channel with the submitter’s name, email, and message.
Log every submission to Google Sheets Trigger: Form Submitted Action: Google Sheets Append Row with the form title, entry ID, submitter name, email, and timestamp as columns.
Pre-built templates #
| Template | What it does |
|---|---|
ff-auto-responder | Auto-responder email on FluentForms submission |
ff-lead-notification | Team notification for new FluentForms leads |
ff-lead-to-crm | Syncs form submission data to FluentCRM automatically |
Troubleshooting on FluentForms integration #
Field merge tags aren’t resolving. Go to Krom Automation > Logs, find the relevant execution, and open the step detail for the trigger. Look at the input data to see the exact keys your FluentForms fields were captured under. Use those exact keys in your merge tags.
The workflow runs for all forms, not just the one I intended. Add a condition on form_id set to equals and your specific form ID. Without this, the trigger fires for every FluentForms submission across the site.
