Overview
This node acts as a webhook trigger for Salla, an e-commerce platform. It listens to various events from Salla such as order creation, product updates, customer changes, payments, shipments, and reviews. When one of the selected events occurs in Salla, the node receives the webhook payload and triggers the workflow.
Common scenarios where this node is beneficial include:
- Automating order processing when new orders are created or updated.
- Syncing product or customer data with other systems upon changes.
- Reacting to payment or shipment status updates.
- Monitoring coupon usage or special offers applied.
- Collecting and processing new reviews automatically.
For example, you could use this node to start a workflow that sends a notification email whenever a new order is created or to update your CRM system when a customer is updated.
Properties
| Name | Meaning |
|---|---|
| Events | The specific Salla events to listen to. Options include: Order Created, Order Updated, Product Created, Customer Deleted, Payment Updated, Coupon Used, Shipment Created, Review Created, and many more. Selecting "*" listens to all events. |
| Validate Webhook | Whether to validate the webhook signature to ensure the request authenticity. |
| Webhook Secret | The secret key used to validate the webhook signature. If left empty, the secret from credentials will be used. |
| Return Raw Data | Whether to return the raw webhook data instead of parsed event data. |
Output
The node outputs JSON data representing the webhook event received from Salla. The structure depends on whether "Return Raw Data" is enabled:
If Return Raw Data is
false(default), the output JSON includes:event: The event type string (e.g., "order.created").timestamp: Timestamp of the event from headers or current time.merchantId: Merchant identifier from headers or payload.data: The main event data payload.- Other top-level properties from the webhook payload except
merchant_id.
If Return Raw Data is
true, the output JSON includes:headers: All HTTP headers received.body: The full webhook payload as received.event: The event type.timestamp: Current timestamp.
No binary data output is produced by this node.
Dependencies
- Requires an active webhook endpoint configured in n8n to receive POST requests from Salla.
- Optionally requires an API authentication token or OAuth2 credential containing the webhook secret if webhook signature validation is enabled and no secret is manually provided.
- Uses an internal helper function to validate webhook signatures based on the secret.
Troubleshooting
- Event Ignored: If the incoming event type is not among the selected events, the node responds with a message "Event ignored" and does not trigger the workflow. Ensure the correct events are selected.
- Invalid webhook signature: If signature validation is enabled and the signature does not match, the node throws an error "Invalid webhook signature". To resolve:
- Verify the webhook secret matches the one configured in Salla.
- Check that the secret is correctly set either in the node property or credentials.
- Confirm that the webhook request is unaltered and uses the expected signature header.
- Missing Event Type: If the event type cannot be determined from headers or payload, the event defaults to "unknown" and may be ignored unless "*" is selected.
- Credential Issues: If the webhook secret is not provided and credentials are missing or invalid, signature validation will fail.
Links and References
- Salla Official Documentation – For details on available webhook events and payloads.
- Webhook Security Best Practices – General advice on validating webhook signatures.
- n8n Webhook Trigger Nodes – Understanding how webhook triggers work in n8n.