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/automations/branch-by-purchase.md.
  • English

      • How do I branch an automation by what the contact purchased?

      Add a condition from the Payment group inside the Router (or Condition) step and branch the automation by what the contact has already bought — a specific product, an offer, how many purchases they made or how much they spent. This is how you deliver a bonus only to people who bought the advanced course, or send an upgrade offer only to one-time buyers.

      Until now the only way was to build a segment in the CRM and point the automation at it — and a segment only refreshes once a day. Payment conditions check the purchase at the moment the contact reaches the Router.

      Role: any member with edit access to the workspace.

      Before you start

      • An automation, published or in edit mode, with at least one trigger.
      • Contacts need an email address on file — read the Contacts without an email never match section below before you build the flow.

      Step by step

      1. On the automation canvas, click the + where the split should go and choose Router.

      2. On path 1, give it a name that describes the intent (for example, Bought the advanced course) and click Add condition.

      3. In the left column of the menu, open the Payment tab.

      4. Pick the condition:

        ConditionMatches on...
        Purchased productthe product the contact bought
        Purchased offera specific offer inside a product
        Product namethe text of the product name
        Number of purchasestotal approved purchases
        Last purchase datewhen they last bought
        Last purchase valuethe amount of the most recent purchase
        Lifetime value (LTV)everything they have spent
        Average order valueaverage amount per purchase
        Offer typethe offer category (Course, Mentorship, Event…)
        Offer currencythe currency the purchase was made in

      5. For Purchased product and Purchased offer, the field opens a searchable picker — type to filter and select as many items as you need. The operators are is one of and is not one of, so a single path can cover a whole list of products.

      6. Repeat on the other paths. Use Add path to create more (up to 10).

      7. Connect each path's output to the step that should follow, and also the Otherwise output — that is where contacts that match no path come out.

      Contacts without an email never match

      A purchase is matched to a contact by email: the email used at checkout has to be the same one on the contact record. This is the same rule the CRM payment filters follow.

      It matters more in an automation than in a segment, because contacts coming in through WhatsApp, Instagram or Telegram usually arrive without an email. For those contacts every Payment condition is false — they leave through the Otherwise output even if they did buy.

      If your flow starts on a messaging channel, ask for the email before the split, or place the Payment condition only in the part of the flow where the email is already filled in.

      "Fewer than N purchases" does not catch people who never bought

      The conditions that count or add up — Number of purchases, Lifetime value (LTV) and Average order value — only look at contacts that have at least one purchase on record.

      In practice: Number of purchases with less than 3 matches people who bought once or twice, and does not match people who never bought. It feels counter-intuitive, but it is the same behaviour as the CRM filters.

      To reach people who never bought, use one of these:

      • Purchased product with is not one of and the list of products you care about;
      • the Is customer condition, in the general contact fields, set to No.

      If it did not work

      • Every contact comes out of Otherwise: it is almost always the email. Open a contact you know has bought and check that their email matches the checkout one.
      • The automation will not publish: the builder flags a condition left without a value — in Purchased product and Purchased offer, an empty selection counts as no value.
      • The contact took the wrong path: with One path, the first matching path wins, top to bottom. Reorder the paths or switch to Multiple paths.
      • The product is missing from the search: the list shows products in your workspace; a deleted product does not appear. If it was already selected in a saved condition the selection still applies, and the picker marks the item as removed.