Description

n8n-nodes-agencii

This is an n8n community node for the Agencii.ai Platform. It connects your n8n workflows to your agency-swarm powered agencies on the Agencii.ai platform.

Agencii.ai is an AI automation platform that uses agency-swarm to provide infrastructure for building and deploying AI agent agencies. The platform enables you to create multi-agent systems where specialized agents work together to accomplish complex tasks.

n8n is a fair-code licensed workflow automation platform.

How It Works

This integration connects your n8n workflows directly to your agencies on the Agencii.ai platform:

1. Platform Configuration: In your Agencii.ai dashboard, you configure n8n integration settings for your agency
2. Integration ID: Each agency gets a unique n8n integration ID that identifies which agency to route requests to
3. Default Agent Routing: When you send a message through this node, the platform routes it to your agency’s default agent
4. Agency-Swarm Processing: Your agency (powered by agency-swarm) processes the request using its configured agents and tools
5. Response: The agency’s response is returned to your n8n workflow for further processing

Table of Contents

• How It Works
• Installation
• Operations
• Design Principles
• Credentials
• Usage
• Compatibility
• Resources
• Version History

Installation

Follow the installation guide in the n8n community nodes documentation.

Quick Install

1. Go to Settings > Community Nodes in your n8n instance
2. Select Install
3. Enter n8n-nodes-agencii
4. Agree to the risks and select Install

After installation, the Agencii node will be available in your node palette.

Operations

The Agencii node supports the following operation:

Send Message

Send a message to your agency on the Agencii.ai platform and receive a response from your agency’s default agent.

Parameters:

• Message (required): The message or task to send to your agency
• Session ID (optional): Identifier to continue an existing conversation. If not provided, a new session is created automatically.
• Integration ID (required): The specific Integration ID for the agency you want to connect to

Note: Model selection, temperature, max tokens, tools, and agent behavior are configured on the Agencii.ai platform (see Agency Swarm Overview).

Returns:

• text: The agency’s response to your message
• response: Alias for text (for backwards compatibility)
• sessionId: The session identifier (for continuing the conversation in follow-up calls)
• n8nIntegrationId: The integration ID used
• Additional metadata fields as provided by the backend

Design Principles

• Connectivity, not configuration:

– This node connects n8n to your agencies on the Agencii.ai platform. It does not configure agent behavior.

• Platform-managed tuning:

– Model, temperature, max tokens, system prompts, tools, and multi-agent logic are defined on the platform.

• Fixed endpoint:

– The endpoint is fixed and not user-editable in this node. Routing to the correct agency is handled via your Integration ID.

• Default agent routing:

– Messages are routed to your agency’s default agent unless otherwise configured on the platform.

• Session-focused:

– Provide Session ID to continue context; omit it to start a new session automatically.

Credentials

To use this node, you need to configure your Agencii.ai Platform credentials:

Prerequisites

1. Sign up for an Agencii.ai account at agencii.ai
2. Get your API key from your Agencii dashboard
3. For each workflow, you’ll need the specific Integration ID for the agency you want to connect to

Setting Up Credentials in n8n

1. In n8n, go to Credentials and click Add Credential
2. Search for Agencii API and select it
3. Fill in the following field:
– API Key: Your Agencii.ai API key for authentication
4. Click Save

Configuring Each Node

Each Agencii node instance requires an Integration ID parameter that specifies which agency to connect to. This allows you to:

• Connect different nodes to different agencies in the same workflow
• Reuse the same API credentials across multiple agencies
• Easily switch between agencies by changing the Integration ID parameter

Authentication Method

The node uses Bearer token authentication (API Key in header) and sends your Integration ID as a URL query parameter to route requests to the correct agency on the Agencii.ai platform.

Usage

Single Request

Use the Send Message operation to send a single message to your agency and receive a response.

Example Use Case: Task execution via agency

1. Add an Agencii node to your workflow
2. Select Resource: Chat
3. Select Operation: Send Message
4. Set Integration ID: Your agency's Integration ID from Agencii dashboard
5. Set Message: "Analyze the customer feedback data and provide a summary: {{$json.feedbackData}}"
6. Leave Session ID empty (a new session will be created automatically)

Result: Your agency processes the request using its configured agents and tools, returning the result.

Multi-Turn Conversation

For conversational workflows where context matters, reuse the sessionId from previous calls in subsequent Send Message calls to maintain session continuity.

Example Use Case: Interactive data analysis with context

Step 1: Initial request
Add an Agencii node
Select Resource: Chat
Select Operation: Send Message
Set Integration ID: Your agency's Integration ID
Set Message: "Analyze this sales data and identify trends: {{$json.salesData}}"
Leave Session ID empty (stores the sessionId in output)
Step 2: Follow-up questions
Add another Agencii node
Select Resource: Chat
Select Operation: Send Message
Set Integration ID: Same Integration ID as Step 1
Set Message: "Based on those trends, what should our Q4 strategy be?"
Set Session ID: {{$node["Previous Node"].json.sessionId}}
Your agency will remember the previous analysis and provide contextual recommendations

Benefits:

• Your agency maintains conversation context across multiple interactions
• More natural and contextual task execution
• Efficient processing as the agency remembers prior exchanges

Advanced Patterns

#### Conditional Session Management

Use an IF node to check if a sessionId exists. If yes, reuse it for conversation continuity; if no, a new session will be created automatically.

#### Session Persistence

Store sessionId values in n8n’s built-in data storage or an external database to maintain long-running conversations with your agency across multiple workflow executions.

Understanding Agency Routing

When you send a message through this node:

1. Your Integration ID identifies which agency to route to
2. The message is sent to your agency’s default agent (configured in Agencii.ai platform)
3. Your agency, powered by agency-swarm, coordinates between its agents to process the request
4. Each agent has specific tools and capabilities configured in your agency setup
5. The agency returns the final response to your n8n workflow

Note: Agent behavior, system prompts, tools, and capabilities are all configured within the Agencii.ai platform, not in this n8n node. The node simply connects n8n to your pre-configured agency.

Compatibility

• Minimum n8n version: 1.0.0
• Tested on: n8n v1.0.0+
• Node API Version: 1

This node uses n8n’s declarative routing feature for simplified API integration.

Resources

• n8n Documentation
• n8n Community Nodes
• Agencii.ai Platform
• Agency Swarm Overview
• Agency-Swarm Framework
• Agencii.ai Documentation

Support

For issues, questions, or feature requests:

• Open an issue on GitHub
• Join the n8n community

Version History

0.1.0 (Initial Release)

• ✨ Initial implementation of Agencii.ai Platform integration for n8n
• 🚀 Support for Send Message operation: Send messages to your agency-swarm powered agencies
• 🔐 Secure API authentication via Integration ID (routes to specific agency)
• 🤖 Direct integration with agency-swarm infrastructure on Agencii.ai
• 📊 Response includes text, response (alias), and sessionId fields
• 💬 Session management for multi-turn conversations with agencies
• 📝 Comprehensive documentation and workflow examples

License

MIT

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.