Overview
This client-mode connector calls the Slack Web API so plant or ops events on MQTT can approve apps or manage conversations. The packaged events are eight admin methods only (admin.apps.*, admin.conversations.*). It does not include chat.postMessage.
The LoT file still sets
BASE_ADDRESS to https://api.example.com because the source spec did not carry the Slack host. Change it to https://slack.com/api before you deploy. Calls need a Slack token; this template has not been verified against the live API.Basic Syntax
Events
Auth
Slack expects a bot or user token as Bearer:string
required
Set to
https://slack.com/api (the file default is a placeholder).string
required
Slack token with the admin scopes those methods need. Pass it on the MQTT payload. Prefer a Hub secret or
GET SECRET upstream. Never commit the token.{payload} as JSON. Put method arguments in that body (Slack also accepts form bodies; this template uses application/json).
Try it
- Fix
BASE_ADDRESStohttps://slack.com/api, then add the connector on a lab broker. - Publish
{"api_token": "YOUR_SLACK_TOKEN"}tointegrations/slack/request/AdminAppsApprovedList. - Subscribe to
integrations/slack/response/AdminAppsApprovedList. - POST methods: include both
api_tokenand the method fields. The connector body is{payload}, so keep secrets out of logs.
No live Slack call has been recorded for this package (no token on the build host, and no test log).
admin.* methods need a workspace token with admin scopes.
