Chatbot AI per la generazione di lead HubSpot
Questo flusso di lavoro alimentato da AI automatizza la qualificazione dei lead e la gestione dei contatti in HubSpot. Il chatbot raccoglie informazioni dell'ut...
4 min di lettura
The Hubspot New Message Received component is designed to act as a trigger within your AI workflow whenever a new message is received from HubSpot. This component allows you to integrate and automate actions based on incoming HubSpot messages, making it valuable for process automation, customer support, or lead management scenarios.
Purpose and Functionality
This component listens for new messages arriving in HubSpot and then passes the message along your workflow for further processing. It’s typically used as the starting point (input node) in a flow, enabling downstream components to act upon new customer or contact interactions.
Inputs
| Input Name | Type | Description | Required | Advanced | Visible |
|---|---|---|---|---|---|
| Text | Message (str) | Message to be passed as input. | No | No | No |
| Thread Owner | Dynamic Single Select | The owner of the thread. Populated dynamically from your HubSpot actors. | No | Yes | Yes |
- Text: Represents the content of the incoming message. This is typically managed internally and does not require manual input.
- Thread Owner: Allows you to specify or filter by the owner of the message thread. This field is dynamically populated from your HubSpot account and is useful for routing or assigning messages based on ownership.
Outputs
The component emits the following output:
| Output Name | Type | Description |
|---|---|---|
| Non-Agent Message | Message | The received message for further processing in the workflow. |
- Non-Agent Message: This output contains the actual message received from HubSpot. It can be connected to other components in your workflow, such as sentiment analysis, auto-reply, or CRM update modules.
Key Features
- Event Trigger: Initiates your workflow upon receipt of a new HubSpot message.
- Thread Ownership Filtering: Optionally filter or route messages based on the message thread owner.
- Workflow Integration: Easily send incoming messages to AI or automation modules for further analysis or action.
Use Cases
- Customer Support Automation: Automatically trigger AI responses or agent notifications when a customer message is received.
- Lead Management: Route new leads or inquiries to the appropriate owner or system based on the message’s thread owner.
- Data Logging & Analytics: Capture incoming messages for tracking, analysis, or reporting within your workflows.
Summary
Hubspot New Message Received is a foundational component for integrating HubSpot message events into your AI-powered workflows. By acting as a trigger on new messages, it enables seamless automation and response mechanisms, enhancing the efficiency and responsiveness of your processes.
Note: This component requires a HubSpot integration. Haven’t set it up yet? Start with this quick guide.
What Is The HubSpot New Message Received Component?
This component represents the start of the conversation with FlowHunt. Think of it as the Chat Input component, but it listens to HubSpot inbox messages instead of chat messages.
Component Handles
This component includes only one output handle, representing the message sent by the chatbot user. Since this component is always at the start of a Flow or a subflow, there is no input handle.
- Non-Agent Message – The message sent by the customer, not the agent.
Component Settings
- Thread Owner – This optional setting allows you to have FlowHunt only answer for a specific user. If left as default, FlowHunt will answer all threads. We recommend setting up a new user for FlowHunt and auto-assigning chats to that user.
Want to see this component in action as part of a full chatbot setup? Check out our HubSpot chatbot guide.
