Overview

The Slack Message Reader node retrieves messages, threads, sender details, and attachments from Slack channels. It supports triggers for automation and can be customized to filter and fetch specific data for your workflows.


How To Use

  1. Authenticate with Slack

    • Go to the Credentials page.
    • Authenticate and allow access under “Read & Send Slack Messages.”
  2. Add Gumloop to Your Slack Channel

    • In Slack, type /invite @Gumloop in the desired channel and press enter.
  3. Configure the Node

    • Select the target channel.
    • Set message count or define a date range.
    • Choose data to retrieve (e.g., message content, thread IDs, sender names, attachments).
    • Use More Options:
      • Ignore Bot Messages: Exclude bot-generated messages.
      • Read Full Thread: Fetch and process entire threads.
  4. Configure Inputs

    • Use the Configure Inputs panel (accessible on hover) to expose the following fields as inputs for dynamic configuration:
      • Channel
      • Message Count
      • Date Range (requires “Use Dates” option).

Inputs

  • Channel: Target Slack channel.
  • Message Count: Number of messages to fetch (default: 10).
  • Date Range (Optional): Start and end dates for filtering.
  • Message Information: Specify data to retrieve, including content, thread IDs, sender names, and attachments.

Outputs

Outputs are provided as lists if message count is greater than 1 for easy integration with downstream nodes:

  • Messages: Message content.
  • Thread IDs: Unique thread identifiers (can be passed directly to the Slack Sender or the Slack Canvas Writer node to share messages in a thread).
  • Sender Names: Authors of the messages.
  • Attachments: Attached files or media.

Features

  • Ignore Bot Messages: Focus on human-generated content.
  • Read Full Thread: If checked, the node will fetch and process the full thread for each message.
  • Activate as flow trigger: Start flows when new messages are posted.

    Note: Thread messages will also activate the trigger.


Use Cases

  • Monitor Communications: Track discussions or updates.
  • Save Key Information: Archive announcements or resources.
  • Organize Feedback: Collect and analyze team or user feedback.
  • Automate Responses: Trigger workflows for customer support or notifications.

The Slack Message Reader node offers a streamlined approach to accessing Slack content, enabling efficient data management and automation.