Overview
This node integrates with the Gyazo API to retrieve information about a specific image collection. The "Get Collection" operation fetches detailed metadata and properties of a given collection by its unique identifier or URL.
Typical use cases include:
- Retrieving collection details for display or further processing in workflows.
- Automating management or reporting on image collections stored in Gyazo.
- Integrating Gyazo collections data into other systems or dashboards.
For example, you might use this node to get the name, creation date, and images count of a particular collection identified by its ID or URL.
Properties
| Name | Meaning |
|---|---|
| Collection | The target collection to retrieve. You can specify it either by: |
| - ID: A 32-character hexadecimal string representing the collection's unique ID. | |
- URL: The full URL of the collection in the format https://gyazo.com/collections/{id}. |
Output
The output is a JSON object containing the collection's details as returned by the Gyazo API. This typically includes fields such as:
- Collection ID
- Name of the collection
- Creation and update timestamps
- List or count of images within the collection
- Other metadata related to the collection
The exact structure depends on the Gyazo API response but generally provides comprehensive information about the specified collection.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Gyazo API.
- The node uses the Gyazo API base URL
https://api.gyazo.com. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Invalid Collection ID or URL Format:
If the provided collection ID does not match the required 32-character hexadecimal format, or if the URL does not follow the expected pattern (https://gyazo.com/collections/{id}), the node will throw an error indicating invalid format.
Resolution: Verify and correct the input value.Authentication Errors:
If the API key is missing, invalid, or expired, requests will fail.
Resolution: Ensure the API key credential is correctly set up and valid.Collection Not Found:
If the specified collection ID does not exist or is inaccessible, the API will return an error.
Resolution: Confirm the collection exists and that the API key has permission to access it.Network Issues:
Connectivity problems may cause request failures.
Resolution: Check network connectivity and retry.