Prerequisite: the PC owner installs the host
(no Glasswarp account on that machine). You pair the tray code
while logged in and turn on API access. Create an API key in
Console → API Keys.
What you get
Sessions meter wall-clock minutes from start to end. Always
DELETE the
session — the importable workflow does.
Import the smoke workflow
The first workflow does not click. It lists a usable PC, starts a desktop session, observes text and targets only (image=0 — no JPEG, so the HTTP
node does not choke on a 4K frame), then ends the session.
- Download
n8n-observe-session.json. - In n8n: ⋯ → Import from File (or Import from URL with that JSON link).
- Create a Header Auth credential named Glasswarp API:
- Name:
Authorization - Value:
Bearer gw_live_sk_...(the wordBearer, a space, then your key)
- Name:
- Attach that credential on every HTTP Request node (Import will prompt).
- Confirm the host is online and API access is on.
- Test workflow. Open Console → Sessions and click Eye while it runs — Live View is how you watch; this page does not add a “see the PC” button in Console.
onError: continue on observe). If Start session never
ran, there is nothing to end.
If import complains about the credential id
Delete the dummyGLASSWARP_HEADER_AUTH credential reference and pick your
Header Auth credential on each HTTP Request node. The name Glasswarp API
is only a label.
HTTP map (same API)
Base URL:https://signal.glasswarp.com. Header: Authorization: Bearer <key>.
Usable PC:
online === true and api_access_enabled === true. Full
contract: API reference.
After the smoke: click a named control
Hardcoding “click Export” is as brittle as a selector farm. For a stable dialog you have watched in Live View, resolve a target byname from
observe, then POST /input with a mouse_click at the target center
(x + w/2, y + h/2, native coordinates). For messy screens, put an LLM
node on the observe text.summary / targets and let n8n decide — Glasswarp
still does not own the brain.
Always DELETE the session in a final node, including on the error path.
Cloud vs self-hosted n8n
Both work. The Windows host is the customer’s PC; n8n only needs outbound HTTPS tosignal.glasswarp.com. Do not put the Glasswarp host installer on the n8n
server unless that server is the Windows PC you mean to drive.
Related
- Pair a PC
- Ways to run agents
- Observe
- Live View
- Connect via MCP — Cursor / Claude, not n8n
