Hotmart Trigger icon

Hotmart Trigger

Recebe eventos da Hotmart via webhooks

Overview

The Hotmart Trigger node listens for webhook events sent by the Hotmart platform, which is widely used for digital product sales and subscription management. It processes various types of purchase and subscription-related events such as approved purchases, completed purchases, cancellations, refunds, chargebacks, boleto (bank slip) prints, disputes, expirations, delays, subscription cancellations, plan changes, billing date updates, and user access events.

This node is beneficial for automating workflows based on real-time sales and subscription activities in Hotmart. For example, you can use it to:

  • Send personalized emails or notifications when a purchase is approved or completed.
  • Update CRM records when a subscription is canceled or changed.
  • Trigger different automation paths depending on whether a payment was made via PIX, boleto, or credit card.
  • Separate handling of new subscriptions versus renewals for targeted marketing.

The node supports three trigger modes that define how incoming events are routed through workflow outputs:

  • Standard: Single output; filters events by type.
  • Smart: Multiple outputs, one per event type, allowing branching without condition nodes.
  • Super Smart: Further separates single purchases, new subscriptions, and renewals into distinct outputs for more granular control.

Properties

Name Meaning
Como configurar este webhook na Hotmart? Clique aqui Notice with a link to Hotmart's official webhook setup documentation.
Modo de Trigger Defines how the node processes incoming data. Options: Padrão (Uma Saída) (Standard - one output), Smart (Múltiplas Saídas) (Smart - multiple outputs by event), Super Smart (Separa Assinaturas) (Super Smart - separates subscriptions).
Evento (Only for Standard mode) Selects the specific Hotmart event to process, e.g., "Compra Aprovada" (Purchase Approved), "Assinatura Cancelada" (Subscription Canceled), or "Todos" (All events).
Usar Token de Verificação Boolean to enable validation of the verification token sent in the X-HOTMART-HOTTOK header to ensure webhook authenticity.
Token de Verificação The expected verification token value to validate incoming webhook requests against. Required if "Usar Token de Verificação" is enabled.
Personalizar Nomes das Saídas Boolean to enable custom display names for the node's outputs (only for Smart and Super Smart modes).
Nome alternativo para: [EVENT_NAME] Custom display names for each event output, e.g., "Aprovada" for Purchase Approved, "Reembolso" for Purchase Refunded, etc. Separate sets exist for Smart and Super Smart modes, allowing tailored output labels for clarity.

Output

The node outputs JSON data representing the received Hotmart event enriched with metadata and additional flags. The structure varies slightly depending on the trigger mode:

  • Standard Mode: Single output containing an object with:

    • Original event data under data.
    • eventName: Human-readable event name.
    • eventType: Event code string.
    • receivedAt: ISO timestamp of reception.
    • isSubscription: Boolean indicating if the event relates to a subscription.
    • metadata: Includes the verification token and HTTP headers.

  • Smart Mode: Multiple outputs (one per event type). Each output receives the JSON array with the event data corresponding to its event type.

  • Super Smart Mode: Multiple outputs further split subscription-related events into:

    • Single purchase
    • New subscription
    • Subscription renewal
      Additional fields include:
    • isRenewal: Boolean indicating if the event is a subscription renewal.
    • recurrenceNumber: Number of the subscription recurrence.
    • isPrimarySubscription: True if it's a primary subscription payment (not a renewal).
    • paymentMethod and paymentInfo for boleto/PIX/card detection.

No binary data output is produced by this node.

Dependencies

  • Requires configuration of a webhook URL in the Hotmart dashboard pointing to the node's webhook endpoint.
  • Optional use of a verification token (X-HOTMART-HOTTOK header) for security.
  • No external API keys or credentials are required beyond the webhook setup and optional token.
  • No additional environment variables needed.

Troubleshooting

  • Token Verification Failure: If the node is configured to verify the Hotmart token but the incoming request's token does not match, the node responds with HTTP 401 Unauthorized and logs an error. Ensure the token configured in the node matches exactly the token set in Hotmart's webhook settings.

  • Unknown Event Error: If the webhook receives an event not recognized by the node, it responds with HTTP 400 Bad Request and logs "Evento desconhecido". Verify that Hotmart is sending supported event types and that the node's event filter matches.

  • Event Does Not Match Subscription (Standard Mode): When using standard mode with a specific event selected, if the incoming event does not match the selected event, the node returns HTTP 400 with "Evento não corresponde à inscrição". Adjust the event selection or use the "Todos" option to receive all events.

  • Webhook URL Misconfiguration: The node logs instructions to configure the webhook URL in Hotmart. Make sure the URL is correctly copied and set in Hotmart's webhook panel.

  • Multiple Outputs Not Working as Expected: When using Smart or Super Smart modes, ensure your workflow branches handle the multiple outputs properly.

Links and References

Discussion