Description: Simple Webhook to WordPress XML-RPC gateway.
|Author:||Yann Dubois (profile at wordpress.org)|
|WordPress version required:||2.9|
|WordPress version tested:||3.1.4|
|Added to WordPress repository:||29-04-2011|
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|Total downloads:||1 619|
Click to start download
Implement incoming Webhooks in WordPress
This plugin implements a simple gateway to transform webhook calls into regular XML-RPC calls.
WordPress has a very comprehensive XML-RPC API. This gateway will automatically accept webhook calls and convert them into XML-RPC.
It listen to Webhooks to trigger XML-RPC methods in WordPress.
It provides a simple short /webhook URL for triggering WordPress events.
From then on you can use the well-known and well-documented native WordPress XMLRPC API to respond to webhooks and implement needed features in your plugins and custom functions.
The incoming webhook POST data payload will be transferred as-is to the XML-RPC method. It should be XML for it to work well.
If you are using pretty permalinks:
If you are not using permalinks, you need to call the long full url:
misc.method with any XML-RPC method, either WordPress built-in, or your own, or from a third-party plugin.
This gateway has successfully been used to listen to Shopify webhooks to trigger WordPress events (such as upgrade user status when a purchase has been completed).
Drop me a line on my YD Webhook to XML-RPC plugin support site to report bugs, ask for specific feature or improvement, or just tell me how you're using it.
Where should I ask questions?
I will answer only on that page so that all users can benefit from the answer.
So please come back to see the answer or subscribe to that page’s post comments.
Puis-je poser des questions et avoir des docs en français ?
Oui, l’auteur est français.
(“but alors… you are French?”)
What is your e-mail address?
It is mentioned in the comments at the top of the main plugin file. However, please prefer comments on the plugin page (as indicated above) for all non-private matters.
- Initial beta release