Integrating n8n

Overview

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.

Before you start

The Keysender community node for n8n is being published; the steps below apply as soon as it is available.

Make sure you have:

• A Keysender vendor account.
• Your API key and secret, from Account > Settings > API access in the panel.
• A self-hosted n8n instance running, with community packages enabled. It is on by default. If your instance was started with N8N_COMMUNITY_PACKAGES_ENABLED=false, set it to true and restart n8n.

Steps

1. In n8n, go to Settings > Community Nodes > Install a community node.

2. Enter the package name n8n-nodes-keysender.

3. 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.

4. 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.

5. Click Test.

6. Add a Keysender node to your workflow, select the credential, then choose a Resource and an Operation.

Confirm it works

The credential test returns Connected. Run the workflow once and check the node returns data from your account.

What you can build

• Route a delivered order straight to Slack, email, a spreadsheet, or a database.
• Chain a Low Stock trigger into a supply catalog reorder so you restock before selling out.
• Add keys from a spreadsheet, and they go live everywhere the product sells.

Good to know

• Self-hosted only. The node does not run on n8n Cloud.
• Triggers poll on the schedule you set, commonly every 15 minutes. There is no push feed, so nothing arrives faster than that interval.
• Key and code values are masked by default. Turn on Reveal Codes per operation only when you need the real value.
• Your account gets 600 requests a minute, shared across every workflow using the credential.
• List operations cap at 50 pages per run. Narrow a search with filters like platform or SKU instead of using Return All on a large dataset.
• Trigger events dedupe by id, or by threshold crossing for Low Stock and Low Credits, so restarting a workflow will not replay orders already seen.

Troubleshooting

• The Keysender node is not in the node panel. Confirm the instance is self-hosted, then reinstall from Settings > Community Nodes with the exact package name n8n-nodes-keysender and restart n8n.
• The credential test fails. Re-copy the API key and secret from Account > Settings > API access. An extra space is a common cause. Check the Base URL.
• The install is blocked. Community packages may be disabled. Set N8N_COMMUNITY_PACKAGES_ENABLED to true, or remove it, then restart n8n.
• No new items from the trigger. Confirm there is genuinely new activity, and check that no platform filter on the trigger is excluding it.

If it still is not working

Submit a claim so Keysender Support can review it.