Skip to main content
Technical Preview
Every REST API app in this catalog is in technical preview.

Overview

These templates are client-mode TYPE REST_API connectors: an MQTT request topic triggers an HTTP call, and the response is published on a matching topic. Start with REST API Connectors for config, auth, and placeholders. This catalog is the app layer on top of that connector. Every app ships with the broker. The connector signs outbound requests itself through CLIENT_AUTH, and reads credentials from broker secrets (GET SECRET). Create the secrets a template needs before you deploy it: a connector whose CLIENT_AUTH secret is empty does not start. The Hub lists these secrets (requiredSecrets) and asks for them before deploying.

Catalog

Apps are grouped by Hub category. An app with several connectors has one app code per connector, each with its own page.
  • Auth is the CLIENT_AUTH mode the template uses. None means the API is public or takes its key in the request.
  • Minimum tier follows the number of actions the connector registers: up to 24 runs on Community, up to 100 needs Growth, more needs Enterprise.

Analytics

CRM

Cloud IoT

Cloud storage

ERP

Energy

Field service

Finance

Fleet

HR

Identity

LLMs

Manufacturing

Maps

Messaging

Monitoring

Payments

Public data

SCADA

Testing

Work and DevOps

Discover connectors

The broker ships every REST API app in this catalog as a connector template. List them all with -listTemplates, and get one template with -routeCode (alias -connectorCode). Publish both commands to $SYS/Coreflux/Command: An app with one connector is keyed by its folder name, upper-cased with every non-alphanumeric run turned into _ (sap-s4hana-cloud becomes SAP_S4HANA_CLOUD). An app with several connectors keys each one by its connector name without the RestApi suffix (GeminiApiRestApi becomes GEMINI_API). The catalog lists every app code. Each card has this shape (from RouteHandler.BuildTemplatePayload):
  • status is beta for every app today: the broker accepts no other value. The docs call this technical preview.
  • license is community when a Community broker can deploy the template, otherwise licensed. minimumTier is Community, Growth or Enterprise, actionSlots is the number of actions the connector registers, and availableOnThisBroker says whether the current license can deploy it.
  • requiredSecrets lists the broker secrets the template reads (GET SECRET or {secret.NAME}). Create them before you deploy.
  • connector is true and baseType is REST_API for every vendor connector. For built-in connector templates connector is false and baseType equals type.
  • An app code is not a connector type: deploy the template with WITH TYPE REST_API, not WITH TYPE AIRTABLE.
  • template is the deployable connector code only. The ADD METADATA block is split off into metadata, because -addRoute rejects it.
  • #Name,type,description,regex,required# markers are Hub placeholders (for example #RouteName# and #BaseUrl#). Replace them with real values before you deploy with -addRoute.
Last modified on October 21, 2026