Blocklet Service icon

Blocklet Service

Consume Blocklet Service API
Join our community

Actions10

Overview

This node interacts with the Blocklet Service API to manage tags among other resources. Specifically, the "Get Tags" operation fetches a list of tags from the service, supporting pagination to control the number of tags retrieved per request.

Use cases include:

  • Retrieving all available tags for categorizing or filtering content.
  • Integrating tag data into workflows that require dynamic tag lists.
  • Managing large sets of tags by fetching them page-by-page.

For example, you might use this node to get the first 50 tags and then process or display them in your application or workflow.

Properties

Name Meaning
Paging Collection to control pagination when fetching tags:
- Page: The page number to fetch (default is 1).
- Page Size: The number of items per page (default is 50).

Output

The output is a JSON array where each item represents a tag object returned by the Blocklet Service API. Each tag typically includes properties such as its ID, title, description, and color (based on typical tag structures, though exact fields depend on the API response).

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Blocklet Service API.
  • The node depends on the blockletServiceApiRequest function to make HTTP requests to the Blocklet Service.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:
    • Pagination parameters out of range or invalid may cause errors or empty results.
    • Network or authentication failures if the API key is missing or incorrect.
  • Error messages:
    • "Not implemented tag action: getTags" would indicate a misconfiguration or unsupported operation, but this should not occur for the "getTags" operation as it is implemented.
    • API errors returned from the Blocklet Service will be surfaced; ensure the API key has proper permissions.
  • Resolution tips:
    • Verify the API key credential is correctly configured.
    • Adjust paging parameters to valid values.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion