Actions13
Overview
This node integrates with the Blinko API to manage notes and their sharing settings. Specifically, the Note - Share operation allows users to share or unshare a note by its ID. When sharing, users can optionally protect the shared note with a password and set an expiration date for the share link.
Common scenarios include:
- Collaborating on notes by sharing them securely with team members or external parties.
- Temporarily sharing sensitive notes with password protection and automatic expiration.
- Revoking access to previously shared notes by unsharing them.
Example use cases:
- A project manager shares meeting notes with stakeholders, protected by a password and expiring after the project deadline.
- A user unshares a note after the information is no longer relevant or confidential.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the note to be shared or unshared. |
| Share Note | Boolean flag indicating whether to share (true) or unshare (false) the note. |
| Password | Optional password to protect the shared note (only applicable when sharing). |
| Expire Date | Optional date/time when the shared note will expire and become inaccessible (when sharing). |
Output
The node outputs JSON data representing the result of the share/unshare operation. This typically includes confirmation of the action taken, such as a share URL or status message. The exact structure depends on the Blinko API response but generally confirms success or failure.
No binary data output is indicated for 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 environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Note ID: If the provided Note ID does not exist or is malformed, the node may throw an error indicating the note was not found. Verify the Note ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is properly configured.
- Permission Denied: Attempting to share or unshare a note without sufficient permissions may result in authorization errors.
- Invalid Expiration Date: Providing an expiration date in the past or invalid format might cause the API to reject the request.
- Password Issues: If a password is required but missing or does not meet API criteria, the share operation may fail.
To resolve errors, check the input parameters, verify credentials, and consult the Blinko API documentation for valid values and formats.
Links and References
- Blinko API Documentation (replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General best practices for secure note sharing and password protection.