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 operation deletes a relation in a specified collection within a database or data management system. It is useful when you want to remove an existing relational link between collections, such as unlinking related records or cleaning up schema relationships.
Practical examples include:
- Removing a foreign key relationship between two tables.
- Deleting a reference field that connects one collection's record to another.
- Cleaning up outdated or incorrect relational mappings in your data model.
Properties
| Name | Meaning |
|---|---|
| Collection Name | Unique name of the parent collection where the relation exists. Example: "books". |
| Field Name | Name of the field in the collection that holds the related primary key (the relational link). Example: "author". |
Output
The output JSON typically contains the result of the delete operation, such as confirmation of deletion or status information. The exact structure depends on the underlying API response but generally confirms whether the relation was successfully deleted.
No binary data output is expected from this operation.
Dependencies
- Requires access to the target database or API managing collections and relations.
- Needs appropriate authentication credentials (e.g., an API key or token) configured in n8n to authorize deletion operations.
- The node uses dynamic loading methods to fetch available collections and relational fields for user selection.
Troubleshooting
Common issues:
- Attempting to delete a relation that does not exist or specifying incorrect collection or field names.
- Insufficient permissions or missing authentication credentials leading to authorization errors.
- Network or connectivity problems preventing communication with the backend service.
Error messages:
- "Relation not found" or similar indicates the specified relation does not exist; verify collection and field names.
- "Unauthorized" or "Authentication failed" suggests invalid or missing API credentials; check credential configuration.
- Timeout or connection errors imply network issues; ensure the service endpoint is reachable.
Links and References
- Refer to your backend service or API documentation for details on managing relations and required permissions.
- Consult n8n documentation on setting up API credentials and using options loading methods for dynamic property values.