Evermart Trigger icon

Evermart Trigger

Evermart Webhook Trigger

Overview

The Evermart Trigger node is designed to receive webhook events from the Evermart platform in n8n. It acts as a trigger, starting workflows when specific events occur in Evermart, such as purchases, subscription changes, or payment updates. This node is particularly useful for automating processes based on customer actions—like sending notifications after a purchase, updating CRM records when a subscription is renewed, or handling abandoned carts.

Practical examples:

  • Send a thank-you email when a purchase is approved.
  • Notify your team if a subscription is canceled or delayed.
  • Start a recovery workflow for abandoned carts.
  • Update financial records when a refund or chargeback occurs.

Properties

Name Type Meaning
Event options The type of Evermart event to listen for. Options include various purchase, subscription, and payment-related events, as well as "Todos" (all events). This property determines which webhook events will trigger the workflow.

Event options include:

  • Assinatura Atrasada (Subscription Late)
  • Assinatura Cancelada (Subscription Canceled)
  • Assinatura Renovada (Subscription Renewed)
  • Boleto Gerado (Billet Generated)
  • Carrinho Abandonado (Abandoned Cart)
  • Chargeback
  • Compra Aprovada (Purchase Approved)
  • Compra Recusada (Purchase Refused)
  • Compra Cancelada (Purchase Canceled)
  • Compra Concluída (Purchase Completed)
  • Pix Gerado (Pix Generated)
  • Reembolso (Refund)
  • Todos (All Events)

Output

The node outputs a JSON object with the following structure:

{
  "originalData": { /* The full body of the incoming webhook request */ },
  "event": "..." // The normalized event type string, e.g., "postback.compra.aprovada"
}
  • originalData: Contains all data sent by Evermart in the webhook payload.
  • event: The standardized event identifier that triggered the workflow.

Note: This node does not output binary data.

Dependencies

  • External Service: Requires access to the Evermart platform's webhook system.
  • API Key: Needs valid Evermart API credentials (evermartApi), specifically the hottok token for signature verification.
  • n8n Configuration: The webhook endpoint must be accessible to Evermart; ensure your n8n instance is publicly reachable or use n8n's tunnel feature during development.

Troubleshooting

Common Issues:

  • Invalid signature:
    If the incoming webhook's hottok does not match the stored credential, the node will respond with "Invalid signature" and not trigger the workflow.
    Resolution: Double-check your Evermart API credentials in n8n and ensure they match what is configured in Evermart.

  • No workflow execution:
    If the selected "Event" does not match the incoming event type and is not set to "Todos", the workflow will not run.
    Resolution: Set the "Event" property to the correct event type or to "Todos" to catch all events.

  • Webhook not received:
    If no data arrives, verify that the webhook URL is correctly set up in Evermart and that your n8n instance is reachable from the internet.

Links and References

Discussion