Remove Reaction
mattermost.remove_reaction
ActionChat & messagingconnection required
Calls the Mattermost API with the connection's credentials.
Remove an emoji reaction from a post.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Mattermost
- Secret shape
- the personal access token, or {"token": "…"}
- Config it needs
- base_url, team_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 |
|---|---|---|---|---|---|
post_id The post to take the reaction off. | string | Yes | — | — | — |
emoji_name The emoji name, with or without colons. | string | Yes | — | — | white_check_mark |
user_id Whose reaction to remove. Defaults to the connection's own user. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"emoji_name": "white_check_mark"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
removed True when Mattermost removed the reaction. | boolean | — |
post_id The post that was changed. | string | — |
emoji_name The emoji that was removed. | string | — |
user_id The user whose reaction was removed. | string | — |
{
"emoji_name": "",
"post_id": "",
"removed": false,
"user_id": ""
}See Remove Reaction run in a workflow.
In a technical demo we add the Mattermost connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.