Package Information
Documentation
n8n Designer – Salla Nodes (Actions + Triggers)
A community node package that lets you receive and handle Salla webhook events and run Salla Actions inside n8n workflows, with support for multi-endpoint workflows and event-based routing.
This package is built for merchants and automation builders who want to connect Salla stores to n8n with a clean, workflow-first experience.
Key Features
- Salla Trigger: Receive Salla events inside n8n and use them to start workflows.
- Salla Actions: Perform Salla operations through configurable nodes.
- Workflow-friendly design: Designed for multi-step automations and event-based routing patterns.
- Consistent node UX: Clear node naming and grouping for easier navigation in the node list.
Installation
n8n Self-hosted
Install via npm in your n8n environment:
npm install n8n-nodes-n8ndesigner-salla-n8nai
Then restart n8n.
Note: Availability in n8n Cloud depends on n8n’s community node policies.
Usage
- Add the Salla Trigger node to start a workflow from Salla events.
- Add Salla Actions nodes to perform operations as part of the same workflow.
- Use standard n8n nodes (IF, Switch, HTTP Request, Set, Code, etc.) to route and transform data.
Duplicate events
The Salla Trigger ignores an event it has already accepted, so a retry from Salla or
n8n Designer does not run your workflow twice.
De-duplication is scoped per workflow and per trigger node. Routing one event to
several workflows is therefore safe: each workflow runs. Only a repeat delivery of the
same X-Salla-Event-Id to the same trigger node is dropped, within a 10 minute
window. The editor's test listener and production webhooks are tracked separately, so
testing a workflow never suppresses live deliveries.
A skipped delivery still answers HTTP 200, so the sender stops retrying, creates no
execution in n8n, and returns a body that states plainly that nothing ran:
{ "ok": true, "duplicate": true, "executed": false, "event_id": "..." }
Every response the trigger sends follows the same shape, so the sender can tell what
happened without opening n8n:
| Situation | Body | Execution |
|---|---|---|
| Accepted | { "ok": true, "received": true, "executed": true, "event_id": "..." } |
yes |
| Duplicate | { "ok": true, "duplicate": true, "executed": false, "event_id": "..." } |
no |
| Event doesn't match Trigger On | { "ok": true, "ignored": true, "executed": false, "event": "...", "expected": "..." } |
no |
| No event name | { "ok": false, "executed": false, "error": "missing_event" } |
no |
Limits worth knowing:
- The cache is held in memory, so it resets when n8n restarts.
- In queue mode, or behind several webhook processes, each process keeps its own
cache — the same event reaching two processes can run twice.
Keep workflows idempotent regardless (for example, upsert by order id).
Before 0.3.186 de-duplication was keyed on the event id alone and shared across the
whole n8n process, so the first trigger node to see an event claimed it and every
other workflow subscribed to that event was silently skipped.
Support & Contact
- Website: https://n8ndesigner.com/
- Email: support@n8ndesigner.com
- Telegram Community: t.me/+nrnxntkvDn1kNTBk
- News Channel: t.me/+QPFFnJNnnrM5NmVk
License
MIT — Copyright (c) 2025 n8n Designer