TeleFlow icon

TeleFlow

Interact with TeleFlow API
Join our community

Actions145

Overview

This node interacts with the TeleFlow API to manage various resources, including devices. Specifically, the Device Delete operation allows users to delete a device resource by specifying its unique identifier (ID). This is useful in scenarios where devices are no longer needed or must be removed from the system for cleanup, compliance, or lifecycle management.

Practical examples:

  • Removing decommissioned hardware devices from your TeleFlow account.
  • Automating device lifecycle workflows where devices are deleted after certain conditions are met.
  • Cleaning up test or temporary devices created during development or testing phases.

Properties

Name Meaning
ID The unique identifier of the device resource to delete. This is required to specify which device to remove.
Fields Optional field-value pairs to include in the request for more specific queries (not typically used in delete operations).

Output

The output JSON contains the response from the TeleFlow API after attempting to delete the specified device. Typically, this will confirm whether the deletion was successful or provide details if an error occurred.

Example output structure:

{
  "success": true,
  "message": "Device deleted successfully"
}

or, in case of failure:

{
  "error": "Device not found"
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the TeleFlow API.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP DELETE requests to the endpoint /devices/{id} to perform the deletion.

Troubleshooting

  • Missing ID Error: If the ID property is not provided, the node throws an error stating that the ID is required. Ensure you supply a valid device ID.
  • API Errors: If the device does not exist or cannot be deleted due to permissions, the API may return an error message. Check that the ID is correct and that the API key has sufficient privileges.
  • Network Issues: Connectivity problems or incorrect base URL configuration can cause request failures. Verify network access and credential settings.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion