Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation deletes a specific Relation by its unique identifier. It is useful in scenarios where you need to remove outdated or incorrect relational data from your system, such as unlinking entities or cleaning up records that are no longer relevant.
For example, if you have a database of customer relationships and want to delete a particular relation entry by its ID, this node operation allows you to do so programmatically within an n8n workflow.
Properties
Name | Meaning |
---|---|
Id | The unique numeric identifier of the Relation to be deleted. This property is required to specify which Relation record should be removed. |
Output
The output JSON will typically contain confirmation of the deletion action. This may include status information or details about the deleted Relation. Since the source code does not explicitly show the output structure, it can be assumed that the output confirms successful deletion or provides error details if the operation fails.
No binary data output is expected for this operation.
Dependencies
- Requires an API key credential for authentication with the external service managing Relations.
- The node uses a base URL configured via credentials to connect to the appropriate API endpoint.
- The underlying implementation depends on an OpenAPI specification loaded from
openapi.json
and a helper library for building properties and making requests.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Relation ID will likely result in an error indicating that the resource could not be found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent the node from reaching the API endpoint.
Error messages:
- "Relation not found" or similar indicates the specified ID does not exist; verify the ID before retrying.
- Authentication errors suggest checking the API key or token configuration.
- Timeout or connection errors require verifying network access and API availability.
Links and References
- Refer to the API documentation of the external service managing Relations for detailed information on the delete operation.
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/integrations/creating-nodes/