Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the "SIP Trunk" resource and the "Get Many" operation, it retrieves multiple SIP Trunk records from the TeleFlow system. This is useful when you want to fetch a list of SIP Trunks, optionally filtered by specific fields.
Common scenarios include:
- Retrieving all SIP Trunks configured in your TeleFlow account.
- Filtering SIP Trunks based on certain criteria (e.g., name or host) to process or analyze them further.
- Integrating SIP Trunk data into workflows for monitoring or reporting purposes.
Example: You might use this node to get all SIP Trunks whose name contains a particular substring or that match a specific host address.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the SIP Trunks returned by the query. Each pair specifies a field name (e.g., "name") and a value to match. Multiple pairs can be added for more specific queries. |
Output
The output is an array of JSON objects representing the SIP Trunks retrieved from the TeleFlow API. Each object contains the properties of a SIP Trunk as returned by the API, such as its name, host, and other relevant details.
No binary data is output by this node.
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.
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 API's expected parameters, the request may return no results or errors.
- Network issues or API downtime: HTTP request failures may occur; verify network connectivity and TeleFlow service status.
- Error message "ID is required for get/update/delete": This does not apply to the "Get Many" operation but indicates missing required parameters for other operations.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)