WHMCS webhook setup sends a message to another system each time something happens in WHMCS: a new order, a paid invoice, a failed provisioning attempt, a ticket reply or a cancellation request. The destination can be a Slack or Discord channel, an automation tool such as Zapier, n8n or Make, or an HTTPS endpoint you run. Pricing starts at $199 as a one-time job. The traffic here goes one way, out of WHMCS. To change how WHMCS itself behaves, see custom hooks development; and when another platform must pull data from WHMCS or write changes into it, API integration is the right page.
Start with what WHMCS already has
WHMCS ships a Notifications feature at Configuration > System Settings > Notifications. You build rules from an event category (Ticket, Invoice, Order, Service or Domain), add conditions such as department, priority, client group or order total, and send the result to Slack or email. If that covers your need, we set up the rules and the Slack connection and the job is done at the low end of the price. Beyond Slack and email, WHMCS has no screen that posts events to an arbitrary URL, so everything else is built with hooks.
Events we usually wire up
| Event | WHMCS hook point | Typical destination |
|---|---|---|
| Order placed | AfterShoppingCartCheckout | Sales channel |
| Order paid | OrderPaid | Sales channel or CRM automation |
| Invoice paid | InvoicePaid | Zapier or n8n flow for bookkeeping |
| Service set up or failed | AfterModuleCreate, AfterModuleCreateFailed | Operations channel |
| Service suspended or terminated | AfterModuleSuspend, AfterModuleTerminate | Operations channel |
| Ticket opened or customer replied | TicketOpen, TicketUserReply | Support channel on Discord or Slack |
| Cancellation request | CancellationRequest | Retention workflow |
| Order flagged as fraud | FraudOrder | Private admin channel |
| Domain transfer failed | DomainTransferFailed | Domains queue |
Payloads that are safe to send
- JSON with the event name, a unique event ID, a timestamp and the related WHMCS IDs
- Only the fields the receiver needs; passwords, card details and full addresses stay inside WHMCS
- An admin area link in chat messages, so staff can open the order or ticket in one click
- An HMAC-SHA256 signature header computed with a shared secret, so your endpoint can reject forged requests
- The event ID repeated on retries, so the receiver can ignore a duplicate
Delivery that does not slow checkout
A webhook call made in the middle of checkout must not leave the customer waiting on a slow third party. Each send uses a short timeout. When a destination is down or answers with an error, the message goes into a queue table and a cron-driven hook retries it on later runs, with a delivery log you can read in the admin area. After repeated failures you get one email instead of a stream of silent errors.
Destinations
- Slack: WHMCS's own Slack provider for simple rules, or an incoming webhook for formatted messages
- Discord: a channel webhook per team, with embeds for orders and tickets
- Zapier, Make and n8n: a catch-hook trigger in each tool, tested end to end with one sample workflow
- Your own endpoint: signed JSON, with sample verification code for PHP or Node.js
If you would rather manage channels from a settings screen, our Multi-Channel Notifications module covers Slack, Discord, Telegram, SMS and generic webhooks, and the WHMCS Discord Bot adds two-way commands and role sync.
Versions
The hook points above exist in both WHMCS 8.13 (PHP 8.1 or newer) and 9.x (PHP 8.2 or newer). Testing happens on your exact version and PHP build.
What we ask you for
- The list of events and who should see each one
- Webhook URLs, or admin rights in Slack, Discord or the automation tool so we can create them
- Access to the WHMCS admin area and the hooks folder
Handover
You receive the hook files, an event catalogue with a sample payload for each event, the signing secret, and test messages already sent to every destination. For two weeks after handover, a message that misfires or lands in the wrong place is ours to fix at no charge.
Price guide
| Scope | One-time price |
|---|---|
| Native WHMCS Notifications rules to Slack or email, or up to five hook-based events to one destination | From $199 |
| Signed JSON to Zapier, Make, n8n or your endpoint, with retry queue and delivery log | Quoted per destination count |
| A custom notification provider so a new channel appears in WHMCS's own Notifications screen | Quoted once the channel API is reviewed |
Not covered here
- Inbound webhooks from payment providers, which belong to payment gateway integration
- Large multi-step automations built inside Zapier, Make or n8n
- Fees for Slack, Zapier, Make or n8n plans
List the events you care about on the scoping call, and we will tell you which ones WHMCS can already send without custom code.