BlinkoInstall

Overview

The node integrates with the Blinko API to manage tags among other resources. Specifically, the Tag - List operation retrieves a list of tags from Blinko. This is useful for workflows that need to display, filter, or process tags dynamically based on user input or other automation steps.

A practical example: You might use this node to fetch all tags starting with a certain prefix to categorize notes or attachments automatically, or to populate dropdowns in subsequent nodes with relevant tag options.

Properties

Output

The output is a JSON array where each item represents a tag object retrieved from the Blinko API. Each tag object typically contains properties such as the tag's name and possibly its ID or other metadata (exact fields depend on the API response).

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the Blinko API.
• The node needs an API authentication token credential configured in n8n to authorize requests to Blinko.
• Network access to the Blinko API endpoint is necessary.

Troubleshooting

• Common issues:
  • Authentication errors if the API key or token is missing, invalid, or expired.
  • Network connectivity problems preventing access to the Blinko API.
  • Using unsupported operations or resources will throw errors indicating the operation/resource is not supported.
• Error messages:
  • "The operation \"list\" is not supported!" — indicates a mismatch in operation name; ensure "list" is selected under the "tags" resource.
  • "The resource \"tags\" is not supported!" — indicates an invalid resource selection.
  • API errors returned from Blinko (e.g., rate limits, invalid filters) will be surfaced as error messages; verify filter values and API status.

Links and References

• Blinko API Documentation (hypothetical link, replace with actual if available)
• n8n documentation on Creating Custom Nodes