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
This node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Device Template resource with the Get operation, it retrieves detailed information about a specific device template by its unique ID. This is useful when you need to fetch configuration or metadata of a particular device template within your TeleFlow environment.
Practical examples include:
- Retrieving a device template's details before applying it to a new device.
- Fetching device template data to audit or verify configurations.
- Integrating device template information into workflows that automate device provisioning or management.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the device template to retrieve. This is required for the Get operation. |
| Fields | Optional field-value pairs to specify additional query parameters for filtering or customizing the request. You can add multiple fields, each with a name and value. |
Output
The output is a JSON object representing the device template retrieved from the TeleFlow API. It contains all the properties and metadata associated with the specified device template ID as returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "string",
"name": "string",
"description": "string",
"configuration": { /* device template specific settings */ },
...
}
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the TeleFlow API must be set in the node credentials.
Troubleshooting
- Missing ID error: If the ID property is not provided, the node will throw an error stating that the ID is required for the get operation. Ensure you provide a valid device template ID.
- Authentication errors: If the API key or token is invalid or missing, requests will fail. Verify that the credential is correctly configured.
- Network or API errors: If the TeleFlow API is unreachable or returns an error, the node will log the error message. Check network connectivity and API status.
- Invalid fields: Providing incorrect field names or values in the optional Fields property may result in unexpected responses or errors. Use only supported query parameters.
If the node is set to continue on failure, errors will be returned in the output JSON under an error key instead of stopping execution.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/