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. Specifically, for the Number Port resource with the Get Many operation, it retrieves multiple number port records from the TeleFlow system. This is useful when you want to fetch a list of number ports filtered by specific criteria.
Common scenarios include:
- Retrieving all number port requests or entries in your TeleFlow account.
- Filtering number ports based on certain fields such as status, date, or other attributes.
- Integrating TeleFlow number port data into workflows for reporting, auditing, or further processing.
Example: You might use this node to get all number ports that match certain conditions (e.g., only those with a particular status) and then process or analyze them downstream in your workflow.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to filter the request. You can add multiple fields to specify which records to retrieve. For example, you might filter by "status" or "date". |
The Fields property is a fixed collection allowing multiple entries, each with:
- Name: The name of the field to filter by.
- Value: The value to match for that field.
This enables flexible querying of number port records.
Output
The output is an array of JSON objects representing the number port records retrieved from the TeleFlow API. Each item corresponds to one number port entry matching the specified filters.
The structure of each JSON object depends on the TeleFlow API's response schema for number ports but generally includes details such as port identifiers, statuses, dates, and related metadata.
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 node uses HTTP requests to communicate with the TeleFlow API endpoint defined by the base URL in the credentials.
- Proper network access to the TeleFlow API server is necessary.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key credential is correctly set up and has sufficient permissions.
- Invalid field names or values: If filtering fields are incorrect or unsupported by the API, the request may return errors or empty results. Verify field names against TeleFlow API documentation.
- Network issues: Connectivity problems to the TeleFlow API will cause request failures.
- Empty results: If no records match the filter criteria, the output will be an empty array.
- Error messages: Common errors include missing required parameters (like ID for other operations), invalid JSON responses, or HTTP errors. Review error messages logged by the node for guidance.
To resolve errors, check the input parameters, ensure correct API credentials, and verify network connectivity.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/