# WHMCS Webhook Integration

> WHMCS events delivered to Slack, Discord, Zapier, n8n, Make or your own endpoint, with signed payloads and retries.

Outbound WHMCS webhooks for orders, payments, provisioning, tickets and cancellations: event map, signed JSON payloads, retry queue and delivery log. One-time price from $199.

- **Price:** Starting at $199
- **Billing:** One-time, fixed scope
- **Category:** Custom Development
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-webhook-setup
- **Last updated:** 2026-11-05

## Overview

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](/services/whmcs-hooks-development); and when another platform must pull data from WHMCS or write changes into it, [API integration](/services/whmcs-api-integration) is the right page.

## Start with what WHMCS already has

WHMCS ships a Notifications feature at Configuration &gt; System Settings &gt; 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

EventWHMCS hook pointTypical destinationOrder placedAfterShoppingCartCheckoutSales channelOrder paidOrderPaidSales channel or CRM automationInvoice paidInvoicePaidZapier or n8n flow for bookkeepingService set up or failedAfterModuleCreate, AfterModuleCreateFailedOperations channelService suspended or terminatedAfterModuleSuspend, AfterModuleTerminateOperations channelTicket opened or customer repliedTicketOpen, TicketUserReplySupport channel on Discord or SlackCancellation requestCancellationRequestRetention workflowOrder flagged as fraudFraudOrderPrivate admin channelDomain transfer failedDomainTransferFailedDomains 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](/modules/whmcs-notifications) covers Slack, Discord, Telegram, SMS and generic webhooks, and the [WHMCS Discord Bot](/modules/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

ScopeOne-time priceNative WHMCS Notifications rules to Slack or email, or up to five hook-based events to one destinationFrom $199Signed JSON to Zapier, Make, n8n or your endpoint, with retry queue and delivery logQuoted per destination countA custom notification provider so a new channel appears in WHMCS's own Notifications screenQuoted once the channel API is reviewed

## Not covered here

- Inbound webhooks from payment providers, which belong to [payment gateway integration](/services/whmcs-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.

## What's included

- Setup of WHMCS Notifications rules for Slack and email where they are enough
- Hook-based webhooks for orders, payments, provisioning, tickets, cancellations and fraud flags
- Event map listing each WHMCS hook point and its destination
- JSON payloads with event ID, timestamp and only the fields the receiver needs
- HMAC-SHA256 signatures so receivers can reject forged requests
- Short timeouts so checkout never waits on a third party
- Retry queue processed by cron, with a delivery log
- Slack, Discord, Zapier, Make, n8n and custom endpoint destinations
- Sample payloads and verification code handed over
- 14-day correction window after delivery

## Business outcomes

- Sales, support and operations hear about events as they happen instead of on the next login
- Failed provisioning and fraud flags reach a person straight away
- A destination outage delays messages rather than losing them
- Customer data shared with third parties stays limited to what each one needs
- Automations in Zapier, Make or n8n start from reliable WHMCS events

## Frequently asked questions

### Does WHMCS support webhooks natively?

Partly. The Notifications feature sends rule-based alerts to Slack and email, but posting events to other URLs needs hooks or a notification module.

### Which WHMCS events can trigger a webhook?

Any event with a hook point, which covers orders, invoices, payments, provisioning results, tickets, domains, clients and cron runs. The Hook Index on developers.whmcs.com lists them all.

### Will webhooks slow down my checkout?

Not with short timeouts and a retry queue. If a destination is slow or down, the message waits in the queue and the customer's checkout continues normally.

### Can I send WHMCS events to Zapier or n8n?

Yes. Each tool has a webhook trigger that accepts our JSON payloads, and we test one sample workflow in each tool you use.

### How does my endpoint know a request really came from WHMCS?

Every request carries an HMAC-SHA256 signature made with a secret only you and WHMCS know. Your endpoint recalculates it and rejects any request where the values differ.

### Can I pay in crypto?

Yes, through NOWPayments. Stripe (cards, Apple Pay, Google Pay) and PayPal are also accepted.
