Delete Message
rocketchat.delete_message
ActionChat & messagingconnection required
Calls the Rocket.Chat API with the connection's credentials.
Delete a message from a room.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Rocket.Chat
- Secret shape
- the personal access token, or {"token": "…", "user_id": "…"}
- Config it needs
- base_url, user_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
room_id The room id (not its name) — use rocketchat.get_channel_info to resolve one. | string | Yes | — | — | — |
msg_id The message to delete. | string | Yes | — | — | — |
as_user Record the deletion as the message's own author rather than as the connection's user. | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"as_user": false
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
deleted True once Rocket.Chat accepted the deletion. | boolean | — |
msg_id The message that was deleted. | string | — |
room_id The room it was deleted from. | string | — |
ts When the deletion happened, when Rocket.Chat reports it. | string | — |
{
"deleted": false,
"msg_id": "",
"room_id": "",
"ts": ""
}See Delete Message run in a workflow.
In a technical demo we add the Rocket.Chat connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.