glonasssoft

Read-only n8n community nodes for the GLONASSSoft Public API 3.0

Documentation

@catalogicus-international/n8n-nodes-glonasssoft

Read-only n8n community nodes for the GLONASSSoft Public API 3.0. The package exposes documented retrieval, reporting, analytics, and export methods while keeping all mutation methods out of workflow and AI operation selectors.

Features

  • Four nodes: GLONASSSoft, GLONASSSoft Authentication, GLONASSSoft AI, and GLONASSSoft Trigger.
  • 72 read-only operations classified from 148 documented HTTP method/path combinations.
  • Safe GET and read-only POST requests for searches, telemetry, reports, analytics, and exports.
  • Separate login and ready-token credentials.
  • Dedicated AI Agent tool surface containing only read-only operations.
  • Polling trigger for changed vehicle snapshots.
  • Automatic 500 ms request spacing and a three-request report concurrency limit.
  • No runtime dependencies outside n8n-workflow.

Mutation operations are retained only in the generated documentation inventory. They cannot be selected or executed by the workflow or AI nodes. The package intentionally has no Custom API node or arbitrary-path option.

Installation

Install @catalogicus-international/n8n-nodes-glonasssoft as a community node package in n8n. The package requires an n8n version that supports the current community-node tooling and AI Tool nodes.

Authentication

Use GLONASSSoft Login API credentials with GLONASSSoft Authentication to obtain an X-Auth token. Pass its token and baseUrl output fields to Session Token Override and Base URL Override in the main or AI node. Overrides are evaluated per input item and take precedence over stored token credentials.

For scheduled workflows and the Trigger, store the server URL and a ready token in GLONASSSoft Token API credentials. Tokens are sent only through the X-Auth header.

The default server is https://hosting.glonasssoft.ru. Private GLONASSSoft servers are supported through the Base URL credential field. A Base URL must be an HTTPS origin only, for example https://monitoring.example.com or https://monitoring.example.com:8443; paths, query strings, fragments, and embedded credentials are rejected.

Nodes

  • GLONASSSoft — select a read-only Resource and Operation, then provide path, query, and body parameters.
  • GLONASSSoft Authentication — exchange a login and password for an X-Auth token.
  • GLONASSSoft AI — configure one safe operation and connect its generated Tool variant to an AI Agent.
  • GLONASSSoft Trigger — poll the latest data for selected vehicle IDs and emit changed snapshots.

The main and AI nodes support two input modes:

  • Fields — provide generated path fields plus JSON objects for Query and Request Body. Request Body is used only by read-only POST operations.
  • Raw JSON — provide an object with optional path, query, and body properties.

Response Mode defaults to Auto: documented exports become binary data, arrays become separate n8n items, and other responses become one item. Single Item, Split Items, and Binary can override that behavior. Binary files are returned in property data. Every output retains its input-item pairing, and Continue On Fail produces an error item for the affected input.

Safety and limits

  • Login and password are sent only to POST /api/v3/auth/login; ready tokens are sent only in the X-Auth header.
  • Runtime requests accept only HTTPS origins and relative /api/v3/... paths.
  • Runtime API calls are globally spaced by at least 500 ms inside the n8n process.
  • No more than three /api/v3/Reports/... requests are allowed to run concurrently.
  • The operation registry is generated from a committed documentation snapshot; runtime execution does not fetch API documentation.

Trigger

Configure a comma-separated list of vehicle IDs and choose whether sensor values should be included. The first active poll establishes a baseline and emits nothing. Later polls emit vehicleId, previous, current, and a sorted changedFields array for new or changed vehicles.

Manual execution returns the current snapshots without changing the baseline. Changing the vehicle list or Include Sensors resets the baseline. A vehicle omitted from one response is retained in the baseline and is not treated as deleted.

API Snapshot

The source page is Methods for working with the GLONASSSoft API. A snapshot dated 2026-09-25 is committed under api-docs/; generation and runtime never fetch it from the network. pnpm generate deterministically rebuilds nodes/shared/generated/operations.ts; do not edit that generated file manually.

Development

pnpm install
pnpm generate
pnpm run generate:check
pnpm run validate:skills
pnpm run lint
pnpm run build
pnpm test
npm pack --dry-run

Русский

Пакет предоставляет read-only интеграцию n8n с GLONASSSoft Public API 3.0. Изменяющие методы остаются только в сгенерированном реестре документации и недоступны для выбора в workflow и AI.

  • Одна основная нода с выбором раздела и операции.
  • 72 операции получения данных: поиск, телеметрия, сообщения, отчёты, аналитика и экспорт.
  • Четыре ноды: основная, авторизация, AI Tool и polling trigger.
  • Изменение, создание, удаление, импорт, команды терминалам и изменение биллинга недоступны.
  • Запросы выполняются с паузой не менее 500 мс; одновременно формируется не более трёх отчётов.

Для интерактивного workflow используйте GLONASSSoft Authentication, затем передайте token и baseUrl через override-поля основной или AI-ноды. Для расписаний и Trigger сохраните готовый X-Auth в GLONASSSoft Token API credentials. Base URL должен быть HTTPS-origin без пути, query, fragment и встроенных логина/пароля.

Основная и AI-ноды принимают параметры через Fields или Raw JSON. В режиме Auto массивы разбиваются на отдельные items, а экспорт возвращается как binary data. Поддерживаются Single Item, Split Items и Binary.

Trigger опрашивает POST /api/v3/vehicles/getlastdata. Первый автоматический запуск сохраняет исходное состояние и ничего не возвращает; последующие возвращают только новые или изменившиеся снимки. Ручной запуск baseline не меняет. Изменение списка объектов или Include Sensors создаёт новый baseline, а временно отсутствующий в ответе объект не считается удалённым.

License

MIT

Discussion