Overview
A client-mode connector for a curated slice of InfluxDB (OSS and Cloud v2) plus InfluxDB 3 HTTP write/query:
Default
BASE_ADDRESS is https://YOUR_INFLUXDB_HOST (no trailing slash). Cloud example: https://{region}.cloud2.influxdata.com. OSS often http://host:8086 — set USE_SSL "false" when not TLS. Topics use data/influxdb/<object>/<verb>.
See the base guide: REST API Connectors.
Auth scheme: use
Authorization: Token <token> — not Bearer. Prefer Hub secrets (GET SECRET "INFLUXDB_TOKEN" or "INFLUX_TOKEN").Line protocol:
PostWrite and PostWriteLpV3 send the MQTT payload as the HTTP body with Content-Type: text/plain; charset=utf-8. Build measurement lines upstream (Telegraf MQTT consumer, LoT action, or edge agent).Factory live smoke used ephemeral local
influxdb:2.7 (PostWrite → 204, Flux PostQuery → 200). Point BASE_ADDRESS at your Cloud or OSS host before production use.Basic Syntax
InfluxdbRestApi.lot under the broker templates tree after you push feat/rest-api-route-influxdb.
Auth and placeholders
Template reference
Generated from the shipped broker templateinfluxdb (-routeCode INFLUXDB). It lists every event the template defines.
Auth
Authorization: Token {value.json.api_token} (InfluxDB API token / operator token). Prefer GET SECRET INFLUXDB_TOKEN or INFLUX_TOKEN. Never commit real credentials. Not Bearer. Auth headers used by the template:Authorization: Token {value.json.api_token}.
Template parameters
BASE_ADDRESS default: https://YOUR_INFLUXDB_HOST.
Events
Deploy
Get the template card (JSON withtemplate and metadata) from the broker, then deploy the connector:
BASE_ADDRESS already filled in:
-addRoute (do not include ADD METADATA).
Usage example
CallGetHealth by publishing a JSON payload to its request topic, and read the reply on the response topic:

