n8n

Workflows with vynst data, triggers on changes and booking times, locks from n8n and ready-made templates with n8n-nodes-inwendo-erp.

The community package n8n-nodes-inwendo-erp adds three nodes to n8n: inwendo ERP (read and write data), inwendo ERP Trigger (start workflows) and inwendo ERP Lock Trigger (your own locks). It connects vynst (inwendo ERP) with more than a thousand other services, such as Slack, Teams, email, Google Sheets or AI agents.

Installation

In n8n, go to Settings → Community Nodes → Install (Einstellungen → Community Nodes → Installieren), enter n8n-nodes-inwendo-erp and confirm. For a self-hosted n8n without the UI:

cd ~/.n8n/nodes
npm install n8n-nodes-inwendo-erp

n8n 1.85 or later, including 2.x, is required.

Credentials

Create credentials of the type inwendo ERP API in n8n:

• ERP Host URL: https://your-instance.iw-erp.de
• API Token (JWT): a long-lived token from Settings → API access (Einstellungen → API-Zugänge)

When you save, n8n checks the token with GET /api/base/api_access_token_test?mode=info. Every request carries X-IW-Trigger-Source: n8n, so changes made by a workflow do not fire that workflow’s own trigger again.

Reading and writing data

The inwendo ERP node covers 23 areas, including company, person, project, ticket (with SLA status), time entry, invoice and offer (with PDF), booking, event, registration, loan, shift, volunteer hours and helper duties, membership breaks, members’ meeting, occupancy, meter, notification (push to the vynst app, email, SMS), lock, webhook and free API calls.

• Get Many can read all pages if you choose.
• Update uses PATCH: fields you do not set stay unchanged.
• The node can be used as a tool for AI agents in n8n.

Starting workflows

The inwendo ERP Trigger starts when a company, person, booking, invoice, ticket, loan, shift, volunteer hour and much more is created, changed or deleted. When activated, it registers itself with vynst (POST /api/n8n/webhook), and when deactivated, it unregisters. It checks incoming calls with the header X-IW-Webhook-Token.

An event looks like this:

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

Booking times: With integration_booking_timed_events_enabled, the trigger also starts before a booking, at its start, at its end and after it ends. This lets you remind caretakers or switch equipment on and off.

Door openings and check-ins: With integration_ha_access_events_enabled, lock logs and check-ins include a summary:

{ "type": "access", "smart_lock_name": "Haupteingang", "action": "unlock",
  "success": true, "person_name": "Max Mustermann", "source": "app" }

Locks from n8n

1. Create an inwendo ERP Lock Trigger, enter your locks (Lock ID, name in vynst, Open button or QR code in the app) and activate the workflow. The trigger registers the locks with /api/n8n/smart_lock/register.
2. In vynst, open the smart lock connection from the provider n8n, Sync devices, and grant rights.
3. When someone with the right taps Open, the workflow receives command (open or lock), lock_id and lock_name, and switches a relay or Shelly.

Commands are signed with HMAC-SHA256 (X-IW-Signature) and are rejected after 60 seconds or when repeated. n8n must be publicly reachable via https.

Templates

To import them, go to Workflows → Import from File:

Features behind switches

If a feature is off in vynst, the node reports this function is switched off (ERP setting "<setting>"). The most important switches:

API

The endpoints under /api/n8n/ are listed under Smart home and automation. Source code and templates: github.com/inwendo/n8n-nodes-inwendo-erp.