Actions13
Overview
This node integrates with the Blinko API to retrieve multiple notes based on user-defined criteria. It is useful for scenarios where you want to fetch a list of notes filtered by type, tags, archival status, presence of files, or search text. For example, you might use it to gather all active notes tagged with a specific label or to retrieve only "Blinko" type notes for further processing or reporting.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching notes or limit the number of results returned. |
| Limit | Maximum number of notes to return if not returning all (minimum 1, maximum 100). |
| Type | Type of notes to get: All notes, only normal notes, or only Blinko notes. |
| Filters | Collection of filters to narrow down the notes: |
| - Tag ID | Filter notes by a specific tag identifier. |
| - Is Archived | Include archived notes if true; otherwise exclude them. |
| - With File | Include only notes that have attached files if true. |
| - Search Text | Text string to filter notes by content or metadata. |
| - Order By | Sort order of the results: Ascending or Descending. |
Output
The output is an array of JSON objects representing the notes retrieved from the Blinko API. Each object contains note details such as its content, type, tags, archival status, and any other metadata provided by the API. The node does not explicitly handle binary data in this operation.
Dependencies
- Requires an API key credential for authenticating with the Blinko API.
- The node expects proper configuration of this API key within n8n credentials.
- Network access to the Blinko API endpoint is necessary.
Troubleshooting
- Common Issues:
- Incorrect or missing API authentication token will cause authorization errors.
- Requesting more than the allowed limit (over 100) will likely result in validation errors.
- Using unsupported filter values may cause the API to reject the request.
- Error Messages:
"The operation "getNotes" is not supported!"indicates a misconfiguration or typo in the operation parameter."The resource "notes" is not supported!"suggests the resource parameter is incorrect.- API errors related to authentication or rate limits should be resolved by verifying credentials and usage quotas.
Links and References
- Blinko API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes