Generic Webhook Service

Details
Category: Services
  • Applicable Software: MokonyxSocial
  • Min Version Number: 01.03.12
  • Max Version Number: Not Applicable

Why Use a Webhook

Not every destination has a dedicated connector, and some workflows are entirely your own. The webhook service is the escape hatch: because the payload is standard HTTP, you can route article data into virtually any system that can receive a request — an automation platform, a custom API, a CRM, or your own logging and analytics tooling.

How It Works

When an article is published on your Mokonyx site, MokonyxSocial sends a request to the webhook URL you configure. The payload carries the article data — title, URL, introtext, fulltext, image URL, category, author, and publish date — so the receiving system has everything it needs to act on the new content.

Credentials

  • Webhook URL — The endpoint that receives the article data.
  • HTTP Method — POST or PUT.
  • Authentication — None, Bearer Token, or Basic Auth.
  • Bearer Token (if Bearer auth) — Sent as an Authorization: Bearer header.
  • Username / Password (if Basic auth) — Sent as a Basic Auth header.
  • Content Type — application/json or application/x-www-form-urlencoded.

Setup

  1. Create or copy the endpoint URL from the service that will receive the data (your automation platform or your own API).
  2. In Joomla, go to Components, Mokonyx Social, and add a Generic Webhook service.
  3. Paste the Webhook URL, pick the HTTP method and content type, and set any authentication the endpoint requires.
  4. Save and publish the service, then publish a test article to confirm the payload arrives.

Payload and Use Cases

  • Zapier or IFTTT triggers for custom workflows
  • n8n or Make automations
  • Custom CMS or CRM integrations
  • Analytics or logging systems

Tips for Best Results

  • Match the content type — Choose application/json for most modern APIs and automation tools; use form-encoded only when the endpoint specifically expects it.
  • Secure the endpoint — If your receiver supports it, set Bearer or Basic authentication so only MokonyxSocial can post to the URL.
  • Test with a real publish — Publish a test article and inspect what your endpoint receives before relying on the automation in production.

Troubleshooting

If data doesn't arrive, verify the Webhook URL is reachable from the public internet and that the HTTP method and content type match what the endpoint expects. If the request is rejected, check that the authentication type and credentials line up with the receiving system's requirements.

Need Help?

Field names and available options may change between MokonyxSocial versions. If you need help building an automation or configuring authentication, the Moko Consulting support team is glad to help — just reach out.

Hits: 78