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 integrates with the TeleFlow API to perform various operations on different resources, including "Number Port". Specifically, the Get operation for the Number Port resource retrieves detailed information about a specific number port entry by its unique ID. This is useful when you need to fetch current data or status of a particular number port in your telephony system.
Practical scenarios include:
- Retrieving details of a number port request to check its status.
- Fetching configuration or metadata associated with a specific number port.
- Using the retrieved data to trigger further workflows or updates based on the port's state.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Number Port resource to retrieve. This is required. |
| Fields | Optional key-value pairs to specify additional query parameters or filters for the request. You can add multiple fields, each with a name and value. |
Output
The output is a JSON object representing the Number Port resource as returned by the TeleFlow API. It contains all the details of the requested number port entry, including any fields specified in the input properties.
If the API supports binary data for this resource (not indicated here), it would be included accordingly, but this node primarily outputs JSON data.
Example output structure (simplified):
{
"id": "string",
"status": "string",
"number": "string",
"portDate": "string",
"additionalField1": "value",
...
}
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API.
Troubleshooting
- Missing ID error: If the ID property is not provided for the Get operation, the node will throw an error stating that the ID is required. Ensure you provide a valid ID.
- API connection issues: Errors related to network connectivity or authentication failures may occur if the API key or base URL is incorrect or missing.
- Invalid field names: Providing unsupported or incorrect field names in the Fields property may result in unexpected API responses or errors.
- To resolve these, verify your credentials, ensure the ID exists in the system, and double-check field names against the TeleFlow API documentation.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/