FlowMattic

Core Forms 4.9.5 adds Trigger FlowMattic under Actions → Automation. This connection uses FlowMattic's supported Plugin Actions trigger. It does not install a separate Core Forms app in FlowMattic's integration catalog.

1. Add the action to the Core Form you want to automate.
2. Choose This form. Under Fields to expose, choose Insert field, select the fields you need, then choose Done. Blank sends metadata only; All non-internal fields (*) explicitly includes all non-internal fields.
3. Use Copy hook to copy the exact hook, such as cf_flowmattic_form_123. Changing the trigger scope updates the displayed and copied hook immediately. Save the form to retain the setting.
4. In FlowMattic, choose Plugin Actions → Plugin or WP action triggered and enter that hook name.
5. Capture a sample while the workflow is listening. The single array argument contains form_id, form_title, form_slug, submission_id, submitted_at, event_id, and entry. Map the named keys inside entry into your next steps.
6. Enable the workflow.

For a shared workflow, select Shared hook for opted-in forms on each relevant form and use cf_flowmattic_submission. Filter by form_id in the workflow when routing forms differently. Only forms with this action send events; all other forms remain unaffected.

The trigger uses the normal successful-action pipeline, so payment forms wait for confirmed payment. Spam and pending-payment submissions are also rejected by the bridge. Unsaved submissions have a unique event ID and a submission ID of zero. IP address, user agent, raw requests, nonces, passwords, and local upload paths are not added to the event.

No active hook listener is reported as a configuration failure. A successful dispatch means that the hook listeners ran, not that every later FlowMattic operation succeeded. Check FlowMattic's execution history. The shared action runner prevents replay of completed saved executions. Use event_id in any downstream operation that requires its own deduplication.

Reference: FlowMattic Plugin Actions.

Testing the Current Form

Test action starts with synthetic examples for this form's exact field names. Checkbox groups remain arrays. The samples do not come from customer submissions or saved default answers. Edit the JSON before sending; Use form field samples resets it to the current form's examples.

After a successful test, the action editor shows the hook and selected entry payload. This is the argument dispatched to the hook; it is not proof that later steps in FlowMattic completed. A blank field selection deliberately gives an empty entry object/array. A missing selected field produces an error instead of a misleading success.

Test values are not stored as action settings. Saving the form should keep the same intended actions, without adding blank or unknown cards.