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/guides/webhooks-in-practice.md.
  • English

      • Inbound and outbound webhooks: when do I use each?

      A webhook is an automatic notification between systems: when something happens, one tells the other straight away. The only thing you have to get right is the direction.

      Before you start

      • Role: Owner, Admin or Editor.
      • On the other side there has to be a system capable of sending or receiving those calls.

      The direction decides everything

      TypeWho notifies whomUse when
      InboundExternal system → ClickmaxAn external checkout platform needs to record sales here
      OutboundClickmax → external systemYour tool needs to know that something happened here

      Rule of thumb: inbound brings data in, outbound takes data out.

      Inbound webhook

      You create the integration, enter the token of the platform that will be sending, and use the generated address on the other side. In Explore Integrations this is the Receive data from another platform route, and the address to copy is shown as the Webhook URL. It is the mechanism behind centralise external sales.

      The step by step is in the FAQ on setting up an inbound webhook (Portuguese).

      Outbound webhook

      You enter the external system's URL and choose which events trigger the send — the Create outbound webhook route in Explore Integrations. It is what lets you connect Zapier, Make or n8n and grant access in an external members area.

      The step by step is in the FAQ on setting up an outbound webhook (Portuguese).

      Choose your events deliberately

      Only subscribe to the events you actually need. Subscribing to everything floods the destination with irrelevant calls and makes it harder to find the one that matters when something breaks.

      The available events and the shape of the data are in the webhooks reference and the events reference (both Portuguese).

      Test before you depend on it

      Fire a real event and confirm it arrives on the other side. Webhooks fail silently: nothing on screen tells you the integration has stopped.

      Plan for failure

      Systems go down. Decide how you will notice that the calls have stopped and what you do manually in the meantime — especially if the webhook is what grants access to a paying customer.

      If it didn't work

      • The destination received nothing: check the URL and the format in the webhooks reference (Portuguese).
      • The call returns an error: see the error codes (Portuguese).
      • It arrives but nothing happens: the format is probably not what the system on the other side expects.