Reading this in another language? Use your browser's built-in translate option. Button and field names stay in English on purpose, to match what you see in Keysender.
Install the Keysender community node package in n8n so a workflow can read and act on your orders, stock, products, customers, and supply catalog, and trigger on events like a new order or low stock. The node is for self-hosted n8n only.
TL;DR
n8n-nodes-keysender community node, then create a Keysender credential with those values.The Keysender community node for n8n is being published; the steps below apply as soon as it is available.
Make sure you have:
N8N_COMMUNITY_PACKAGES_ENABLED=false, set it to true and restart n8n.In n8n, go to Settings > Community Nodes > Install a community node.
Enter the package name n8n-nodes-keysender.
Check I understand the risks of installing unverified code, then click Install. Both Keysender nodes appear in your node panel. This warning shows for any community node, not only Keysender's.
Create a Keysender API credential. Paste in your API Key and API Secret, and set the Base URL, which defaults to https://panel.keysender.com.
Click Test.
Add a Keysender node to your workflow, select the credential, then choose a Resource and an Operation.
The credential test returns Connected. Run the workflow once and check the node returns data from your account.
| Symptom | Cause | Action |
|---|---|---|
| The Keysender node is not in the node panel | The instance is not self-hosted, or the package name was wrong | Confirm self-hosted n8n, then reinstall with the exact name n8n-nodes-keysender and restart n8n |
| The credential test fails | The API Key or Secret was copied incorrectly, often with an extra space | Re-copy both from Account, Settings, Security, and check the Base URL |
| The install is blocked | Community packages are disabled on this instance | Set N8N_COMMUNITY_PACKAGES_ENABLED to true, or remove it, then restart n8n |
| No new items from the trigger | Nothing genuinely new has happened, or a platform filter excludes it | Confirm there is new activity, and check the trigger's platform filter |
Submit a claim so Keysender Support can review it.
No, not today. Community nodes, Keysender's included, install only on self-hosted n8n. n8n Cloud does not allow arbitrary community packages, so self-hosting your own server, container, or home lab box is the only way to run this node.
It covers 33 operations across seven resources: Order, Stock, Product, Customer, Catalog, Dashboard, and Message. A separate Keysender Trigger node polls for seven events, including New Order, Order Delivered, Low Stock, Low Credits, New Customer, New Buyer Message, and New Catalog Product.
Yes. Any operation that could return a raw key value masks it by default. Turn on that operation's Reveal Codes toggle only when a workflow truly needs the real value, for example to deliver it yourself, and leave it off for counts, logs, and notifications.