OpsBrain and n8n, talking in both directions.
n8n and OpsBrain work together out of the box, in both directions. Outbound, signed webhooks flow into an n8n Webhook node. Inbound, any n8n flow can start guided work through the ingest API from a plain HTTP Request node. No custom nodes, nothing to install.
Capabilities
What you can do
Both directions, standard nodes
Events flow out to a Webhook node, and work flows in from an HTTP Request node. Your n8n instance needs nothing extra.
Outbound: signed event stream
OpsBrain delivers every event you subscribe to as an HMAC signed webhook, with a versioned envelope your flows can rely on.
Inbound: start guided work
An HTTP Request node posts to the ingest API and a trigger rule turns it into a queued, guided run with fields prefilled.
Verifiable and secure
Outbound payloads are HMAC signed, inbound sources use per-source tokens with optional signing. Both sides can prove who is talking.
Logs on both sides
Outbound deliveries and inbound events each have full activity logs in OpsBrain, so debugging a flow never involves guessing.
In practice
How teams use it
Enrich an event, then fan it out
run.completed hits an n8n Webhook node. The flow looks up the customer in your database, writes a record to the ERP and posts a summary to the finance channel. One event, three systems updated, no code deployed.
A nightly flow queues tomorrow's work
A scheduled n8n flow reads tomorrow's deliveries from your TMS at 6 p.m. and posts one event per route to the ingest API. By the time the morning shift arrives, their runs are waiting in the queue, named and prioritised.
Self-hosted glue for a self-hosted stack
A manufacturer with an on-premise ERP uses n8n as the bridge: database triggers post events to OpsBrain, and completion webhooks write results back. Everything stays inside their network except the guided execution.
Deviations route to the right reviewer
An n8n flow inspects each run.completed event for deviations. Counts that differ from the ERP go to the inventory team, skipped quality steps go to QA. One webhook, smart routing, no inbox triage.
Setup
How it works
Outbound: add a Webhook node
Create a webhook endpoint in OpsBrain pointing at your n8n Webhook node URL, and subscribe it to events.
Verify the signature
Check the HMAC signature in your flow using the endpoint secret. The in-app docs show exactly how.
Inbound: register a source
Create an external source in OpsBrain and post events from an HTTP Request node with its token.
Map and go live
Define trigger rules and field mappings, send a test event from n8n, and watch it appear in the queue.
See n8n working with your operation.
Book a walkthrough and we will set it up against one of your real workflows, or start on your own in minutes.