Správa zo Slacku prijatá

This component represents the user message at the start of a Slack conversation with FlowHunt. You can think of it as a trigger component or an Input component. It lets you control when, where, and how Flo’s Slack responses are triggered.

Using this component requires an active Slack Integration. If you haven’t integrated Slack yet, follow this guide.

Slack Message Received Component

The Slack Message Received component is a trigger node designed for AI workflows that need to react to incoming Slack messages. It allows your workflow to listen for messages in specific Slack channels and respond or process them further as part of your automation.

What Does This Component Do?

This component listens for messages sent to selected Slack channels within a specified Slack workspace. When a message is received, it triggers the rest of your workflow, passing along the content and metadata of the message for downstream processing. It’s especially useful for integrating Slack communications with AI-driven processes, such as chatbots, notifications, or data logging.

• After Bot Stop: Controls what happens after the bot has been manually stopped via Slack.
• After Bot Start: Controls what happens after the bot has been started via Slack.
• Plain message: Controls what happens after the Slack user (you) sends a message.

Component Settings

• Channel: Pick the channels to which you want to add FlowHunt.
• Workspace: Pick the workspace to which you want to add FlowHunt.

Setting up channels and workspace is necessary for the Flow to work.

Inputs

Note: Some fields, such as “Slack Message”, are primarily used for internal message passing within the workflow and are not displayed to end users.

Outputs

When a message is received, the component produces several outputs that can be used by subsequent nodes in your workflow:

These outputs provide flexibility in how your workflow handles different message events from Slack.

Why Use This Component?

• Automate Slack Interactions: Seamlessly connect Slack conversations with automated workflows, such as customer support bots, ticketing systems, or internal notifications.
• Conditional Triggers: Use the “Only Trigger on Mention” option to ensure your workflow only responds when directly addressed, reducing noise and unnecessary processing.
• Multi-Channel Support: Monitor multiple channels at once (up to 5), making it easy to centralize communication handling across teams or projects.
• Integration Ready: Designed to work within broader AI or automation workflows, passing messages and metadata downstream for further processing, enrichment, or response.

Typical Use Cases

• Building AI-powered Slack bots that respond to user queries.
• Sending incoming Slack messages to an AI model for analysis (e.g., sentiment, categorization).
• Triggering downstream automation (e.g., creating tasks, sending notifications) based on Slack messages.
• Logging conversations for compliance or analytics.

This component is essential for anyone looking to build intelligent, responsive Slack integrations as part of an AI-driven process.

Only Trigger on Mention

This setting controls how you trigger an answer from FlowHunt:

• If left unchecked, Flo will respond to every single message sent in the selected channel or thread. This is great for channels used only to talk to FlowHunt, such as Customer Service Chatbot channels. You shouldn’t use this in internal populated channels where people talk to each other, as FlowHunt will annoyingly barge in on any and all conversations.
• If checked, the bot won’t respond unless called on. You can call on Flo by using the @flowhunt mention. We recommend using this when you need quick help retrieving or summarizing information, especially in populated channels.