Agentic Hub Message icon

Agentic Hub Message

Send messages to Agentic Hub API for conversational AI workflows

Overview

This node, Agentic Hub Message, is designed to send messages to the Agentic Hub API, which supports conversational AI workflows. It facilitates communication by posting conversation and message data to a specified API endpoint. This is useful in scenarios where you want to integrate AI-driven conversations into your workflows, such as chatbots, customer support automation, or AI-assisted messaging systems.

Practical examples:

  • Sending user queries to an AI service and receiving responses.
  • Logging conversation metadata like sentiment scores and human attention flags.
  • Tracking conversations by session and phone number for personalized interactions.

Properties

Name Meaning
API URL The API endpoint URL to which the conversation data will be sent.
Workflow ID Numeric identifier of the workflow managing the conversation.
Session ID Unique string identifying the conversation session.
Phone Number Phone number associated with the conversation.
Query/Message The actual message content to send (user query or AI response).
Direction Indicates message direction:
- 1: Question from user to AI
- 0: Answer from AI to user
Additional Options Collection of optional parameters:
- Overall Sentiment (number): Sentiment score for the entire conversation.
- Sentiment Score (number): Sentiment score for this specific message.
- Requires Human Attention (boolean): Flag indicating if human intervention is needed.
- Order ID (number): Associated order ID if applicable.

Output

The node outputs an array with one item per input. Each output item contains a json object structured as follows:

  • success: Boolean indicating if the request was successful.
  • response: The raw response returned by the Agentic Hub API.
  • requestBody: The JSON payload sent to the API, including conversation and message details.
  • timestamp: ISO timestamp when the request was made.

If the request fails and "Continue On Fail" is enabled, the output includes:

  • success: false
  • error: Error message describing the failure.
  • timestamp: ISO timestamp of the error occurrence.

The node does not output binary data.

Dependencies

  • Requires access to the Agentic Hub API endpoint specified by the user.
  • Needs network connectivity to the provided API URL.
  • No internal credential types are referenced; users must provide the full API URL and any necessary authentication externally if required by the API.
  • No additional environment variables or n8n configurations are mandated by the node itself.

Troubleshooting

  • Common issues:

    • Incorrect or unreachable API URL leading to network errors.
    • Missing or invalid required parameters such as sessionId, phoneNumber, or query.
    • API returning errors due to malformed request body or server-side issues.

  • Error messages:

    • Network or HTTP errors will be surfaced with their message in the output's error field if "Continue On Fail" is enabled.
    • If "Continue On Fail" is disabled, the node will throw an error stopping execution, indicating the item index that caused the failure.

  • Resolutions:

    • Verify the API URL is correct and accessible.
    • Ensure all required fields are populated correctly.
    • Check API documentation for expected request format and authentication requirements.
    • Enable "Continue On Fail" during testing to capture error details without halting the workflow.

Links and References

Discussion