Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-orbit-office
An n8n community node for Orbit Office:
tables and columns in dropdowns, records in and out, and a raw call for everything else.
Why not just an HTTP Request node
Because of one rule in the API that does not announce itself. A record's values are keyed by a
column's key — k_7f3a91 — and a column name is silently dropped: {"Status": "Ready"}
is answered 201 and writes nothing. The same narrowing applies to values: a number column
sent the string "12" stores nothing, also with a 201.
This node closes both. Create and Update draw the table's own columns as a form: a select
is a dropdown of its real choices, a number is a number box, a date is a date picker, a checkbox is
a toggle — and the columns a cell write cannot touch (formula, relation, button, id, the
created/edited stamps) are not offered at all, because a box for one would answer 201 and change
nothing.
The choices matter more than they look: a select cell holds a choice id (c_live), not the
word on screen. Typing Ready into it writes nothing.
Install
n8n → Settings → Community nodes → Install → n8n-nodes-orbit-office.
Self-hosted n8n only: n8n Cloud installs verified packages, and this is not one.
Credential
| App URL | The origin you open Orbit on — https://app.orbit-office.com. Not the API host: one origin serves both and /v1 is proxied from it. |
| API Key | orb_…, minted by the workspace owner in Automation → Api Keys and shown once. |
A key acts as the workspace, not as a person, and belongs to exactly one — there is no
workspace id anywhere in this node because there is nothing to address. Two workspaces means two
credentials.
Scopes: read and write is the common case. Add config only if this n8n will build columns,
tables or members. spend is a budget rather than a permission and is only needed for address
search and the AI formula writer.
The credential tests itself against GET /v1/workspace when you save it, so a wrong key fails
where you typed it.
What it does
Record — Get, Search (filtered, sorted, paged, or all of it), Create, Update, Delete (to the
trash, where it can be restored).
Get, Update and Delete pick the record by name: the box searches the table's primary column —
the one the app draws down the left edge — so you do not have to find an id for a record you can
see on your screen. Pasting an id still works, because that is what the node before this one will
hand it. Search has a Name Contains option for the same question over many records.
Both reads put each value under its column's name as well as its key, so the next node says$json.Stage rather than $json.values.k_2b8c04. The keys stay in values, because a write takes
keys — a Get feeding an Update does not translate back.
Table — List tables, List columns (this is how you find the keys).
Page — Get (with its document), Get Many, Create, Update.
View — List the views of a table, with the filters and sorts each one stores.
Orbit Office Trigger — a webhook the other way round: Orbit starts the workflow. Point a
rule's send_webhook action at the URL this node gives you, paste the signing secret Orbit shows
once, and every delivery is checked before anything runs.
Custom API Call — a method and a path relative to /v1, with the same credential. Orbit has
187 key-reachable endpoints and this node wraps a handful on purpose; nothing is out of reach
because of what is not in the menu. The whole reference is at /llms-full.txt and /docs on your
own host.
Searching
Rules are {column, operator, value} and a value may be a list, which is one rule matching any
of them (is with ["shot","editing"]) — or, with a negative operator, none of them. Which
operators apply depends on the column type, and Orbit refuses one that does not, saying so.
The trigger, and why it verifies
Orbit signs every delivery: orbit-signature: t=…,v1=…, an HMAC-SHA256 over t.body with the
rule's own secret. The timestamp is inside the signed string, so a captured delivery stops
being replayable once it is more than 300 seconds old — signing the body alone would leave it
valid forever, because the body never changes.
The secret sits on the node rather than on the credential, because it belongs to the rule: one
workspace key, many rules, a secret each.
A delivery that fails the check is answered 401 and starts nothing. One that is filtered out by
Only These Events is answered 200 and starts nothing — Orbit must see a 200, or it retries
a body you deliberately ignored and files it as failed.
Errors
Orbit answers every failure as {"error": {"code", "message"}}. The node lifts the message into
n8n's red box and keeps the code beside it, so you get "That key is not valid — unknown, revoked,
or expired. (unauthorized)" rather than "403 Forbidden". The limit is 300 requests a minute,
counted against the key.
Developing
npm install
npm run build # tsc, then the icons into dist
npm run verify # 67 checks: the paths n8n loads, the form, the value reader, the signature
npm run verify is the one that matters before publishing: every way a community node fails is
quiet — a path in package.json → n8n that does not exist after a build installs with a green
tick and shows no node at all.
To try it without publishing, build and drop the folder into your n8n's ~/.n8n/nodes/node_modules/,
then restart n8n.
Where this lives
apps/n8n in the Orbit Office repository, deliberately not a workspace of the rootpackage.json: adding it there would rewrite the root lockfile that the Docker build reads, and
a node package has no business touching the API's deploy.