The Delete Post trigger is available in the WordPress Post group in the AI Agent Workflows editor. It starts a workflow when WordPress fires the delete_post hook. The exact timing depends on the event represented by that hook.
Screenshot to add: [Workflow editor showing the Delete Post trigger and its configuration]
When this trigger fires
This trigger listens to the delete_post hook. Several post-related hooks can fire during a single editing or publishing operation; choose the one that matches the point in the lifecycle when you need the workflow to start.
Data available to later nodes
For recognized post hooks, the plugin normalizes the event into fields 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 the corresponding post data is available. Some hooks add event-specific values, such as old and new status or an update flag. Inspect a captured sample in the editor before relying on a particular field.
Configure the trigger
- Open the workflow in the visual editor and open the node picker.
- Select WordPress, then the Post group, and add Delete Post.
- If the node exposes Post Types, leave it empty to include supported posts, pages, and custom post types, or enter comma-separated slugs such as
post,page. Internal WordPress content types are skipped. - Save the workflow and test the relevant event on a test site or with non-critical content. Inspect the trigger sample before mapping values to later nodes.
Source hook
Catalog hook: delete_post. This reference describes the trigger registration in the supplied plugin source; it does not claim that a live event has been tested.