Actions13
Overview
This node integrates with the Blinko API to manage notes and related resources. Specifically, the "Update Note" operation allows users to modify existing notes by specifying the note's ID and the fields to update. This is useful in scenarios where you want to programmatically edit note content, change its status (archived, pinned, shared, recycled), or update metadata such as tags or type.
Practical examples include:
- Automatically updating a note’s content based on external triggers.
- Archiving or unarchiving notes as part of workflow automation.
- Tagging notes dynamically for better organization.
- Changing the note type between "Blinko" and "Note" formats.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the note to update. |
| Update Fields | A collection of fields that can be updated: |
| - Content: Text content of the note. | |
| - Type: Type of the note; options are "Blinko" (0) or "Note" (1). | |
| - Is Archived: Boolean indicating if the note is archived. | |
| - Is Top: Boolean indicating if the note is pinned to the top. | |
| - Is Share: Boolean indicating if the note is shared. | |
| - Is Recycle: Boolean indicating if the note is in the recycle bin. | |
| - Tags: Comma-separated string of tags associated with the note. |
Output
The node outputs JSON data representing the updated note object returned from the Blinko API after the update operation. This typically includes all note properties reflecting the new state post-update.
If the node supports binary data output (not indicated here), it would represent file attachments or similar, but for this operation, the output is purely JSON.
Dependencies
- Requires an active connection to the Blinko API via an API key credential configured in n8n.
- The node uses the Blinko API base URL and request options obtained from credentials.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Note ID will likely result in an error from the API.
- Omitting required fields or providing invalid field values (e.g., wrong type for "Type") may cause the update to fail.
- Network or authentication errors if the API key is missing, expired, or incorrect.
Error messages:
"The operation "update" is not supported!"— indicates a misconfiguration of the operation parameter."The resource "notes" is not supported!"— indicates a misconfiguration of the resource parameter.- API errors related to invalid IDs or permissions will be passed through; ensure the note exists and the API key has sufficient rights.
Resolution tips:
- Double-check the Note ID and ensure it exists in your Blinko account.
- Verify that the API key credential is correctly set up and valid.
- Validate input fields conform to expected types and constraints.
Links and References
- Blinko API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices in n8n workflows