Actions145
- Account Actions
- Account Audit Actions
- Billing Entry Actions
- Call Detail Record Actions
- Carrier Actions
- Device Actions
- Device Template Actions
- Email Template Actions
- Feature Code Actions
- File Actions
- Flow Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Reseller Actions
- SIP Trunk Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
- Transcription Actions
- User Actions
- Voice Actions
- Voice Mail Message Actions
Overview
The node interacts with the TeleFlow API to perform various operations on different resources, including devices. Specifically, the "Get Many" operation for the "Device" resource retrieves multiple device records from the TeleFlow system. This operation supports filtering by specifying fields and their values, allowing users to query devices that match certain criteria.
This node is beneficial in scenarios where you need to fetch a list of devices managed within TeleFlow, such as inventory management, monitoring device statuses, or integrating device data into other workflows. For example, you could retrieve all devices of a specific type or with a particular name pattern to automate reporting or provisioning tasks.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the devices returned by the query. You can specify multiple fields to narrow down the search results. Each field consists of: - Name: The device property to filter by (e.g., "name", "type"). - Value: The value to match for the specified field. |
Output
The output is an array of JSON objects representing the devices retrieved from the TeleFlow API. Each object contains the properties of a device as returned by the API, filtered according to the specified fields if any were provided.
- The
jsonoutput field holds the device data. - No binary data output is produced by this operation.
Example output structure (simplified):
[
{
"id": "device-id-1",
"name": "Device One",
"type": "Type A",
...
},
{
"id": "device-id-2",
"name": "Device Two",
"type": "Type B",
...
}
]
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and base URL are correctly set in the node credentials.
- Invalid field names or values: If filtering fields do not match the expected device properties, the API may return empty results or errors. Verify field names against TeleFlow API documentation.
- Network issues or API downtime: HTTP request failures may occur due to connectivity problems or TeleFlow service outages.
- Error message "ID is required for get/update/delete operations": This does not apply to "Get Many" but appears for other operations; ensure the correct parameters are provided for each operation.
- Empty results: If no devices match the specified filters, the output will be an empty array.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/