n8n
The Evinor node for n8n starts a workflow each time a sensor fires. It connects itself to the sensor as a connected app and verifies every delivery for you, so you don't paste URLs or secrets between the two products.
Install
In n8n, open the nodes panel on the canvas, search for Evinor and install
the node. On self-hosted n8n you can also install
@evinor/n8n-nodes-evinor from Settings → Community Nodes. Either way, you
need to be an instance owner or admin.
Credentials
Create an Evinor credential in n8n with an API key that has both scopes (see Authentication):
| Scope | Used for |
|---|---|
SENSORS_READ | Listing your sensors and checking an existing destination |
SENSORS_WRITE | Connecting and removing the destination, sending test deliveries |
The credential's base URL defaults to the production API. It also accepts plain
http://, which sends your API key in cleartext, so use that only for local
testing.
Choose a sensor
Add the Evinor trigger node and pick a sensor from the list, or give its id. A disabled sensor is listed with a note. You can connect to one, and it delivers once it is enabled.
Setting it up with an agent
An agent connected to the Evinor MCP server can do the Evinor side; the node does the rest:
- The agent creates or finds the sensor with the
create_sensororlist_sensorstool.create_sensorneeds at least one webhook or Slack destination of its own; the node's destination is added alongside it. - In n8n, the Evinor trigger node is set to that sensor's id, with an Evinor credential as above. The agent uses n8n's own tools, or you do it on the canvas.
- Activating the workflow connects the node to the sensor, as described under How the connection works. The node keeps the signing secret it is given.
No Evinor tool connects n8n or hands out the node's secret: the connected-app endpoints the node calls are not MCP tools, so the secret never passes through the agent's transcript.
Your n8n must be reachable over public HTTPS
Evinor delivers to n8n's webhook URL, which must be reachable over public HTTPS. A localhost or LAN n8n instance cannot receive deliveries, because Evinor's delivery path blocks private and loopback addresses. This applies to test events too.
How the connection works
- Activating the workflow connects a destination for its webhook URL. If you placed a waiting n8n destination on the sensor, the connection fills it; otherwise a new destination is added. A sensor holds at most 10 destinations.
- Deactivating the workflow removes the destination. If it was the sensor's only destination, it reverts to a waiting destination.
- Reactivating the workflow connects again, with a new destination id and a
new signing secret. If a destination for the same URL was left behind (for
example, n8n crashed before removing it), the new connection replaces it
instead of failing. The old destination id then returns
404, and its delivery history does not carry over.
A workflow's webhook URL is its own, so two workflows on the same sensor get two separate destinations and don't replace each other.
If your n8n webhook URL changes (for example, a new WEBHOOK_URL), the old
destination keeps delivering to the old URL until you remove it in Evinor. If n8n
crashes before saving a new connection's signing secret, deliveries are rejected
until you reactivate the workflow.
If connecting fails, n8n shows the reason from the API. A URL already used by a
different destination of the sensor, or a sensor that already has 10
destinations, returns 409 state-conflict.
The signing secret is kept in the workflow's static data, which n8n stores in plain text in its database and in workflow exports. Treat both as sensitive.
Test events
Listen for test event requests a one-shot test delivery to n8n's test URL instead of connecting a destination, so it never affects a live destination:
- About five seconds later, Evinor sends one sample event, synthesized from the sensor's event type and never real event data.
- It is sent once and never retried, and it consumes no credits.
- You can request at most 5 test deliveries per account every 10 minutes. Over
that limit the API returns
429rate-limited, and the node shows the reason instead of retrying.
Test events arrive with isTest: true in the node's default output.
Signature verification
The node handles signature verification for you. It rejects a
delivery with 401, without running the workflow, when the signature does not
match, when sender.keyId is not the one it stored, or when the delivery's
timestamp is more than 5 minutes from the current time in either direction.
Output
By default the node outputs the delivery's payload plus messageId,
idempotencyKey and isTest. With Simplify on, it outputs
payload.details with roles flattened to { CODE: textValue }, plus parsed
values, and still includes messageId, idempotencyKey and isTest.
Handling duplicates
The node does not deduplicate. A retried delivery, or one replayed within the
5-minute window, runs the workflow again. To process each event once, track
idempotencyKey in your workflow: it is stable across every attempt of the same
delivery, while messageId changes on each attempt. See
Replay protection.