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 manage various resources, including Number Port entities. Specifically, the Update operation for the Number Port resource allows users to modify existing number port records by specifying their unique ID and providing updated field values.
Typical use cases include:
- Updating details of a number port request or record in TeleFlow.
- Automating changes to number port configurations as part of a telecom workflow.
- Integrating number port updates into larger automation pipelines that manage telephony resources.
For example, you might update a number port's status or associated metadata by providing its ID and the fields to change.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Number Port resource to update. This is required. |
| Fields | A collection of field-value pairs representing the data to update on the Number Port. You can specify multiple fields, each with a name and corresponding value. |
The "Fields" property allows flexible updating of any supported attributes of the Number Port resource by adding multiple field entries.
Output
The node outputs an array of JSON objects, each representing the response from the TeleFlow API after attempting to update a Number Port resource. The structure of the JSON output corresponds directly to the updated Number Port object returned by the API.
No binary data output is produced 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 methods (PUT) to communicate with the TeleFlow REST endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided for the update operation, the node will throw an error stating that the ID is required. Ensure you provide a valid ID.
- Invalid Field Names: Providing incorrect or unsupported field names in the "Fields" collection may cause the API to reject the request or ignore those fields. Verify field names against TeleFlow API documentation.
- Authentication Failures: Incorrect or missing API credentials will result in authentication errors. Confirm that the API key and base URL are correctly set in the node credentials.
- API Errors: Any other API errors (e.g., network issues, invalid data) will be logged and can be handled by enabling the node's "Continue On Fail" option to prevent workflow interruption.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- n8n Custom Node Development Guide: https://docs.n8n.io/integrations/creating-nodes/