n8n-nodes-inwendo-erp

This is an n8n community node package for integrating with the inwendo ERP system.

It provides nodes to read, create, and update ERP data from n8n workflows, and a trigger node to receive webhook events from the ERP.

Nodes

inwendo ERP (Action Node)

Perform CRUD operations on the following ERP resources:

| Resource | Operations | |----------|-----------| | Company | Get, Get Many, Create, Update (PATCH) | | Person | Get, Get Many, Create, Update (PATCH) | | Invoice | Get, Get Many, Create, Update, Get PDF | | Offer | Get, Get Many, Create, Update, Get PDF | | Ticket | Get, Get Many, Create, Update (PATCH) | | Project | Get, Get Many, Create, Update (PATCH) | | Time Entry | Get, Get Many, Create, Update (PATCH) | | Booking | Get, Get Many, Create, Update (PATCH) | | Event | Get, Get Many, Create, Update (PATCH) | | Event Sign-Up | Get, Get Many, Create, Update (PATCH) | | News Article | Get, Get Many, Create, Update (PATCH) | | Webhook | Get, Get Many, Create, Update | | Generic API Request | Custom HTTP request to any ERP endpoint |

inwendo ERP Trigger

Receives webhook events from the ERP when entities are created, updated, or deleted. Supports filtering by entity type and action, and automatically registers/removes the matching webhook in the ERP when the workflow is activated/deactivated.

Credentials

You need an inwendo ERP API token (JWT) to authenticate. Configure:

• ERP Host URL: The base URL of your ERP instance (e.g., https://demo.iw-erp.de)
• API Token (JWT): Your API access token

The token can be validated via the /api/base/api_access_token_test?mode=info endpoint.

JWT API Token Requirements

When creating the API access token in the ERP (Settings → API Access Tokens → Create), use these settings:

| Setting | Required value | Why | |---|---|---| | Scope → Webhook | Write | POST and DELETE on /api/n8n/webhook are annotated userAccessType=Write. | | Expiration | Long-lived | The plugin has no refresh flow, so a short TTL will silently break webhook registration on the next activation. | | URL path restriction (optional hardening) | /api/n8n/webhook* | Least-privilege — the Trigger node only touches that prefix for auto-registration. |

ERP version: auto-registration requires an ERP build that ships the dedicated N8nWebhookController (/api/n8n/webhook). Older installations still need to use the manual setup path below.

Those requirements apply only to the auto-registration feature of the Trigger node. If the same credential is also used by the action node to read or write data (e.g. /api/crm/crmcompanies, /api/invoice/invoices, …), grant the corresponding per-resource scopes in addition to Webhook — that is unrelated to webhook auto-registration.

If your ERP build is too old (no /api/n8n/webhook) or you simply prefer to manage the webhook yourself, switch Auto Register Webhook in ERP off on the Trigger node and create the RegisteredWebhook in the ERP UI manually (see Manual setup below). In that mode the token only needs the scopes for the resources the action node actually calls.

Installation

In n8n (Community Node)

1. Go to Settings > Community Nodes
2. Select Install
3. Enter n8n-nodes-inwendo-erp
4. Agree to the risks and click Install

Local Development

# Clone the repository
git clone https://github.com/inwendo/n8n-nodes-inwendo-erp.git
cd n8n-nodes-inwendo-erp

# Install dependencies
npm install

# Build
npm run build

# Link to your local n8n installation
npm link
cd /path/to/n8n
npm link n8n-nodes-inwendo-erp

Setting Up Webhooks (ERP -> n8n)

To trigger n8n workflows from ERP events:

1. Add an inwendo ERP Trigger node to your workflow
2. Pick the Entity Type and Action you want to listen for
3. Select or create an inwendo ERP API credential on the trigger node
4. Activate the workflow

With Auto Register Webhook in ERP enabled (the default), activating the workflow will:

• call POST /api/n8n/webhook on the ERP to register (or update) a RegisteredWebhook row scoped to notificationClientId = 'n8n', pointing at n8n's production webhook URL and filtered by the selected entity type and action
• generate a random notificationClientToken (if you did not set one manually) and persist it with the workflow so that incoming requests are always validated against the X-IW-Webhook-Token header

Deactivating the workflow calls DELETE /api/n8n/webhook with the same webhook_url, which soft-deletes every matching n8n-owned row so it no longer fires.

The POST /api/n8n/webhook endpoint is idempotent on (webhook_url, notificationClientId = 'n8n'): if you edit the trigger's entity type, action, or webhook token and re-activate, the existing row is updated in place instead of creating a duplicate.

ERP version: this flow requires an ERP build that ships the dedicated N8nWebhookController (/api/n8n/webhook). Older installations do not support auto-registration and must use the manual setup below with Auto Register Webhook in ERP disabled on the trigger.

Manual setup (advanced)

If you prefer to manage the webhook yourself (for example because multiple workflows share a single ERP webhook), switch Auto Register Webhook in ERP off on the trigger node. Then create a RegisteredWebhook in the ERP manually, either via the API or the admin UI:

• notificationType: HTTP_POST
• notificationUrl: The Production Webhook URL shown on the trigger node
• referenceClassName: Entity to watch (e.g., CRMCompany)
• databaseAction: create, update, or delete
• Optionally set notificationClientToken and configure the same value in the trigger node's Webhook Token field

Webhook Payload Format

The ERP sends the following JSON payload:

{
  "iw_entity_class": "Inwendo\\CRMBundle\\Entity\\CRMCompany",
  "iw_entity_short_class": "CRMCompany",
  "iw_entity_id": "123",
  "iw_action": "update",
  "iw_dt": 1709500000,
  "data": { ... }
}

API Endpoints

| Resource | API Path | |----------|----------| | Company | /api/crm/crmcompanies | | Person | /api/crm/crmpeople | | Project | /api/crm/crmprojects | | Ticket | /api/crm/tickets | | Time Entry | /api/time/entries | | Invoice | /api/invoice/invoices | | Offer | /api/invoice/offers | | Booking | /api/event/base_booking | | Event | /api/event/base_event | | Event Sign-Up | /api/event/base_event_signup | | News Article | /api/media/news_article | | Webhook | /api/dw/webhook |

License

MIT