Overview
This node allows users to create and manage custom tools for CrewAI agents within n8n. It is designed to register a new tool by specifying its name, description, and optionally a webhook URL that acts as a bridge between native n8n tools and the CrewAI tool structure.
Common scenarios where this node is beneficial include:
- Automating the creation of specialized AI tools that can be used by CrewAI agents.
- Integrating external webhook endpoints with CrewAI tools to extend their functionality.
- Managing tool metadata programmatically as part of larger automation workflows.
For example, you might use this node to define a new AI tool named "Data Cleaner" with a description explaining its purpose, and provide a webhook URL that receives data for processing by this tool.
Properties
| Name | Meaning |
|---|---|
| Tool Name | The unique name of the tool being created. This must be unique to identify the tool within CrewAI. |
| Description | A detailed explanation of what the tool does and when it should be used. |
| Webhook URL | (Optional) A URL endpoint to receive webhook data for this tool, enabling integration between n8n and CrewAI tool structure. |
| Report Issue | Notice with links to report bugs or get help related to this node. |
| Request Feature | Notice with links to request new features or enhancements for this node. |
Output
The node outputs a single item containing JSON data about the newly created tool:
{
"toolId": "string", // The unique identifier of the created tool (from CrewAI)
"name": "string", // The name of the tool
"description": "string", // The description of the tool
"webhookUrl": "string" // The webhook URL provided (if any)
}
This output can be used downstream in your workflow to reference the created tool or to confirm successful creation.
Dependencies
- Requires an API key credential for authenticating with the CrewAI API.
- The node makes a POST request to the
/toolsendpoint of the CrewAI API to create the tool. - No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
- Missing Required Fields: If "Tool Name" or "Description" is empty, the node will throw an error indicating these fields are required. Ensure these inputs are provided.
- API Request Failures: Network issues or invalid API credentials may cause the request to fail. Verify your API key and network connectivity.
- Webhook URL Issues: If the webhook URL is malformed or unreachable, the tool creation might still succeed but integration will fail at runtime.
- Error Handling: If the node is set to continue on failure, errors will be returned in the output JSON under an
errorfield instead of stopping execution.