
RT Connect Webhooks is a two-way WordPress webhooks plugin that turns your site into a no-code automation hub. Most WordPress webhook plugins only push data out — RT Connect Webhooks also lets external tools push data in, so you can automate WordPress in both directions from a single, clean admin screen with dedicated tabs for Outgoing Webhooks, Incoming Actions, and a full Logs view.
If you’re searching for a way to connect WordPress to Zapier, connect WordPress to Make, or connect WordPress to Pabbly Connect without writing a custom REST controller, RT Connect Webhooks is the missing bridge between that platform and your site.
Send a webhook automatically when something happens — WordPress core events (login, register, update, delete users; publish/update/delete posts; new/updated/trashed/deleted comments; emails sent) plus dedicated trigger groups for every popular plugin category, each appearing automatically once that plugin is active:
For every outgoing webhook you can configure:
X-Webhook-Signature header, so the receiving service can verify the request really came from your siteFlip the direction: generate a unique, secure URL that any external service — Zapier, Make, Pabbly, a form plugin, a mobile app, a custom script — can POST data to. RT Connect Webhooks then performs the configured task, including:
Each incoming action can require its own auth token, so only requests that know the secret are accepted.
Every outgoing delivery and every incoming request is recorded in a single searchable log with a Direction column (incoming or outgoing), the HTTP status code, number of attempts, and the full response body — viewable in a detail popup without leaving the settings page. The admin screen keeps Outgoing Webhooks, Incoming Actions, and Logs in separate tabs so each direction of your webhook automation stays easy to manage on its own. Clear the log at any time.
/wp-json/rtcw/v1/ for managing webhooks, incoming actions, and logs programmaticallyrtcw_payload filter to modify an outgoing payload before it’s sentrtcw_event_dispatched action that fires after an event has been sent to all matching webhooksRTCW_Webhooks::manual_trigger( $event, $data ) to fire a webhook event from your own PHP code@wordpress/components React library, so it looks and feels native to WordPressAll admin REST endpoints require the manage_options capability (cookie auth + X-WP-Nonce, or an authenticated application password). The incoming-action delivery endpoint is public and secured separately, per action, with its own auth token.
GET /wp-json/rtcw/v1/webhooks — list outgoing webhooksPOST /wp-json/rtcw/v1/webhooks — create an outgoing webhook (url, enabled, events[], secret, method, content_type, auth_type, auth_key_name, auth_key_value, auth_token, auth_username, auth_password, custom_headers[], timeout, retry_count)PUT /wp-json/rtcw/v1/webhooks/{id} — update an outgoing webhookDELETE /wp-json/rtcw/v1/webhooks/{id} — delete an outgoing webhookPOST /wp-json/rtcw/v1/webhooks/{id}/test — send a one-off test payloadGET /wp-json/rtcw/v1/events — list available trigger events (WooCommerce-aware)GET /wp-json/rtcw/v1/logs — recent delivery logs (incoming and outgoing)DELETE /wp-json/rtcw/v1/logs — clear the delivery logGET /wp-json/rtcw/v1/incoming-actions — list incoming actionsPOST /wp-json/rtcw/v1/incoming-actions — create an incoming action (label, action_type, target_hook, auth_token, enabled)PUT /wp-json/rtcw/v1/incoming-actions/{id} — update an incoming actionDELETE /wp-json/rtcw/v1/incoming-actions/{id} — delete an incoming actionGET /wp-json/rtcw/v1/incoming-action-types — list available incoming action typesPOST /wp-json/rtcw/v1/incoming/{key} — public endpoint external services call to deliver data into an incoming action (send an X-RTCW-Token header if the action requires one)Building the admin app from source: the React source lives in src/. Requires Node.js.
npm install
npm run start — watch mode while developing
npm run build — production build into `build/` (already built and committed for this release)