Wiresk

Wiresk

Slack – Reactions & Pins

Estimated reading time: 7 min

What your automation will do…

A connection to your Slack account is needed so we can sync it with our platform.
Refer to Slack – Connection
You can include between 1 and 255 Methods to build complex Flows.
This Method is used to add an emoji reaction to a specific message in a Slack channel or conversation.
 
● The emoji name should be a Slack emoji alias, like smile, tada, rocket, white_check_mark — without : colons. Add emojis Alias or custom emoji here.
● You must be able to see the message as the bot or user adding the reaction.
● You can only add a reaction per emoji — Slack will return an error if the user tries to add the same reaction again.

For more detail, see Slack API reference Reactions.add

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*Add Reaction
Connection*Select your connection or create one.

MAP FIELDS

Channel Type*:

Select the Channel Type:

  • Public Channel
  • Private Channel
  • Direct Message

Channel ID*:

Select or enter a channel ID that represents a channel, private group, or IM channel to archive.

Timestamp (Message ID)*:

Use Wiresk Lookup feature to provide the ts. Go to Default value > Lookup tab > search for message).

Or map the ts (message ID) from a step response.

To get the Timestamp (Message ID) from step responses, you can use:

  • Trigger “List Replied Messages“
  • Method “List Messages History“
  • Method “List Replied Messages“
  • Method “Search Messages“

Reaction (emoji) Name*:

The name of the emoji. e.g., thumbsup, tada, rocket)

Add emojis Alias or custom emoji here.

For Unicode emoji that support skin tone modifiers, name may indicate a modifier by appending ::skin-tone- and a number from 2 to 6, like, thumbsup::skin-tone-6 or wave::skin-tone-3. This will add a reaction with the base emoji and the specified skin color.

(*) required field

Response sample 
{
  "message": "Reaction Added successfully"
}
Expand
This Method returns all reactions a user made across the workspace, including:
● Messages
● Files
● File comments

For more detail, see Slack API reference Reactions.list

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*List Reactions
Connection*Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Count:

Number of items to return per page.

Default: 100

Full:

true - false

If true always return the complete reaction list.

User ID:

Show reactions made by this user. Defaults to the authed user.

Get a user ID by using Wiresk Method “List Users“.

Cursor:

Paginate through collections of data by setting the cursor parameter to a next_cursor attribute returned by a previous request’s response_metadata. Default value fetches the first “page” of the collection. See pagination for more detail.

Team ID:

The team_id is only relevant when using an org-level token. This field will be ignored if the API call is sent using a workspace-level token.

(*) required field

