Save Post for WordPress

Starts a WordPress workflow when core fires save_post. This is the functions.php hook most teams want in a workflow builder: notify, sync, or rewrite after a post is saved.

Use the General and Design tabs to narrow when it should run. The Payload Fields section lists data WordPress passes to the flow.

Save and activate the flow, then perform the action on your WordPress site to test.

When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the Design tab.

Save Post is a trigger in the WordPress Events › Post Events group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.

Typical reasons teams add Save Post to a flow:

• Replace a save_post snippet in functions.php with a visible flow
• Sync the post to a PIM, translation service, or search index
• Notify Slack or email only when the post type or status matches

This trigger starts the flow when its signal fires on your linked site or when an inbound request matches its configuration. Downstream steps receive the trigger payload as their input.

Common patterns on the canvas:

1. Save Post → Send Email (notify editor)
2. Save Post → Set JSON → API REST POST (sync to CRM)
3. Save Post → If (role check) → Send Notification

The designer shows these tabs for this node:

_This node does not define standard output payload fields in the designer Info tab._

Other steps in the same area of the palette:

• Delete Post (event-wp-delete_post) — WordPress Events › Post Events
• Publish Post (event-wp-publish_post) — WordPress Events › Post Events
• Transition Post Status (event-wp-transition_post_status) — WordPress Events › Post Events
• Trash Post (event-wp-trash_post) — WordPress Events › Post Events