Ninja Forms Integration: Trigger, Setup, and Automation Examples
Krom Automation Pro connects to Ninja Forms, one of WordPress’s longest-standing drag-and-drop form builders. Every successful Ninja Forms submission fires a trigger in Krom Automation, giving you access to all submitted field data as merge tags you can use across any automation — from auto-responder emails and admin alerts to CRM syncing and email list subscriptions.
No API key or configuration is required. Krom Automation detects Ninja Forms automatically when the plugin is active.
Requirements #
- Krom Automation Pro installed and activated
- Ninja Forms installed and active
Available trigger #
Form Submitted
Fires when a Ninja Forms submission is processed successfully.
| Data field | Description |
|---|---|
form_id | The Ninja Forms form ID |
form_title | The form title |
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 key |
About field merge tags: Ninja Forms uses field keys to identify each field. The key is set per field in the form editor. After your first real submission, open Krom Automation > Logs and look at the trigger step input data to see the exact keys captured for your form’s fields. Use those keys as merge tag names in your action fields.
Setting up your first Ninja Forms workflow #
- Go to Krom Automation > Workflows and click Add New Workflow.
- Click Add Trigger and select Form Submitted under the Ninja Forms category.
- If you have multiple Ninja Forms 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 key merge tags in your action fields.
- Simulate the workflow, then activate it.
Screenshot: Ninja Forms Form Submitted trigger on the canvas connected to an action node below it.
Real-world automation examples #
Auto-responder email to the submitter Trigger: Form Submitted (filtered by form_id) Action: Send Email to the submitter’s email field with a personalised reply using their name field as a merge tag in the greeting.
Admin notification on every new submission Trigger: Form Submitted (filtered by form_id) Action: Send Email to {{admin_email}} with the submitter’s details and the form title in the subject line.
Subscribe submitter to MailerLite Trigger: Form Submitted Action: MailerLite Subscribe using the email field merge tag and the name field as the subscriber name.
Notify team in Slack Trigger: Form Submitted (filtered by form_id) Action: Slack Send Message to your preferred channel with the submitter’s name, email, and message as the notification body.
Pre-built templates #
| Template | What it does |
|---|---|
nf-auto-responder | Auto-responder email on Ninja Forms submission |
nf-lead-notification | Admin notification for new Ninja Forms leads |
nf-lead-to-mailerlite | Subscribes Ninja Forms submitters to a MailerLite group |
Troubleshooting on Ninja Forms integration #
Field merge tags aren’t resolving. Open the execution log for a real submission and look at the trigger step input data. Note the exact field key names as captured and use those in your merge tags. Ninja Forms field key names may not match the visible field label.
The workflow is running for all forms instead of just one. Add a condition on form_id to limit the trigger to a specific form. The Form Submitted trigger fires for every Ninja Forms submission across your site without this filter.
