Overview
The node named "Robolly" is designed to interact with the Robolly service to retrieve data related to templates and renders. Specifically, the "Get Renders" operation fetches render data associated with templates from Robolly. This node is useful in scenarios where users want to automate the retrieval of rendered outputs or template information for further processing, analysis, or integration into workflows.
Practical examples include:
- Automatically fetching all renders of a specific template to archive or analyze them.
- Limiting the number of renders retrieved to reduce data volume when only recent or specific renders are needed.
- Integrating render data into other systems such as content management or digital asset management platforms.
Properties
| Name | Meaning |
|---|---|
| Return All Items | Boolean option to decide whether to retrieve all render items of the template (true/false). |
| Limit | Number specifying how many render items to return if "Return All Items" is false. |
| ⚠️ Warning Get Renders may show a huge data ⚠️ | Informational notice warning that retrieving all renders may result in large amounts of data. |
Output
The output of the node is an array of items, each containing a json field with the render data retrieved from Robolly. Each item also includes metadata linking it back to the input item it originated from (pairedItem). The structure of the json field corresponds directly to the render data returned by the Robolly API.
If multiple renders are returned, each render is output as a separate item in the array. If a single object is returned, it is wrapped in an item with the json property.
The node does not explicitly handle binary data output.
Dependencies
- Requires an API key credential for authenticating with the Robolly service.
- The node depends on internal methods and operators defined in bundled dependencies to perform API calls and load options dynamically.
- No additional environment variables or external configurations are indicated beyond the required API authentication.
Troubleshooting
- Large Data Volumes: When "Return All Items" is enabled for "Get Renders," the node may retrieve very large datasets, potentially causing performance issues or timeouts. Users should consider limiting the number of items if possible.
- API Authentication Errors: Failure to provide valid API credentials will prevent the node from accessing Robolly data.
- Empty or Unexpected Responses: If the API returns no data or unexpected structures, verify that the template IDs and parameters used are correct.
- Error Messages: Common errors may relate to network connectivity, invalid parameters, or rate limits imposed by the Robolly API. Checking the API documentation and ensuring proper parameter usage can help resolve these.
Links and References
- Robolly Official Website (for general service information)
- Robolly API Documentation (not provided in source; consult Robolly support or developer resources)