Skip to main content
Technical Preview

Overview

A client-mode connector for a curated CRM / Field Service / IIoT bridge slice of the Salesforce REST API under https://YOUR_INSTANCE.my.salesforce.com/services/data/v62.0/: BASE_ADDRESS is the org instance URL from the OAuth token response (no trailing slash). Topics use crm/salesforce/<object>/<verb>.
Use the instance_url returned with the access token (for example https://mycompany.my.salesforce.com). login.salesforce.com and test.salesforce.com are for OAuth token exchange only — calling /services/data/ on the login host returns URL_NOT_RESET.
API version is pinned to v62.0 (Hugo catalog base_url). Bump the path version in the .lot when you standardize on a newer org API version. Bulk 2.0 and Pub/Sub (gRPC) are out of scope for this REST_API client template. Prefer Hub secrets for tokens. This template has not been verified against a live org.

Basic Syntax

Events

Auth

OAuth 2.0 Bearer access token — default in the template:
  1. In Salesforce Setup, create a Connected App with the OAuth scopes your integration needs (at least API access).
  2. Obtain an access_token (authorization code, JWT bearer, or client credentials where the org enables it).
  3. Set connector BASE_ADDRESS to the token response instance_url (My Domain host).
  4. Pass access_token on the MQTT request payload so headers resolve:
    • Authorization: Bearer {value.json.access_token}
  5. Store the token in Hub secrets / GET SECRET. Never commit real credentials.

Example payloads

List sObjects (smoke): include access_token on the MQTT JSON root used for header substitution. SOQL:
Create Case:
PATCH Asset: path uses assetId; body is the field map. Platform Event: set eventName to the API name ending in __e (for example DeviceAlert__e); body is the event field map.

Deploy notes

Last modified on October 21, 2026