For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/reference/webhooks.md.
  • English

      • Webhooks

      Clickmax has two kinds of webhook: inbound (in), which receives events from an external platform, and outbound (out), which sends an event from Clickmax to an external URL when a trigger fires.

      Role required: authenticated workspace member. Webhooks are managed in the Integrations area.

      Direction

      TypeDirectionWhat it is
      inExternal platform → ClickmaxReceives data through a dedicated URL (https://webhooks.<your-domain>/<slug>), validated by token.
      outClickmax → external platformFires a POST to the configured URL when the trigger occurs.

      Inbound platforms

      Values accepted when creating an inbound webhook.

      PlatformIdentifier
      ActiveCampaignactivecampaign
      Asaasasaas
      Braipbraip
      CartPandacartpanda
      Eduzzeduzz
      Greenngreenn
      Digital Manager Guruguru
      Hotmarthotmart
      HotWebinarhotwebinar
      Hublahubla
      Kiwifykiwify
      Kommokommo
      ManyChatmanychat
      Monetizzemonetizze
      Pagar.mepagarme
      PerfectPayperfectpay
      StartBetstartbet
      Stripestripe
      Tictoticto
      TMB (Tem Mais no Boleto)tmb
      VStagevstage
      Vunelvunel
      WebinarKitwebinarkit
      Yampiyampi

      Outbound platforms

      Destinations accepted when creating an outbound webhook.

      PlatformIdentifier
      ActiveCampaignactivecampaignout
      Basecampbasecamp
      Calendlycalendly
      Circlecircle
      Clickmax (internal funnel/tag)clickmax
      Discorddiscord
      Google Drivedrive
      Dropboxdropbox
      Eventbriteeventbrite
      Google Sheetsgooglesheets
      HubSpothubspot
      Intercomintercom
      JivoChatjivochat
      Makemake
      n8nn8n
      Nibonibo
      Nota do Infoprodutornotadoinfoprodutor
      Notazznotazz
      Notionnotion
      Outsideroutsider
      Pipedrivepipedrive
      PipeRunpiperun
      QuickBooksquickbooks
      RD Stationrdstation
      Shopifyshopify
      Slackslack
      Somos BIUsomosbiu
      UTMifyutmify
      WooCommercewoocommerce
      Zapierzapier
      Zendeskzendesk
      Zoom Webinarzoomwebinar

      Triggers

      Events that fire an outbound webhook (the trigger field).

      TriggerWhen it fires
      ABANDONED_CARTCart abandoned
      CHARGEBACK_REQUESTEDChargeback requested
      FUNNEL_CREATEDFunnel created
      FUNNEL_DELETEDFunnel deleted
      FUNNEL_EDITEDFunnel edited
      LEAD_CAPTUREDLead captured
      LEAD_CREATEDLead created
      PAGE_CREATEDPage created
      PAGE_DELETEDPage deleted
      PAGE_EDITEDPage edited
      PIX_OR_BOLETO_EXPIRED_OR_OVERDUEPix or Boleto expired/overdue
      PROJECT_CREATEDProject created
      PROJECT_DELETEDProject deleted
      PROJECT_EDITEDProject edited
      REFUND_MADERefund issued
      REFUSED_CARDCard declined on the charge (once per attempt)
      SALE_CANCELLEDSale cancelled
      SALE_MADESale completed
      SUBSCRIPTION_CANCELLEDSubscription cancelled
      SUBSCRIPTION_STARTEDSubscription started
      TAG_ADDEDTag added
      TAG_REMOVEDTag removed
      TRANSACTION_FAILEDTransaction failed

      Card declined vs transaction failed

      REFUSED_CARD fires once per payment attempt in which the card was sent to the charge and refused. A second attempt by the buyer with the same card, minutes later, is a new refusal and fires again.

      A purchase that never reaches the charge — required card missing, product out of stock, pending seller account, missing delivery address — is not a card refusal: it only fires TRANSACTION_FAILED. Pix and Boleto failures also use TRANSACTION_FAILED only.

      When SUBSCRIPTION_CANCELLED fires

      On any subscription cancellation, whatever its origin: cancelled by the buyer, by you or by support, the automatic cancellation for missed payment after the tolerance period, and the cancellation that comes with a refund.

      A subscription that reached the end of its contracted duration (the plan's last scheduled charge) is not a cancellation and does not fire this trigger.

      Record statuses

      Every delivery creates a record with one of these statuses.

      StatusMeaningApplies to
      PROCESSINGReceived/sent, being processedinbound and outbound
      COMPLETEDProcessed successfullyinbound and outbound
      DELAYEDDelivery postponed for a retryoutbound only
      FAILEDFailed (the provider may retry)inbound and outbound

      If it didn't work

      • The platform gets a 401 when sending inbound: the webhook is inactive, has been deleted, or the token/signature does not match — see Error codes.
      • An outbound webhook never reaches its destination: check the record status and the endpoint's response in Error codes.
      • General questions about integrations: see the Frequently asked questions.