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 and enter the field names to expose. Blank sends metadata only; * explicitly includes non-internal fields.
3. Save the form and copy the displayed hook, such as cf_flowmattic_form_123.
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.