Rocket.Chat

Node catalog Actions

On this page

Send, read and manage Rocket.Chat messages.

Usage and specifics

Use an action credential or a separate webhook credential according to the node. To receive events, publish and configure the HTTPS URL, events and permissions in the service. The test payload is a normalized event and does not validate connectivity. Output preserves the provider payload.

Technical type : rocketchat. Runtime : nodulz.

Credentials and prerequisites

Rocket.Chat (integration / rocketchat). Server URL, user ID and Rocket.Chat personal access token, stored in the encrypted credential.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`operation`	`enum`	`"send"`	`send`, `update`, `delete`, `get`, `history`, `replies`, `channels`, `spaces`, `react`, `template`, `media`, `read`
`channelId`	`string`	`""`	-
`messageId`	`string`	`""`	-
`text`	`string`	`""`	-
`threadId`	`string`	`""`	-
`recipient`	`string`	`""`	-
`sender`	`string`	`""`	-
`emoji`	`string`	`""`	-
`templateName`	`string`	`""`	-
`language`	`string`	`"fr"`	-
`mediaType`	`enum`	`"image"`	`image`, `video`, `audio`, `document`
`mediaUrl`	`string`	`""`	-
`apiVersion`	`string`	`"v23.0"`	-
`cursor`	`string`	`""`	-
`limit`	`number`	`20`	-; ≥ 1, ≤ 100
`data`	`string`	`"{}"`	-

Configuration help

operation Action: Choose an action supported by this integration. The token still needs the appropriate permissions.
data Additional API parameters (JSON): JSON object merged into the request. Form fields take priority. Examples: blocks for Slack, props for Mattermost, cardsV2 for Google Chat, template.components for WhatsApp, base64_attachments for Signal.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "operation": "send",
  "channelId": "",
  "messageId": "",
  "text": "",
  "threadId": "",
  "recipient": "",
  "sender": "",
  "emoji": "",
  "templateName": "",
  "language": "fr",
  "mediaType": "image",
  "mediaUrl": "",
  "apiVersion": "v23.0",
  "cursor": "",
  "limit": 20,
  "data": "{}"
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.