Actions13
Overview
This node integrates with the Blinko API to manage tags and their associated notes. Specifically, the "Delete" operation under the "Tag" resource allows users to delete a tag by its ID. Additionally, there is an option to delete all notes associated with that tag simultaneously. This functionality is useful for cleaning up tags and related data in bulk, ensuring no orphaned notes remain after tag removal.
Practical examples:
- Removing a deprecated or obsolete tag from your system along with all notes linked to it.
- Cleaning up tags and their notes as part of a data maintenance workflow.
Properties
| Name | Meaning |
|---|---|
| Tag ID | The unique identifier (number) of the tag you want to delete. |
| Delete Associated Notes | Boolean option to also delete all notes associated with this tag (true or false). |
Output
The output JSON contains the result of the delete operation. Typically, this will confirm whether the tag (and optionally its associated notes) were successfully deleted. The exact structure depends on the API response but generally includes status information or confirmation messages.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Blinko API.
- The node uses the Blinko API base URL and request options configured via credentials.
- No additional external services are required beyond the Blinko API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Tag ID will likely cause an error indicating the tag could not be found.
- Insufficient permissions or invalid API credentials may result in authentication errors.
- Attempting to delete associated notes when none exist should not cause failure but verify API behavior.
Error messages:
"The operation "delete" is not supported!"— indicates an unsupported operation was requested; ensure the operation name is correct."The resource "tags" is not supported!"— indicates an unsupported resource; verify the resource parameter.- API errors returned from Blinko (e.g., 404 Not Found, 401 Unauthorized) should be handled by checking credentials and input parameters.
To resolve errors:
- Double-check the Tag ID is correct and exists.
- Verify API credentials are valid and have necessary permissions.
- Use the "Delete Associated Notes" option carefully if you want to remove linked notes.
Links and References
- Blinko API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on creating custom nodes