Actions13
Overview
The node integrates with the Blinko API to manage various resources such as notes, attachments, tags, and comments. Specifically, for the Attachment Upload operation, it allows users to upload binary files as attachments to the Blinko platform. This is useful in scenarios where you want to programmatically add files (e.g., images, documents) to your Blinko workspace or notes.
Practical examples include:
- Automatically uploading screenshots or reports generated by other workflows.
- Attaching files received from external sources into Blinko for centralized access.
- Enriching notes or projects with relevant documents without manual uploads.
Properties
| Name | Meaning |
|---|---|
| Binary Property | The name of the binary data property in the input that contains the file to be uploaded. |
This property expects a string specifying which binary field holds the file data to upload.
Output
The node outputs JSON data representing the result of the upload operation. Typically, this includes metadata about the uploaded attachment such as its ID, filename, URL, or status returned by the Blinko API.
If the node supports binary output (not explicitly shown here), it would represent the uploaded file or related binary content, but based on the code and context, the output is JSON metadata only.
Dependencies
- Requires an active connection to the Blinko API via an API key credential configured in n8n.
- The node uses helper functions to retrieve credentials and base URLs dynamically.
- No additional external dependencies are indicated beyond the Blinko API.
Troubleshooting
Common issues:
- Incorrect binary property name: If the specified binary property does not exist or is empty, the upload will fail.
- Authentication errors: Missing or invalid API credentials will prevent successful communication with the Blinko API.
- Unsupported file types or size limits imposed by Blinko may cause upload failures.
Error messages:
"The operation "upload" is not supported!"— indicates a misconfiguration or typo in the operation parameter."The resource "attachments" is not supported!"— indicates an incorrect resource selection.- API errors returned from Blinko will be surfaced as node execution errors; check credentials and input data validity.
To resolve these, verify the binary property name matches the input data, ensure valid API credentials are set up, and confirm the file meets Blinko's requirements.
Links and References
- Blinko API Documentation (hypothetical link as no real URL provided)
- n8n documentation on working with binary data
- n8n guide on API credentials setup