Uncanny Automator Integration

Use a Core Forms submission as a native trigger in Uncanny Automator recipes.

Integration code: COREFORMS / Trigger code: COREFORMSSUBMITTED Class: Core_Forms\Integrations\AutomationIntegrations Source: src/integrations/class-automation-integrations.php

This is not configured on the form's Actions tab. When Uncanny Automator is active, Core Forms registers itself as an Automator integration automatically, and you build the recipe inside Uncanny Automator.

Requirements

The Uncanny Automator plugin must be active. The integration registers on init only when the Uncanny_Automator\Automator() function exists. No Core Forms settings are needed.

Setup

Install and activate Uncanny Automator.
Go to Automator > Add New and create a recipe.
Add a trigger and choose the Core Forms integration (it appears with the Core Forms icon).
Select A Core Forms form is submitted.
Add any Automator actions (send email, add user to group, call a webhook, etc.).

Trigger Details

Property	Value
Trigger sentence	A Core Forms form is submitted
Fires on	Every successful submission (`cf_form_success` hook)
User context	The currently logged-in user (if any)

The trigger fires after the submission is validated and stored, i.e. only for successful submissions. For forms submitted by logged-out visitors, use an Everyone recipe type; logged-in recipe types require a signed-in user.

Trigger Meta / Tokens

For each completed trigger run, Core Forms stores these values as trigger meta, available to the recipe's actions:

Key	Description
`FORM_ID`	ID of the submitted form
`SUBMISSION_ID`	ID of the stored submission
`SUBMISSION_DATA`	All submitted fields, JSON-encoded

SUBMISSION_DATA is a single JSON string of the whole field set (e.g. {"name":"Jane","email":"jane@example.com"}), which is convenient for webhook actions or custom code that parses the payload.

How It Works

Core Forms fires cf_form_success with the submission and form objects after every successful submission.
The bridge calls maybe_add_trigger_entry() for the COREFORMSSUBMITTED trigger with the current user ID and signed-in state.
For every matching recipe, it inserts the FORM_ID, SUBMISSION_ID, and SUBMISSION_DATA trigger meta and completes the trigger, which runs the recipe's actions.

Troubleshooting

Core Forms not listed in Automator: confirm both plugins are active; the integration requires the Uncanny_Automator\Automator() bootstrap function.
Recipe not firing for visitors: logged-in recipes need an authenticated user. Switch the recipe to the "Everyone" type for public forms.
Trigger fires but actions see no data: use the trigger meta keys above; the submitted fields live in SUBMISSION_DATA as JSON rather than as individual tokens.