Kiwify Trigger

Kiwify Webhook Trigger

Overview

The Kiwify Trigger node is designed to receive and process webhook events from the Kiwify platform within n8n workflows. It acts as a trigger, starting workflows when specific events occur in your Kiwify account, such as purchases, subscription changes, or payment updates. This node is particularly useful for automating actions based on customer activity, such as sending notifications, updating CRM records, or managing orders.

Practical examples:

Automatically send a thank-you email when a purchase is approved.
Notify your team when a subscription is late or canceled.
Update your database when a boleto (bank slip) or Pix payment is generated.
Handle abandoned carts by triggering follow-up sequences.

Properties

Name	Type	Meaning
Event	options	The type of Kiwify event that will trigger the workflow. Options include various order, payment, and subscription events (e.g., "Assinatura Atrasada", "Compra Aprovada", "Pix Gerado", "Carrinho Abandonado", "Todos").

Output

The node outputs a JSON object with the following structure:

{
  "originalData": { /* The full body of the incoming webhook request from Kiwify */ },
  "event": "..." // The internal event type string determined from the webhook payload
}

originalData: Contains all data sent by Kiwify in the webhook POST request.
event: The normalized event type as interpreted by the node (e.g., "postback.compra.aprovada").

Note: The node does not output binary data.

Dependencies

External Service: Requires a valid Kiwify API token (provided via n8n credentials named kiwifyApi).
n8n Configuration: The node must be set up as a webhook endpoint (POST method at path /mkt/kiwify). Ensure your Kiwify account is configured to send webhooks to this URL.
Environment Variables: None required beyond standard n8n setup.

Troubleshooting

Common Issues:

Invalid signature:
If the webhook request's signature does not match the expected HMAC-SHA1 hash (using your Kiwify API token), the node will respond with "Invalid signature" and ignore the request.
Resolution: Double-check that the correct API token is used in both Kiwify and n8n credentials.
Invalid event:
If the event type in the webhook does not match the selected "Event" property (and is not set to "Todos"), the node will respond with "Invalid event" and not trigger the workflow.
Resolution: Ensure the "Event" property matches the types of events you expect to receive, or use "Todos" to accept all supported events.
No data received:
If the webhook is not triggered, verify that Kiwify is correctly configured to send webhooks to your n8n instance and that your n8n instance is accessible from the internet (or use test mode).