Automate anything. Norbix handles the backend. n8n reaches it the way any program does — the REST API, the SDKs, or the MCP server — with a service-user key that holds only the roles you pick.
An nbsu_ key is an AI service user with the roles you pick — Viewer to read one project, Data Editor to change records, Administrator for everything in it. The key comes from the Hub API or the Norbix CLI (Read-only keys in the docs); Cloud lists and removes service users under Account → AI service users. Keep the key in an n8n credential, not in the workflow.
Every endpoint of the REST API is one HTTP Request node away: records, users, files, emails, payments, logs. Send the key as a bearer token and name the project in a header.
GET https://api.norbix.ai/v3/database/collections/orders
Authorization: Bearer nbsu_…
norbix-project-id: pr_…In a Code node the TypeScript SDK (@norbix.ai/ts) does the same with typed methods. And if your workflow uses an AI agent, point its MCP client at the hosted server — https://hub.norbix.ai/v3/account/mcp — with the same key as a bearer header; every Norbix endpoint marked as an AI tool becomes a tool the agent can call.
Add your n8n Webhook URL as a webhook destination in Norbix. A signup, a payment, a record change — the event calls n8n, and your workflow takes it from there: qualify the lead, send the notification, update the record, all against the same production backend.
Norbix webhooks start workflows on backend events: user signups, payments, data changes, and more.
Query your production database over the REST API, filter records, and fetch related data in workflow steps.
Create users, manage roles, update permissions, handle invitations — as far as the key's roles allow.
Trigger payment operations, check transaction status, handle refunds and subscriptions.
Send emails, SMS, and push notifications based on backend events and workflow conditions.
Complex workflows with conditional logic, loops, and calls across all modules. Every call shows up in Logs.
The Viewer and Auditor roles, and a key for CI.
The address, OAuth or a key, the consent screen, roles and environments.
Every tool group per module, which ones read, change, or ask first.
Install, sign in, every command, JSON output, profiles and sessions.
Create a free account, make a service-user key, and build your first automation workflow.