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 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.
Common scenarios where this node is beneficial include automating telecom infrastructure management, updating porting requests, or synchronizing number port data between systems. For example, a telecom operator could use this node to update the status or details of a number port request programmatically as part of a workflow.
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 properties to update on the resource. |
The "Fields" property allows adding multiple entries, each specifying:
- Name: The name of the field to update.
- Value: The new value for that field.
Output
The node outputs an array of JSON objects corresponding to the updated Number Port records. Each output item contains the full JSON response from the TeleFlow API after performing the update, reflecting the current state of the resource.
No binary data output is produced by this operation.
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 PUT requests to update resources via the TeleFlow REST API.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the update operation. Ensure the ID is correctly set.
- API Request Failures: Network issues, invalid credentials, or incorrect field names/values may cause the API request to fail. Check the API key validity, endpoint URL, and field correctness.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual link if available)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/