Input & Output

Input Shape

Every operation on this node reads its configuration through the same three-tier pattern:

1. Routing keys — resource and operation select which of the 42 feature partials handles the call.
2. Credential keys — botToken (inline) or credentialID (vault). message/search and user/updateProfile use a user-level token instead — see Authentication & Setup.
3. Operation-specific fields — documented per-operation on the five resource pages (Message, Channel, File, Reaction, User, User Group).

Each operation is backed by a settings DTO (e.g. SendMessageInfo, ChannelCreateInfo) whose LoadFrom(ConfigDataPropertyBag) method reads the config keys, and whose Validate() method reports the first missing/invalid field.

Output Ports

Every Slack node instance is created with two output ports via GetOrCreatePortSuccessAndError():

Standard Success Shape

Every successful operation writes at minimum:

{
  "status": "success",
  "resource": "message",
  "operation": "send",
  "items": [ { /* operation-specific result fields */ } ]
}

The items array wraps the operation's specific result object so downstream nodes can iterate it uniformly, regardless of whether the operation returns a single record (e.g. message/send) or a list (e.g. channel/getMany).

Standard Error Shape

{
  "status": "error",
  "errorCode": "MISSING_BOT_TOKEN",
  "resource": "message",
  "operation": "send",
  "message": "botToken is required"
}