Blinko icon

Blinko

Consume Blinko API
Join our community

Actions13

Overview

The node integrates with the Blinko API to manage tags among other resources. Specifically, the Edit Tag operation allows users to update properties of an existing tag by specifying its ID and the fields to change. This is useful in scenarios where you want to rename a tag, change its icon (usually an emoji), or adjust its sort order to reorganize how tags appear.

Practical examples include:

  • Renaming a tag from "Urgent" to "High Priority".
  • Changing the tag icon to better represent its meaning.
  • Adjusting the display order of tags in a user interface.

Properties

Name Meaning
Tag ID The unique numeric identifier of the tag you want to edit.
Update Fields A collection of fields to update for the tag:
   Name The new name for the tag (string).
   Icon The new icon for the tag, typically an emoji (string).
   Sort Order Numeric value defining the tag's sort order (number).

Output

The output is a JSON object representing the updated tag after the edit operation completes successfully. It contains the tag's current properties including any changes made (such as updated name, icon, or sort order).

If the node supports binary data output elsewhere, it is not relevant for this operation.

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 URL for API requests.
  • No additional external dependencies are indicated beyond the Blinko API access.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Tag ID will likely result in an error from the API indicating the tag was not found.
    • Omitting all update fields may cause the operation to do nothing or return an error depending on API behavior.
    • Incorrect API credentials or network issues will prevent successful communication with the Blinko API.

  • Error messages:

    • "The operation "edit" is not supported!" — indicates a misconfiguration or typo in the operation parameter.
    • "The resource "tags" is not supported!" — indicates the resource parameter is incorrect.
    • API errors related to authentication or validation will be passed through; ensure your API key is valid and that the Tag ID exists.

  • Resolution tips:

    • Double-check the Tag ID and ensure it exists in your Blinko account.
    • Verify that at least one field in "Update Fields" is provided.
    • Confirm your API credentials are correctly set up in n8n.
    • Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.

Links and References

Discussion