/ Screencast — 58 seconds

WordPress Webhook Payload Mapping via Plugin UI

Select which hook context fields appear in the JSON payload, rename their keys, and save — all in the plugin UI without writing a single line of PHP.

/ What This Screencast Shows

By default, Webhook Actions sends the full WordPress hook context as the JSON payload. The payload mapping interface lets you choose which fields to include and rename them to match whatever key names your receiving system expects — without writing a PHP filter.

The screencast walks through opening the mapping panel for an existing webhook, selecting individual fields from the available hook context, assigning custom key names, and saving. The next time the webhook fires, the delivered payload will contain only the mapped fields under the specified keys.

This is useful when the receiving endpoint — an n8n workflow, a Zapier Zap, a REST API — expects a specific JSON shape that does not match the raw WordPress hook data. Instead of writing a custom PHP filter on the server, you configure the mapping in the UI and the plugin handles serialization automatically.

Full plugin feature overview including async queue, REST API, and delivery logs → WordPress Webhook Plugin