Toolhouse AI Agent icon

Toolhouse AI Agent

Send and continue conversations with Toolhouse agent
Join our community

Actions2

Overview

This node integrates with Toolhouse AI agents to start or continue conversations. It allows users to send messages to a selected Toolhouse agent and receive responses, enabling conversational workflows within n8n.

Common scenarios include:

  • Automating customer support by interacting with AI agents.
  • Integrating AI-driven chatbots into business processes.
  • Continuing multi-turn conversations with an AI agent using a run ID.

For example, you can start a new conversation with a specific AI agent by sending a message, then use the returned run ID to continue the conversation later, maintaining context.

Properties

Name Meaning
Agent Name or ID Select a Toolhouse AI agent from a list or specify its ID. Agents can be public or private.
Message The text message to send to the selected Toolhouse agent.

Note: The "Agent Name or ID" property supports loading available agents dynamically and checking if an agent is public or private.

Output

The node outputs two main JSON fields:

  • response: The response object returned by the Toolhouse agent API, containing the agent's reply or error details.
  • runId: A string representing the current conversation run ID, used to continue conversations.
  • agentId: The ID of the agent involved in the interaction.
  • public: A boolean indicating whether the agent is public (true) or private (false).

If the node encounters an error (e.g., access denied), it outputs an error object with message, status code, and optional details.

The node has two output channels:

  • The first output contains successful responses.
  • The second output contains errors.

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Toolhouse API.
  • Needs network access to https://api.toolhouse.ai/v1 and https://agents.toolhouse.ai.
  • The node uses HTTP requests to communicate with Toolhouse endpoints.

Troubleshooting

  • Missing or invalid API credentials: The node throws an error if the API token is missing or invalid. Ensure the API key credential is configured correctly.
  • Access denied to private agents: If you try to access a private agent without permission, the node returns a 403 error with a message "You do not have access to this private agent." Verify your permissions or use a public agent.
  • Invalid agent ID: Providing an incorrect agent ID will cause HTTP errors. Double-check the agent selection.
  • Run ID required for continuing conversations: When using the "Continue Conversation" operation, ensure the run ID is provided; otherwise, the request will fail.
  • Network issues: Connectivity problems to Toolhouse endpoints will result in request failures.

Links and References

Discussion