The WordPress Post trigger group contains 13 catalog entries in the supplied AI Agent Workflows source. These triggers listen to WordPress post lifecycle hooks and can provide normalized post fields to later workflow nodes.
Screenshot to add: [Workflow editor WordPress Post trigger group and available post event nodes]
Available Post triggers
- Trigger Workflows on Post Status Updates
- Trigger Workflows When a Post Is Moved to Trash
- Trigger Workflows When a Post Is Deleted
- Trigger Workflows on Post Revision Creation
- Use the WordPress Meta Box Setup Trigger
- Trigger Workflows Before a Post Is Deleted
- Use the WordPress Delete Post Trigger
- Trigger Workflows When a Post Is Updated
- Trigger Workflows When a Post Is Saved
- Trigger Workflows When a Post Is Restored
- Trigger Workflows After a Post Is Inserted
- Trigger Workflows When WordPress Inserts a Post
- Use the WordPress Trash Post Trigger
Important differences and duplicate-event risks
Several catalog entries can fire during the same editing operation. Post Moved to Trash and WP Trash Post both use wp_trash_post. Save Post, WP Insert Post, WP After Insert Post, and Post Updated are separate hooks that can occur around a save/update sequence. Avoid configuring overlapping triggers unless you intentionally want multiple workflow runs.
Post Types filter
The content lifecycle triggers that support the Post Types field can be limited using comma-separated type slugs such as post,page. When left empty, supported posts, pages, and custom post types are included; internal WordPress content types are skipped. The Meta Box Setup and Revision Creation entries do not expose this same filter.
Payload data
Recognized post hooks can expose values such as post ID, title, content, text-only content, excerpt, status, type, slug, author, dates, parent ID, and hook-specific values such as old/new status or an update flag. Inspect a captured sample before mapping fields into later nodes.