Actions14
- Agent Actions
- File Actions
- Image Actions
- Prompt Actions
- RAG Actions
Overview
The "Add RAG" operation for the Agent resource in this node allows users to associate a Retrieval-Augmented Generation (RAG) instance with a specific agent. This is useful when you want an agent to leverage external knowledge bases or document collections managed as RAGs to enhance its responses or capabilities.
Typical use cases include:
- Enhancing a conversational AI agent by linking it to a RAG that contains domain-specific documents.
- Dynamically updating an agent's knowledge base by adding new RAGs without recreating the agent.
- Managing multiple RAGs across different agents for specialized tasks.
For example, if you have an agent handling customer support, you can add a RAG containing product manuals and FAQs to improve the quality of automated answers.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent to which the RAG will be added. Example: agent_123456789 |
| RAG ID | The unique identifier of the RAG instance to add to the agent. |
Output
The output JSON contains the response from the Straico API after attempting to add the specified RAG to the agent. It typically includes confirmation details such as success status, updated agent information, or error messages if the operation failed.
Example output structure (simplified):
{
"success": true,
"agent_id": "agent_123456789",
"rag_added": {
"id": "rag_987654321",
"name": "Example RAG"
}
}
The exact fields depend on the API response but generally confirm the association of the RAG with the agent.
Dependencies
- Requires an active connection to the Straico API via an API key credential configured in n8n.
- The node uses HTTP requests authenticated with this credential to communicate with the Straico backend.
- No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Agent ID or RAG ID parameters will cause the request to fail.
- Network connectivity problems or incorrect API credentials will result in authentication errors.
- Attempting to add a RAG that does not exist or is already linked may return an error from the API.
Error messages and resolutions:
"No binary data property ... found on item!": Not applicable for this operation since it does not handle binary data.- API errors indicating unauthorized access usually mean the API key credential is invalid or expired; reconfigure the credential.
- Errors about missing parameters indicate that required inputs like Agent ID or RAG ID were not provided; ensure these are set correctly.
Links and References
- Straico API Documentation: https://docs.straico.com/api-reference
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- Retrieval-Augmented Generation (RAG) Concept Overview: https://en.wikipedia.org/wiki/Retrieval-augmented_generation