Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-apiron
n8n community node package for the Apiron lead distribution platform — the n8n counterpart of make-app/ (Make.com) and zapier-app/ (Zapier).
Unlike those two (which are JSON specs pasted into the platforms' builders), this is a real npm package that n8n loads directly.
What's in the package
| File | What it is |
|---|---|
credentials/ApironApi.credentials.ts |
API-key credential (X-API-Key header) + verify test against GET /api/n8n/verify. Includes a baseUrl field (default https://app.apirongroup.com) so the same package works against staging/local. |
nodes/Apiron/ApironTrigger.node.ts |
Apiron Trigger — webhook trigger for new lead matches. On workflow activation it registers its webhook URL via POST /api/n8n/webhooks; on deactivation it unregisters via DELETE /api/n8n/webhooks/{id}. Same REST-hook lifecycle as the Zapier app. |
nodes/Apiron/Apiron.node.ts |
Apiron action node with four operations: Update Lead Status, Submit Lead Feedback, Submit Pipeline Event (POST /api/crm-pipeline/events?via=n8n), Get Recent Leads. |
The backend endpoints live in the main app under src/app/api/n8n/* and share their handlers with Make/Zapier (src/lib/integration-handlers.ts). The n8n API key is a third, independent key (Bildungstraeger.n8nApiKey) managed on the customer-facing page /crm/integration/n8n.
Build
cd n8n-app
npm install
npm run build # tsc + copy icon → dist/
This directory is intentionally excluded from the main app's tsconfig/eslint — it has its own toolchain and depends on n8n-workflow, which is not installed at the repo root.
Publish to npm
Community nodes are installed by package name from npm, so the package must be published:
cd n8n-app
npm run build
npm publish --access public
Bump version in package.json for every release. n8n instances update via Settings → Community Nodes → Update.
Install in n8n (self-hosted)
- In n8n: Settings → Community Nodes → Install
- Enter
n8n-nodes-apironand confirm the risk prompt. - The nodes "Apiron Trigger" and "Apiron" appear in the nodes panel.
For n8n Cloud, the package must go through n8n's verified community node review before it is installable. Until then, cloud users can use the plain HTTP Request / Webhook nodes against the same endpoints (documented on /crm/integration/n8n).
Local development install (without npm publish)
cd n8n-app && npm install && npm run build && npm link
cd ~/.n8n/nodes && npm link n8n-nodes-apiron # then restart n8n
Testing against staging/local
Create the credential with baseUrl pointing at https://staging.apirongroup.com or http://localhost:3000 and the corresponding institution's n8n API key. Note the trigger only works if Apiron can reach the n8n instance's webhook URL from the internet (use a tunnel for local n8n).
Example workflows
[Apiron Trigger] → [Gmail: Send Email] # notify on every new lead
[Apiron Trigger] → [HubSpot: Create Contact] → [Apiron: Update Lead Status → ANRUFVERSUCH]
[HubSpot Trigger: Deal Updated] → [Apiron: Submit Pipeline Event] # ROAS / pipeline sync