jfb-action-events
JetFormBuilder: action events — when does an action run?
A JFB Form Action doesn't just "run on submit" — it runs on a named event, and the form admin can pick (in the action editor) which event(s) trigger each action instance. Built-in events cover the common cases (form submitted, form validation failed, payment gateway success/failure, conditional state activated). Plugins can register their own events for specialized triggers (inbound webhooks, scheduled CRON, third-party callbacks).
This skill is the companion to jfb-form-action. That one covers the action class itself; this one is the when layer.
API stability note
The Base_Event / Base_Action_Event / Base_Gateway_Event hierarchy, the 'jet-form-builder/event-types' registration filter, the 'jet-form-builder/before-trigger-event' / 'jet-form-builder/after-trigger-event' hooks, and the action-side supported_events() / unsupported_events() / get_required_events() overrides have been stable across JFB 3.x in the source observed. The plugin-version-tested value records last end-to-end verification only.
When to use this skill
- An action should run only on payment callbacks, not on plain submit.
- An action should run on validation failure (e.g. log invalid attempts).
- An action should run on conditional-block state changes.
- The plugin needs a brand-new event type (webhook receiver, scheduled task, custom integration callback).
- The diff/files contain
supported_events,unsupported_events,get_required_events,Base_Event,Base_Gateway_Event,'jet-form-builder/event-types',add_hidden,'GATEWAY.SUCCESS','DEFAULT.REQUIRED'.