Actions82
- 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
Overview
This node integrates with the TeleFlow API to manage various telephony-related resources. Specifically, for the Phone Number resource with the Get Many operation, it retrieves multiple phone number records from the TeleFlow system. Users can specify filtering criteria by providing field-value pairs to narrow down the results.
Common scenarios where this node is beneficial include:
- Fetching a list of phone numbers that match certain attributes (e.g., type, status).
- Integrating TeleFlow phone number data into workflows for reporting or further processing.
- Automating audits or synchronization tasks involving phone number inventories.
Example: Retrieve all phone numbers of a specific type or belonging to a particular account by specifying those fields as filters.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used to filter the phone numbers returned by the query. Each pair consists of: - Name: The field name to filter on. - Value: The value to match for that field. Multiple such pairs can be added to refine the search criteria. |
Output
The node outputs an array of JSON objects representing the phone numbers retrieved from the TeleFlow API. Each object corresponds to a phone number record and includes all fields returned by the API based on the specified filters.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
- The base URL for the TeleFlow API must be set in the credentials.
- The node sends HTTP GET requests to the
/phoneNumbersendpoint with optional query parameters derived from the provided fields.
Troubleshooting
- Missing or incorrect API credentials: Ensure the API key and base URL are correctly configured in the node's credentials.
- Invalid field names or values: If the API returns errors or empty results, verify that the field names and values used for filtering exist and are valid according to TeleFlow's API documentation.
- Empty response: This may indicate no phone numbers match the given filters; try broadening or removing filters.
- Network issues or API downtime: Check network connectivity and TeleFlow service status if requests fail consistently.
- Error messages about missing ID: Not applicable for "Get Many" operation but relevant for other operations like "Get" or "Update" which require an ID.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/