內容簡介
RT Connect Webhooks 是一款雙向的 WordPress 外掛，能將您的網站轉變為無需編碼的自動化中心。它不僅能將資料推送出去，還能接收外部工具的資料，讓您能夠從單一的管理介面自動化 WordPress 的各項功能。
【主要功能】
• 雙向網路鉤子，支援資料進出
• 自動化事件觸發，如用戶註冊和訂單生成
• 生成安全的接收動作 URL
• 兼容多種平台，如 Zapier 和 Pabbly Connect
• 透明的日誌紀錄功能
外掛標籤
開發者團隊
② 後台搜尋「RT Connect Webhooks | WordPress Webhooks for Zapier, Make & Pabbly」→ 直接安裝（推薦）
原文外掛簡介
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.
What can you automate with this WordPress webhooks plugin?
Send an outgoing webhook the moment something happens on your site — a new user registers, a post is published, a WooCommerce order is placed, a form is submitted, and dozens of other events across the plugins you already run.
Generate a secure incoming action URL that Zapier, Make (Integromat), Pabbly Connect, n8n, a form plugin, a mobile app, or any custom script can POST data to, so WordPress can create posts, create users, update memberships, and more — automatically.
Connect WordPress to virtually any platform that speaks webhooks and JSON: CRMs, Slack, Discord, spreadsheets, email marketing tools, and custom internal systems.
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.
Why use RT Connect Webhooks?
No-code automation — set up outgoing webhooks and incoming action URLs entirely from a clean, modern admin screen. No shortcodes, no functions.php edits required.
Two-way webhooks — most webhook plugins only send data out. RT Connect Webhooks also lets external services send data in to create WordPress content.
Built for real integrations — configurable HTTP method, request format, authentication, and headers mean it can talk to almost any third-party API, not just a fixed set of partners.
Transparent logging — every request and response is logged, with a one-click “Test” button so you’re never guessing whether a webhook actually fired.
Developer-friendly — clean REST API, PHP filters, and action hooks so agencies and developers can extend it for client projects.
Outgoing Webhooks (Triggers) — its own “Outgoing Webhooks” tab
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:
Forms: Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Formidable Forms, Forminator, Ninja Forms, HappyForms, Newsletter, Elementor Pro Forms
E-commerce & Payments: WooCommerce, Easy Digital Downloads (customers, downloads, payments, licensing, subscriptions), GiveWP, WP Simple Pay
Membership & LMS: Paid Memberships Pro, Paid Member Subscriptions, MemberPress, LearnDash (course/lesson/quiz/topic completion), Profile Builder
Marketing & Support: FluentCRM, Fluent Support, AffiliateWP, WP Fusion
Site Health: Broken Link Checker, Amelia bookings, bbPress topics
For every outgoing webhook you can configure:
HTTP method — POST, GET, PUT, PATCH, or DELETE
Request format — JSON, form URL-encoded, or XML
Authentication — none, API key (custom header), Bearer token, or Basic Auth
Payload signing — optional HMAC-SHA256 signature via a shared secret, sent as an X-Webhook-Signature header, so the receiving service can verify the request really came from your site
Custom headers, request timeout, and automatic retry count on failed delivery
One-click Test — fire a sample payload at the webhook and see the response instantly, without waiting for a real event
Incoming Actions (Receive Data) — its own “Incoming Actions” tab
Flip 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:
WordPress Core: create/update/delete/search users, create/update/delete/search posts, create/update/delete comments, send an email, create a taxonomy term, or fire your own custom hook
LearnDash: complete a course or lesson, enroll or remove a user from a course
Paid Memberships Pro: add, remove, or cancel a user’s membership level
Profile Builder: approve/unapprove a user, confirm a user’s email
FluentCRM: add a contact to a list or tag
Easy Digital Downloads: full customer, discount, download, and payment CRUD, plus license (create/update/delete/renew) and subscription (create/update/delete) management when EDD Software Licensing / EDD Recurring are active
Each incoming action can require its own auth token, so only requests that know the secret are accepted.
Logging & Troubleshooting — its own “Logs” tab
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.
Built for Developers
REST API at /wp-json/rtcw/v1/ for managing webhooks, incoming actions, and logs programmatically
rtcw_payload filter to modify an outgoing payload before it’s sent
rtcw_event_dispatched action that fires after an event has been sent to all matching webhooks
RTCW_Webhooks::manual_trigger( $event, $data ) to fire a webhook event from your own PHP code
Admin UI built entirely on WordPress’s own @wordpress/components React library, so it looks and feels native to WordPress
Common Use Cases
Send a webhook to Zapier or Make whenever a new WordPress user signs up
Notify Slack, Discord, or a CRM when a WooCommerce order is placed
Create a WordPress post automatically from a Google Sheets row, Airtable record, or form submission
Sync new WordPress users into an email marketing tool or CRM
Trigger your own custom PHP logic from any external event without writing a REST controller from scratch
Developer Notes
All 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 webhooks
POST /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 webhook
DELETE /wp-json/rtcw/v1/webhooks/{id} — delete an outgoing webhook
POST /wp-json/rtcw/v1/webhooks/{id}/test — send a one-off test payload
GET /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 log
GET /wp-json/rtcw/v1/incoming-actions — list incoming actions
POST /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 action
DELETE /wp-json/rtcw/v1/incoming-actions/{id} — delete an incoming action
GET /wp-json/rtcw/v1/incoming-action-types — list available incoming action types
POST /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)