Response sample 
[
  {
    "type": "message",
    "channel": "C08THJLDGCE",
    "message": {
      "user": "U08QCLYRD5H",
      "type": "message",
      "ts": "1747996666.349819",
      "client_msg_id": "de1b06eb-1968-4992-944f-82bbc88cd374",
      "text": "message for reaction",
      "team": "T08QCLYQESF",
      "blocks": [
        {
          "type": "rich_text",
          "block_id": "VtzPD",
          "elements": [
            {
              "type": "rich_text_section",
              "elements": [
                {
                  "type": "text",
                  "text": "message for reaction"
                }
              ]
            }
          ]
        }
      ],
      "reactions": [
        {
          "name": "rocket",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08THJLDGCE/p1747996666349819"
    }
  },
  {
    "type": "message",
    "channel": "C08QCLZ5ECB",
    "message": {
      "subtype": "tombstone",
      "text": "This message was deleted.",
      "user": "USLACKBOT",
      "hidden": true,
      "type": "message",
      "ts": "1747629891.904709",
      "thread_ts": "1747629891.904709",
      "parent_user_id": "USLACKBOT",
      "reply_count": 1,
      "reply_users_count": 1,
      "latest_reply": "1747629991.826279",
      "reply_users": [
        "U08QCLYRD5H"
      ],
      "is_locked": false,
      "pinned_to": [
        {
          "id": "C08QCLZ5ECB"
        }
      ],
      "reactions": [
        {
          "name": "raised_hands",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        },
        {
          "name": "heavy_check_mark",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08QCLZ5ECB/p1747629891904709?thread_ts=1747629891.904709&cid=C08QCLZ5ECB"
    }
  },
  {
    "type": "message",
    "channel": "C08QMJ69RS5",
    "message": {
      "user": "U08QCLYRD5H",
      "type": "message",
      "ts": "1746000309.460109",
      "client_msg_id": "9f39df89-525e-4e27-a495-24b7eadc795e",
      "text": "test new channel",
      "team": "T08QCLYQESF",
      "blocks": [
        {
          "type": "rich_text",
          "block_id": "cROrZ",
          "elements": [
            {
              "type": "rich_text_section",
              "elements": [
                {
                  "type": "text",
                  "text": "test new channel"
                }
              ]
            }
          ]
        }
      ],
      "reactions": [
        {
          "name": "white_check_mark",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08QMJ69RS5/p1746000309460109"
    }
  },
  {
    "type": "message",
    "channel": "C08QMJ69RS5",
    "message": {
      "subtype": "channel_join",
      "user": "U08Q2P1AAKY",
      "text": "<@U08Q2P1AAKY> has joined the channel",
      "type": "message",
      "ts": "1746001179.443319",
      "reactions": [
        {
          "name": "white_check_mark",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08QMJ69RS5/p1746001179443319"
    }
  },
  {
    "type": "message",
    "channel": "C08QMJ69RS5",
    "message": {
      "subtype": "bot_add",
      "text": "added an integration to this channel: <https://wiresk-test.slack.com/services/B08PWLZRH63|Wiresk app>",
      "user": "U08QCLYRD5H",
      "bot_link": "<https://wiresk-test.slack.com/services/B08PWLZRH63|Wiresk app>",
      "bot_id": "B08PWLZRH63",
      "type": "message",
      "ts": "1746005834.661249",
      "reactions": [
        {
          "name": "white_check_mark",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08QMJ69RS5/p1746005834661249"
    }
  },
  {
    "type": "message",
    "channel": "C08QCLZ5ECB",
    "message": {
      "user": "U08QCLYRD5H",
      "type": "message",
      "ts": "1746000291.989599",
      "edited": {
        "user": "U08QCLYRD5H",
        "ts": "1746000337.000000"
      },
      "client_msg_id": "7763b62d-0a49-4c9c-a439-87c65614a250",
      "text": "test all wiresk test",
      "team": "T08QCLYQESF",
      "blocks": [
        {
          "type": "rich_text",
          "block_id": "A46Yz",
          "elements": [
            {
              "type": "rich_text_section",
              "elements": [
                {
                  "type": "text",
                  "text": "test all wiresk test"
                }
              ]
            }
          ]
        }
      ],
      "reactions": [
        {
          "name": "heart",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08QCLZ5ECB/p1746000291989599"
    }
  },
  {
    "type": "message",
    "channel": "C08QCLZ5ECB",
    "message": {
      "subtype": "tombstone",
      "text": "This message was deleted.",
      "user": "USLACKBOT",
      "hidden": true,
      "type": "message",
      "ts": "1747629891.904709",
      "thread_ts": "1747629891.904709",
      "parent_user_id": "USLACKBOT",
      "reply_count": 1,
      "reply_users_count": 1,
      "latest_reply": "1747629991.826279",
      "reply_users": [
        "U08QCLYRD5H"
      ],
      "is_locked": false,
      "pinned_to": [
        {
          "id": "C08QCLZ5ECB"
        }
      ],
      "reactions": [
        {
          "name": "raised_hands",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        },
        {
          "name": "heavy_check_mark",
          "users": [
            {
              "id": "U08QCLYRD5H"
            }
          ],
          "count": 1
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08QCLZ5ECB/p1747629891904709?thread_ts=1747629891.904709&cid=C08QCLZ5ECB"
    }
  }
]
Expand
This Method is used to removes an emoji reaction from a message, file, or file comment that was previously added by the calling user or bot. 
 
⚠️ One of file, file_comment, or the combination of channel and timestamp must be specified.

For more detail, see Slack API reference Reactions.remove

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*Remove Reaction
Connection*Select your connection or create one.

MAP FIELDS

Channel Type:

Select the Channel Type:

  • Public Channel
  • Private Channel
  • Direct Message

Channel ID:

Select or enter a channel ID that represents a channel, private group, or IM channel to archive.

Reaction (emoji) Name*:

The name of the emoji (e.g., thumbsup, tada, rocket) to be removed.

Add emojis Alias or custom emoji here.

Timestamp (Message ID):

Use Wiresk Lookup feature to provide the ts. Go to Default value > Lookup tab > search for message).

Or map the ts (message ID) from a step response.

To get the Timestamp (Message ID) from step responses, you can use:

  • Trigger “List Replied Messages“
  • Method “List Messages History“
  • Method “List Replied Messages“
  • Method “Search Messages“

File ID:

File to remove reaction from.

File Comment ID:

File comment to remove reaction from.

If not Found Consider as:

Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

Response sample 
{
  "message": "Reaction Removed successfully"
}
Expand
This Method is used to list items pinned to a channel.

⚠️ This method cannot be called with bot user tokens belonging to Slack apps, although legacy bot tokens will work.
 
You can pin various types of items. Each item in your list has a type that determines its other properties:
● Message: This type includes a message object and the channel ID where the message is located.
● File: This type contains a file object.
● File comment: This type includes a file object and the associated comment on that file.

For more detail, see Slack API reference Pins.List

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*List Pined Messages
Connection*Select your connection or create one.

MAP FIELDS

Channel Type*:

Select the Channel Type:

  • Public Channel
  • Private Channel
  • Direct Message

Channel ID*:

Select or enter a channel ID that represents a channel, private group, or IM channel to archive.

(*) required field

Response sample 
[
  {
    "type": "message",
    "created": "2025-06-02 08:47:33",
    "created_by": "U08QCLYRD5H",
    "channel": "C08QCLZ5ECB",
    "message": {
      "user": "U08QCLYRD5H",
      "type": "message",
      "ts": "1748829600.907229",
      "client_msg_id": "4e52d749-2d0e-45c5-95cb-7220cacc5088",
      "text": "test",
      "team": "T08QCLYQESF",
      "blocks": [
        {
          "type": "rich_text",
          "block_id": "gB9fq",
          "elements": [
            {
              "type": "rich_text_section",
              "elements": [
                {
                  "type": "text",
                  "text": "test"
                }
              ]
            }
          ]
        }
      ],
      "pinned_to": [
        {
          "id": "C08QCLZ5ECB"
        }
      ],
      "permalink": "https://wiresk-test.slack.com/archives/C08QCLZ5ECB/p1748829600907229"
    }
  }
]
Expand
This Method pins a message to a particular conversation or channel.

Some objects cannot be pinned: 
● Channel join messages
● Files
● File comments.

For more detail, see Slack API reference Pins.add

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*Pin a Message
Connection*Select your connection or create one.

MAP FIELDS

Channel Type*:

Select the Channel Type:

  • Public Channel
  • Private Channel
  • Direct Message

Channel ID*:

Select or enter a channel ID that represents a channel, private group, or IM channel to archive.

Timestamp (Message ID)*:

Use Wiresk Lookup feature to provide the ts. Go to Default value > Lookup tab > search for message).

Or map the ts (message ID) from a step response.

To get the Timestamp (Message ID) from step responses, you can use:

  • Trigger “List Replied Messages“
  • Method “List Messages History“
  • Method “List Replied Messages“
  • Method “Search Messages“

(*) required field

Response sample 
{
  "message": "Pined a message successfully"
}
Expand
This Method un-pins an item (file, file comment, channel message, or group message) from a channel.

For more detail, see Slack API reference Pins.remove

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*Un-pin a Message
Connection*Select your connection or create one.

MAP FIELDS

Channel Type*:

Select the Channel Type:

  • Public Channel
  • Private Channel
  • Direct Message

Channel ID*:

Select or enter a channel ID that represents a channel, private group, or IM channel to archive.

Timestamp (Message ID)*:

Use Wiresk Lookup feature to provide the ts. Go to Default value > Lookup tab > search for message).

Or map the ts (message ID) from a step response.

To get the Timestamp (Message ID) from step responses, you can use:

  • Trigger “List Replied Messages“
  • Method “List Messages History“
  • Method “List Replied Messages“
  • Method “Search Messages“

If not Found Consider as:

Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

Response sample 
{
  "message": "Un-pined a message successfully"
}
Expand

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.