Overview
A client-mode connector for a curated MES slice of the Tulip public API, aligned to Hugo catalog #136:BASE_ADDRESS is the instance root (https://YOUR_INSTANCE.tulip.co, no trailing slash). Topics use mes/tulip/<object>/<verb>. Interactive OpenAPI is also on each instance at /apiDocs.
See the base guide: REST API Connectors.
Auth: HTTP Basic with a Tulip API Token — username = token key, password = token secret. Prefer Hub secrets (
TULIP_API_KEY / TULIP_API_SECRET) or pass Authorization: Basic {value.json.basic_b64} on each MQTT payload. Never commit real tokens. Typical scopes: tables:read, tables:write, attributes:report.For global API tokens, provide workspace context with path prefix
/api/v3/w/{workspaceId}/… or header X-Tulip-Workspace-ID. Workspace-scoped tokens infer the workspace. The first workspace is often DEFAULT.This template has not been verified against a live authenticated Tulip tenant. Status remains blocked until an authenticated live smoke succeeds (prefer GET
/api/v3/tables → 200, then GET records → 200).Basic Syntax
MQTT payload examples
List tables (smoke):payload (must include id):
References
Template reference
Generated from the shipped broker templatetulip (-routeCode TULIP). It lists every event the template defines.
Auth
HTTP Basic (Tulip API Token key as username + secret as password). Prefer Hub secrets TULIP_API_KEY / TULIP_API_SECRET or Authorization: Basic {value.json.basic_b64}. Never commit real credentials. Scopes: tables:read, tables:write, attributes:report. Auth headers used by the template:Authorization: Basic {value.json.basic_b64}.
Template parameters
BASE_ADDRESS default: https://YOUR_INSTANCE.tulip.co.
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
CallListtables by publishing a JSON payload to its request topic, and read the reply on the response topic:

