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/features/integrations/outgoing-webhooks.md.
  • English

      • Outgoing integrations (webhooks)

      While checkout integrations bring data into Clickmax, an outgoing integration does the opposite: when something happens in your account (a sale, a contact created, a tag applied), Clickmax sends that event to a URL you choose — Zapier, Make, n8n, Slack, your own system, and so on.

      Workspace role: Owner, Admin, Editor, or Collaborator.

      Several triggers in the same integration

      One integration can listen to as many events as you want. When creating or editing, the triggers field accepts multiple selection, and every selected event is sent to the same URL, with the same token and the same credentials.

      This replaces the previous behavior, where each integration listened to a single event — reacting to five events meant creating five integrations, each with its own history and token.

      Select at least one trigger. An integration with no trigger stays active but never fires.

      Available triggers per platform

      Most platforms (Zapier, Make, n8n, Slack, Notion, RD Station…) accept every event, because they simply forward whatever they receive.

      Some platforms have their own translation and therefore accept only the events they know how to interpret:

      PlatformAccepted triggers
      ActiveCampaignContact created, Contact captured, Tag applied, Tag removed
      UTMify, Notazz, Nota do Infoprodutor, Somos BiuPurchase completed, Purchase canceled, Refund issued, Chargeback requested

      If you pick an event the platform does not accept, Clickmax tells you right away instead of saving a setup that would never deliver anything.

      What ActiveCampaign requires for each event group

      ActiveCampaign's two event groups go to different places in your account, and each one needs its own setup. A single integration can listen to both — and then it needs both.

      If you selectYou must provide
      Contact created, Contact capturedthe contact list and the funnel
      Tag applied, Tag removedthe tag

      Miss any of these and Clickmax will not let you save. That is on purpose: without them the integration would sit there active without ever delivering anything, and with no visible error.

      A tag-only integration does not ask for a list — the list is only used when the event creates or captures a contact.

      Contacts without an email are not sent to ActiveCampaign

      ActiveCampaign identifies every contact by email. Contacts that exist in Clickmax with only a phone number or Instagram handle are not sent — neither on contact events nor on tag events. This is not an error: the delivery is simply skipped and does not show up in History.

      View and edit an integration

      On the integration card, click the edit icon to open the detail page. It has two tabs:

      • Settings — name, destination URL, triggers, credentials, and enable/disable.
      • History — every delivery made so far.

      Changes apply to upcoming events; deliveries already recorded are not changed.

      Credentials

      For security, Clickmax never shows saved credentials back (API keys, tokens). On the edit screen, credential fields appear empty, indicating only which ones are already configured.

      • Leave blank to keep the current credential.
      • Type a new value to replace it.

      Delivery history

      The History tab lists each delivery with the trigger that produced it, the date, and the status. The trigger column is what lets you tell deliveries apart when the integration listens to several events.

      Clicking the magnifier on a delivery shows:

      • the request Clickmax sent (body and headers);
      • the destination platform's response, per attempt — including the status code and error message when the delivery failed.

      That is what lets you find out why a delivery failed, instead of only seeing that it did.

      Resend a delivery

      Every history row has a Resend action. Use it when the failure was on the other platform's side (instability, expired credential, URL temporarily down) and you have already fixed the problem.

      Resending sends exactly the same content already recorded — nothing is recalculated. Each resend is added to the history as a new attempt, so the trail stays complete.

      The button responds immediately and the delivery happens right after, asynchronously: the row moves to "processing" and the result shows up once the platform answers.

      When an integration is disabled automatically

      After 15 consecutive failed attempts, Clickmax disables the integration to stop hammering a destination that does not answer. This applies to the whole integration, not per trigger, because the URL and credentials are shared by all of its events.

      Fix the destination, re-enable the integration on the Settings tab, and use Resend on the failed deliveries if you want to recover what was missed.