Actions30
- Dataset Actions
- Document Actions
- Segment Actions
- Metadata Actions
Metadata → Bind Tag
AI-generatedOverview
The node manages metadata tags within a knowledge base system, specifically allowing users to bind tags to documents. This operation is useful for organizing and categorizing documents by associating them with relevant tags, which can later facilitate searching, filtering, or applying specific workflows based on tag membership.
A practical example: Suppose you have a dataset of research papers and want to label certain documents with tags like "Machine Learning," "Data Science," or "AI Ethics." Using this node's Bind Tag operation, you can attach these tags to individual documents, enabling easier retrieval and management.
Properties
| Name | Meaning |
|---|---|
| Dataset ID | The unique identifier of the dataset containing the document. |
| Document ID | The unique identifier of the document to which tags will be bound. |
| Tag IDs | A comma-separated list of tag identifiers that should be bound (attached) to the document. |
Output
The output JSON contains the result of the bind tag operation, typically reflecting the updated state of the document's metadata or confirmation of successful binding. It may include details such as the document ID, the tags now associated with it, or status messages.
This node does not explicitly output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Dify AI knowledge base service.
- Needs the base URL of the Dify API configured in the node credentials.
- Relies on the external Dify Knowledge Base API to perform operations on datasets, documents, and metadata.
Troubleshooting
Common issues:
- Invalid or missing Dataset ID, Document ID, or Tag IDs can cause failures.
- Incorrectly formatted Tag IDs (not comma-separated) may lead to errors.
- Network or authentication errors if API key or base URL are misconfigured.
Error messages:
"The operation "bindTag" is not supported for resource "metadata": Indicates a possible typo or unsupported operation; verify operation name.- Errors related to authorization usually mean the API key is invalid or expired.
- If the node throws errors about missing parameters, ensure all required fields (Dataset ID, Document ID, Tag IDs) are provided.
Links and References
- Dify AI Knowledge Base Documentation (general reference for API capabilities)
- n8n Documentation on Creating Custom Nodes