Prerequisites
Before you begin, make sure you have:- A self-hosted n8n instance (v1.0 or later)
- A Chariow API key (starts with
sk_) — generate one from Settings → API Keys in your Chariow Dashboard - Node.js >= 18.10 on the machine running n8n
Installation
npm (recommended)
Run the following command in your n8n user directory:Docker
If you run n8n in Docker, set theN8N_CUSTOM_EXTENSIONS environment variable to install the package on startup:
Community Nodes UI support is planned. Once available, you will be able to install directly from Settings → Community Nodes inside n8n.
Configure credentials
1
Open credentials
In n8n, go to Settings → Credentials → Add Credential.
2
Search for Chariow
Search for Chariow API and select it.
3
Enter your API key
Paste your Chariow API key (starts with
sk_) into the API Key field.4
Save
Click Save. n8n will test the connection automatically. A green tick confirms your key is valid.
Verify installation
1
Create a new workflow
Click New Workflow in n8n.
2
Add a node
Click + to add a node and search for Chariow.
3
Confirm both nodes appear
You should see two nodes:
- Chariow — for performing actions (get, list, create)
- Chariow Trigger — for starting workflows from store events
Troubleshooting
Nodes not appearing after install
Nodes not appearing after install
- Make sure you installed the package in the correct directory (
~/.n8nfor npm installs) - Restart n8n completely after installation
- Check the n8n logs for any installation errors:
docker logs n8nor check your process output - Verify the package is installed:
ls ~/.n8n/node_modules/@chariow
Credential test failed
Credential test failed
- Confirm your API key starts with
sk_and is copied in full - Check that your store is active in the Chariow dashboard
- Ensure your n8n instance can reach
https://api.chariow.com(no firewall or proxy blocking)
Docker container issues
Docker container issues
- Verify the
N8N_CUSTOM_EXTENSIONSenvironment variable is set correctly - Rebuild and restart the container:
docker compose down && docker compose up -d - Check container logs for npm install errors:
docker logs <container_name>
Next steps
Available resources
See all resources and operations
Trigger events
Browse the 8 available trigger events