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/yever.md.
  • English

      • Integrate Yever

      Create an inbound integration in Clickmax, paste your Yever Api Token, and register the generated URL in Yever's webhooks. From then on every event carrying an email creates or updates a contact (tagged yever), and paid orders become sales in Clickmax.

      Before you start

      • Workspace role: Owner, Admin, Editor or Collaborator. Finance, Guest and Attendant have no access to Integrations.
      • Plan:
      • From your Yever account you need the Api Token (Configuração > API > Novo token), which Clickmax uses to list your products in triggers. It is shown only once, when you create it — generate a new one if you lose it.
      • The webhook Token is generated by Yever itself when you register the webhook, so it only exists after step 6.

      Step by step

      1. In Clickmax, open Integrations and select the Yever card.
      2. In another tab, go to Yever and sign in.
      3. In Yever, go to Configuração > API > Novo token, copy the generated token and paste it into the Api Token field in Clickmax.
      4. Name the integration and click Create integration. Leave the Token field empty for now.
      5. Clickmax generates a webhook URL. Copy it.
      6. In Yever, go to Configuração > Webhooks > Novo webhook and paste the copied URL.
      7. Select the events you want to receive: Pedidos (orders), Carrinho abandonado (abandoned cart), Assinatura (subscription) and Cashback. Inside Pedidos, also enable Pedido pago — webhooks created before that event existed are not subscribed to it automatically.
      8. Copy the token Yever shows on the webhook screen, return to Clickmax, edit the integration and paste it into the Token field.
      9. Click Finish integration.

      What starts arriving

      Every event carrying an email creates or updates a contact tagged yever. Paid orders mark the contact as a customer and record the sale; refunds, chargebacks and cancellations are recorded as sales too. Events without the customer's email are ignored.

      Yever eventClickmax trigger
      Order createdOrder created
      Order paidOrder paid
      Order updated → refundedOrder refunded
      Order updated → charged backOrder charged back
      Order updated → canceledOrder canceled
      Order shippedOrder shipped
      Abandoned cartCart abandoned
      Subscription createdSubscription created
      Renewal succeededRenewal approved
      Renewal failedRenewal failed
      Subscription updated → activeSubscription reactivated
      Subscription updated → pausedSubscription paused
      Subscription updated → canceledSubscription canceled
      Subscription updated → finishedSubscription finished
      Cashback created / redeemed / expired / expiring / canceled / restoredOne trigger each

      Yever fires order paid and order updated on the same payment transition. Clickmax only uses order paid in that case, so your automation runs once.

      Orders with more than one product

      An order with an order bump (or several items) creates one sale in Clickmax, carrying the order total — not one sale per product. In the external sales list the main product shows a +N badge for the additional items.

      The contact history is the opposite: it gets one activity per product, each with that item's value, and the ones Yever flags as order bumps get an Order bump badge. That is where you see exactly what was purchased.

      In flows, a trigger filtered by product fires when that product is in the order — including when it came in as an order bump.

      Filtering by product

      On order and subscription triggers you can pick a product: Clickmax lists products straight from your Yever store using the Api Token. The filter matches on the product id, so renaming the product in Yever breaks nothing.

      Cashback triggers have no product filter — Yever does not include the product in those events, so they fire for any cashback.

      Abandoned cart matches on the product name

      Yever's abandoned-cart event does not include the product id, only the name. So when you filter that trigger by product, Clickmax compares on the name.

      Practical consequence: if you rename the product in Yever, the trigger stops firing — the name saved in the filter no longer matches what arrives in the webhook. When that happens, reopen the trigger, pick the product from the refreshed list and save. If you would rather not depend on that, leave the filter empty to fire for any abandoned cart.

      If it didn't work

      • I can't create the integration: Clickmax validates the Api Token on creation. If it is wrong or expired, generate a new one under Configuração > API in Yever. See the error codes.
      • No events arrive: check that the Token shown by Yever was pasted into the integration — without it Clickmax rejects the deliveries. Also check that the events are selected on the Yever webhook. See the FAQ.
      • Order paid doesn't arrive but the others do: enable Pedido pago on the webhook screen in Yever. Older webhooks are not subscribed to that event.
      • A specific event doesn't arrive: events without the customer's email are discarded (Clickmax cannot resolve the contact). See the error codes.
      • The abandoned-cart automation stopped firing: the product was probably renamed in Yever. Reopen the trigger, pick the product from the refreshed list and save.