Actions13
Overview
This node integrates with the Blinko API to manage notes and related entities. Specifically, the Create Note operation allows users to create a new note with customizable content, tags, type, pinning status, sharing options, and file attachments.
Common scenarios for this node include:
- Automatically creating notes from incoming data streams or events.
- Adding rich notes with metadata and attachments for project management or documentation.
- Sharing notes programmatically within teams or external collaborators.
- Tagging notes for better organization and retrieval.
For example, you could use this node to create a meeting summary note with attached files and share it with your team automatically after a call.
Properties
| Name | Meaning |
|---|---|
| Content | The main text content of the note. |
| Additional Fields | A collection of optional fields to further customize the note: |
| - Tags | Comma-separated list of tags to categorize the note. |
| - Type | The type of the note; options are "Blinko" (0) or "Note" (1). |
| - Is Top | Boolean flag indicating if the note should be pinned to the top. |
| - Is Share | Boolean flag indicating if the note should be shared. |
| - Files | One or more files to attach to the note. Each file is specified by the name of the binary property containing its data. |
Output
The output JSON contains the created note's details as returned by the Blinko API. This typically includes identifiers, content, metadata such as tags and type, sharing status, pinning status, and information about any attached files.
If files are attached, the node handles binary data input for those files but outputs only the note metadata in JSON form. Binary data is used as input for attachments and not outputted directly.
Dependencies
- Requires an API key credential for authenticating with the Blinko API.
- The node expects proper configuration of this credential within n8n.
- Network access to the Blinko API endpoint is necessary.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Invalid input data: Required fields like "Content" must be provided; missing these will cause errors.
- File attachment issues: The binary property names must match existing binary data on the input items; otherwise, file uploads will fail.
- API errors: If the Blinko API returns errors (e.g., rate limits, invalid parameters), these will be surfaced by the node. Check the error message for details.
- Unsupported operations: Using an unsupported resource or operation will throw an error indicating the operation/resource is not supported.
Links and References
- Blinko API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- n8n Community Forum for troubleshooting and examples: https://community.n8n.io