Generic Webhook — Connect it to MokonyxSocial

Details
Category: MokonyxSocial
  • Applicable Software: MokonyxSocial
  • Min Version Number: 01.03.00 and later
  • Max Version Number: Not Applicable

MokonyxSocial sends your Joomla content as an HTTP POST with a JSON payload to any URL you give it. It fires one POST per publish, and your endpoint decides what to do next — relay it to Slack, Discord, Zapier, Make, or your own app.

What you need

  • A publicly reachable HTTPS endpoint that accepts POST requests.
  • The exact webhook URL for it, including any token or query string it needs.

Get your credentials

Webhook URL webhook_url (required)

This is the full URL MokonyxSocial POSTs your JSON payload to. Where you find it depends on what's receiving it:

  • Slack: create an Incoming Webhook at https://api.slack.com/apps → your app → Incoming Webhooks → Add New Webhook to Workspace, then copy the https://hooks.slack.com/services/... URL.
  • Discord: in a channel, go to Edit Channel → Integrations → Webhooks → New Webhook → Copy Webhook URL.
  • Zapier: build a Zap starting with Webhooks by Zapier → Catch Hook; it hands you a https://hooks.zapier.com/... URL.
  • Make (Integromat): add a Custom webhook module to get a https://hook..make.com/... URL.
  • Your own app: whatever route you set up to catch POSTs.

Copy the whole URL, including any token or query parameters.

Set it up in MokonyxSocial

  1. In Joomla admin, go to Components → MokonyxSocial → Services → New.
  2. Choose Webhook.
  3. Enter the credentials above.
  4. Click Send Test to verify, then Save & Close and make sure it's Published.

Verify

Once Send Test succeeds, check the receiving side — the Slack/Discord channel, your Zapier/Make history, or your app's logs — for the test payload. Then publish a Joomla article and confirm a POST comes through.

Troubleshooting

  • 404 Not Found: the URL is wrong or the webhook was regenerated — grab a fresh one from the receiver.
  • 401/403: your endpoint wants a token you left out — paste the complete URL with its secret.
  • Timeout / connection refused: the endpoint isn't reachable or isn't HTTPS — make sure it's public and accepts POST.
  • 400 / payload rejected: the receiver expects a specific shape (Slack wants {"text": ...}) — put Zapier/Make in front to transform it, or adjust your receiver.

Notes & limits

  • The body is JSON sent via HTTP POST — your receiver has to parse it.
  • There's no guaranteed retry or queue, so if your endpoint is down that post can be missed unless you buffer it.
  • Use HTTPS and put a secret in the URL so strangers can't spam your endpoint.
Hits: 4