The WordPress Trash Post Trigger trigger is available in the WordPress Post group in the AI Agent Workflows editor. It starts a workflow when WordPress fires the wp_trash_post hook.
Screenshot to add: [Workflow editor showing the wp_trash_post trigger and its configuration]
When this trigger fires
This catalog entry listens to wp_trash_post. The separate Post Moved to Trash entry uses the same hook, so adding both triggers can cause overlapping workflow runs for one trash event.
Data available to later nodes
For recognized post hooks, the plugin can provide normalized values such as source, event, post_id, post_title, post_content, post_content_text, post_excerpt, post_status, post_type, post_name, post_author, post_date, post_modified, and post_parent when post data is available. Inspect a captured sample before relying on a specific field.
Configure the trigger
- Open the workflow in the visual editor and open the node picker.
- Select WordPress, then Post, and add the trigger.
- If the node exposes Post Types, leave it empty for supported posts, pages, and custom post types, or enter comma-separated slugs such as
post,page. Internal WordPress content types are skipped. - Save and test with non-critical content, then inspect the sample before mapping values into later nodes.
Source hook
Catalog hook: wp_trash_post. This guide is based on the supplied plugin source and does not claim a live event has been tested.