Dragwyb AI Agent Workflows can start a workflow from native WordPress events, supported form submissions, WooCommerce activity, incoming webhooks, and chat messages. A trigger supplies event data that later workflow nodes can use, but the available fields and exact timing depend on the selected event.
Screenshot to add: [Workflow editor trigger catalog showing WordPress trigger groups and supported integrations]
Trigger catalog at a glance
The supplied plugin source defines 83 native WordPress hook triggers on a standard site, or 97 when WordPress Multisite is enabled. It also defines 23 WooCommerce triggers, four form-integration triggers, and one chat-message trigger. Optional integrations appear only when their required plugin is active. Incoming webhook endpoints are configured separately.
Native WordPress trigger groups
- WordPress Post Events and Triggers — 13 post lifecycle events, including saving, status changes, revisions, trashing, and deletion.
- WordPress User Events and Triggers — 23 user-related events for registration, profile changes, roles, password flows, and application passwords.
- WordPress Custom Events and Triggers — 7 general WordPress setup and system hooks.
- WordPress Plugin Lifecycle Events — 3 events for plugin activation, deactivation, and completed upgrade operations.
- WordPress Media and Attachment Events — 10 events for media records, attachment editing, metadata, and deletion.
- WordPress Options and Settings Events — 5 events for adding, updating, and deleting stored WordPress options.
- WordPress Comment Events and Triggers — 10 events for comment creation, moderation, status changes, trashing, restoration, and deletion.
- WordPress Taxonomy and Term Events — 7 events for taxonomy terms and term lifecycle operations.
- WordPress Authentication and Login Events — 5 login-screen and lost-password-form hooks. These do not confirm successful authentication.
- WordPress Multisite Events and Triggers — 14 network-only events for site lifecycle, signup, and network users.
Optional integrations and external events
- Contact Form 7: start a workflow from a supported form submission; the trigger can optionally filter by form ID.
- WPForms: receive form field and entry information when a supported submission is processed; optional form-ID filtering is available.
- Elementor Pro Forms: listen for classic Elementor Pro form submissions.
- Elementor Pro Atomic Forms: listen for supported Atomic Form submissions when the required Elementor Pro module is available.
- WooCommerce Events and Triggers — 23 events for orders and statuses, customers, coupons, products, stock, and cart changes.
- Incoming webhooks: receive an external service’s HTTP POST request through a configured webhook endpoint.
- Chat messages: start a workflow from a message sent to the workflow’s chat endpoint.
Configure and test a trigger
- Open Agent Workflows and edit the workflow you want to run.
- Add a trigger node that matches the event source and category.
- Set any options shown by the selected trigger, such as a form ID or a post-type filter.
- Inspect sample trigger data when the editor supports it, then map the needed fields into later nodes.
- Test with a controlled event on a staging site or low-risk record before enabling live actions.
Understand event timing and privacy
Not every hook means an operation has finished. For example, some hooks run while a form or admin screen is rendered, before a term or comment is created, or during a deletion process. Read the individual trigger guide to understand its stage and test it in your environment.
Security note: the current source normalizes general WordPress hook arguments and persists trigger payloads with workflow runs. The audit found no general redaction step in that normalization path. Some authentication-related hooks can include sensitive arguments, so do not enable those triggers on a production site until payload redaction and run-log handling have been corrected and verified.