Actions27
- Account Actions
- Device Actions
- Estatísticas E Log Actions
- Item Actions
- Template Actions
Overview
This node integrates with the etiquetas.io platform, specifically focusing on managing devices. The "Backup Dos Binds" operation under the Device resource allows users to back up binding information related to a specific store. This is useful in scenarios where you want to preserve or export device bindings for backup, auditing, or migration purposes.
Practical examples include:
- Backing up device bindings before performing system maintenance.
- Exporting device binding data for reporting or compliance.
- Migrating device bindings from one environment to another.
Properties
| Name | Meaning |
|---|---|
| storeId | Identifier of the store whose device bindings are to be backed up. Can be selected from a searchable list of stores or entered manually by ID (numeric only). |
| outputField | The name of the field in the output JSON where the backup data will be stored. |
Output
The node outputs JSON data containing the backup of device bindings associated with the specified store. The exact structure depends on the API response but will be accessible under the user-defined outputField property in the output JSON.
If the node supports binary data output, it would typically represent exported backup files or similar artifacts; however, based on the provided code and properties, the output is JSON-based.
Dependencies
- Requires an API key credential for etiquetas.io to authenticate requests.
- Uses an internal method to fetch the list of stores for selection (
getStores). - Relies on etiquetas.io's API endpoints to perform the backup operation.
Troubleshooting
- Invalid Store ID: If the store ID does not match the expected numeric format, the node will reject the input. Ensure the store ID contains only digits.
- Authentication Errors: Failure to provide valid API credentials will result in authentication errors. Verify that the API key is correctly configured.
- Store Not Found: Selecting a store that does not exist or has no device bindings may return empty results or errors.
- Network Issues: Connectivity problems with etiquetas.io API can cause timeouts or failures. Check network access and API availability.