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/zapier-make-n8n.md.
  • English

      • How do I connect Clickmax to Zapier, Make or n8n?

      Automation tools like Zapier, Make and n8n wire together systems that know nothing about each other. The route is always the same: Clickmax fires an outbound webhook and the tool reacts.

      Before you start

      • Role: Owner, Admin or Editor.
      • You need an account on the tool you choose.
      • It is worth understanding webhook direction first: webhooks in practice.

      1. Start on the tool's side

      Create the scenario and choose the webhook trigger. The tool generates a URL — that is what you will enter in Clickmax.

      Doing it in this order stops you configuring the webhook here with nowhere to send it.

      2. Set up the outbound webhook

      In Explore Integrations, take the Create outbound webhook route, enter the URL the tool generated in the Webhook URL field and choose the events. The step by step is in the FAQ on setting up an outbound webhook (Portuguese).

      3. Fire a real event to map the fields

      The tool needs to receive at least one real call before it can recognise the shape of the data. Make it happen for real — capture a lead, run a test purchase — rather than trying to fill the fields in by hand.

      The format is in the webhooks reference (Portuguese).

      4. Build the rest of the flow

      With the data mapped, build the actions: add a row to a spreadsheet, post to the team chat, create a record in another system.

      5. Handle the errors

      Set up failure notifications in the tool itself. Without them the automation stops and you only find out when somebody complains.

      Watch your consumption too: these tools charge per run, and a very frequent event can generate unexpected cost. Only subscribe to what you need.

      6. Document it

      Write down what each scenario does and which events it consumes. A forgotten automation still running is a guaranteed source of inexplicable behaviour months later.

      If it didn't work

      • The tool receives nothing: confirm the URL, and that the event really happened.
      • The fields come through empty: fire a real event and remap.
      • The scenario stopped on its own: check the limits and errors in the tool itself.