Skip to main content

n8n Webhook & API

WhatGHL can integrate with n8n per sub-account. In the app you set where events should go (webhook URL), optional material to verify incoming requests in n8n, and an API key your workflow uses according to the n8n-nodes-whatghl setup your agency provides.

Where to configure​

  1. Sub Accounts → open the sub-account → Connection tab.
  2. Open the n8n Webhook & API card (below the GHL connection summary when connected).
  3. Fill in:
    • Webhook URL (n8n) — HTTPS endpoint of your n8n workflow (typical https://…/webhook/…).
    • HMAC key (optional) — if your workflow verifies signed callbacks, configure the same secret here and in n8n as documented for your integration.
    • API key — secret used by your n8n credentials when the WhatGHL node (or your agency’s template) asks for it. You can generate a key in the UI when available.
  4. Save n8n settings.

Treat the API key like a password; rotate it if it leaks.

Good practices​

  • Use HTTPS only for the webhook URL.
  • Prefer a dedicated n8n workflow per sub-account or clear branching so events are easy to debug.
  • After rotating the API key, update every n8n credential that used the old key.

For workflow steps and field meanings beyond this screen, follow the guidance or templates your agency or support gives you together with n8n-nodes-whatghl.