Kajabi Trigger icon

Kajabi Trigger

Starts the workflow when Kajabi events occur via webhooks

Kajabi Trigger

AI-generated

Summary

Listen for various Kajabi events via webhooks, automatically registering and deregistering the webhook with Kajabi for supported auto-registered events, and receive event payloads in the workflow when triggered.

Inputs

  • event (required) — The Kajabi event to listen for: Any Webhook (manual setup), Form Submission, Order Created, Payment Succeeded, Purchase, Tag Added, or Tag Removed.
  • authentication — Authentication method used for auto-registered events: OAuth2 or API Key (shown only for auto-registered events).
  • tagFilter — Optional Kajabi tag ID to filter Tag Added or Tag Removed events; leave empty to receive all tags.
  • formFilter — Optional Kajabi form ID to filter Form Submission events; leave empty to receive all forms.
  • offerFilter — Optional Kajabi offer ID to filter Purchase events; leave empty to receive all offers.
  • options.allowedIps — Optional comma-separated IPv4 addresses or CIDR ranges to restrict which IPs can POST to the webhook; IPv6 not supported.
  • options.flattenResponse — Option to flatten nested webhook payload data into dot notation keys; enabled by default.
  • options.includeRawBody — Option to include the raw webhook request body in the output.
  • options.sharedSecret — Optional shared secret to require as X-Kajabi-Token header or ?token= query parameter for additional webhook security.
  • options.trustForwardedFor — Whether to trust X-Forwarded-For header for client IP detection when restricting by IP; enable only behind trusted reverse proxies.

Output shape

A single webhook payload object representing the Kajabi event data that triggered the webhook, optionally flattened and/or including the raw request body.

For auto-registered events (all except 'Any Webhook'), the node automatically registers and deregisters the webhook URL in Kajabi when the workflow is activated/deactivated. Manual webhook setup is required for 'Any Webhook' events. Filtering by tag, form, or offer ID limits events accordingly. IP allowlisting and token-based validation can be enabled for security. The webhook rejects requests from disallowed IPs with HTTP 403 and invalid tokens with HTTP 401 responses.

Examples

Example 1: Trigger workflow on Kajabi tag added to contact

Set the event to 'Tag Added' and optionally provide a Tag Filter to listen for a specific tag ID. Authenticate using OAuth2 or API Key.

Example 2: Trigger workflow on Kajabi form submission filtered by form ID

Set the event to 'Form Submission', specify a Form Filter ID, and provide appropriate authentication. The webhook is auto-registered in Kajabi.

Example 3: Receive any Kajabi webhook manually

Set the event to 'Any Webhook'. Copy the generated webhook URL and manually configure it in Kajabi to send arbitrary webhook payloads to the workflow. No auto-registration occurs.

Links

Discussion