Actions100
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Item Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This node is designed to delete a specific field from a collection in a data management system. It is useful when you want to remove unwanted or obsolete fields from your collections, helping maintain clean and relevant data structures. For example, if you have a collection of articles and decide that a certain metadata field is no longer needed, this node can be used to delete that field safely.
Properties
| Name | Meaning |
|---|---|
| Field Name | The unique name of the field to delete within the specified collection. |
| Collection Name | The name of the collection from which the field will be deleted. |
Output
The output JSON typically contains the result of the deletion operation, such as confirmation of success or details about the deleted field. There is no indication that binary data is involved in this operation.
Dependencies
- Requires an API key or authentication token to access and modify collections.
- Depends on external methods for loading options dynamically (e.g., available collections and fields).
- The node uses an internal router method to handle the execution logic.
Troubleshooting
- Field Not Found: If the specified field does not exist in the collection, the node may throw an error indicating the field was not found. Verify the field name is correct and exists in the target collection.
- Collection Not Found: An error may occur if the collection name is invalid or does not exist. Ensure the collection name is accurate.
- Permission Issues: Lack of proper permissions or invalid API credentials can cause authorization errors. Confirm that the API key or authentication token has sufficient rights to delete fields.
- Network or API Errors: Connectivity issues or API downtime might lead to request failures. Check network status and API availability.
Links and References
- Refer to the official API documentation of the data management system for detailed information on deleting fields.
- Consult n8n documentation on how to configure API credentials and manage collections.