TeleFlowInstall

Overview

The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Provision resource with the Update operation, it updates an existing provision record identified by its unique ID. This is useful in scenarios where you need to modify provisioning details dynamically, such as updating configuration parameters or attributes of a telephony provision.

Practical example: You have a provision entry representing a telephony service setup, and you want to update certain fields (like name or other custom attributes) without recreating the entire provision. This node allows you to specify the provision ID and the fields to update, sending the changes via the TeleFlow API.

Properties

• ID: Required string input that identifies the specific provision to update.
• Fields: Allows adding multiple fields, each with:
  • Name: The name of the field to update.
  • Value: The new value to assign to that field.

Output

The output is an array of JSON objects, each representing the response from the TeleFlow API after attempting to update a provision. The structure corresponds directly to the API's response for the updated provision resource, typically including updated field values and metadata.

No binary data output is produced by this operation.

Example output snippet:

{
  "id": "12345",
  "name": "Updated Provision Name",
  "otherField": "newValue",
  ...
}

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 requests to communicate with the TeleFlow REST API endpoints.

Troubleshooting

• Missing ID error: If the ID property is not provided, the node throws an error stating "ID is required for update operation". Ensure the ID is set correctly.
• API request failures: Network issues, invalid credentials, or incorrect field names can cause HTTP errors. Check API credentials and field names carefully.
• Invalid field names or values: The API may reject updates if fields are not recognized or values are invalid. Verify field names against TeleFlow API documentation.
• Continue on Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning error messages in the output JSON.

Links and References

• TeleFlow API Documentation (replace with actual URL)
• n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/