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 Report resource and the Update operation, it updates an existing report by its unique ID with specified fields.
This node is useful in scenarios where you need to programmatically modify reports stored in TeleFlow, such as updating report metadata or attributes after creation. For example, you might update a report's name or other custom fields dynamically based on workflow logic.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the report to update. This is required to specify which report to modify. |
| Fields | A collection of field-value pairs representing the properties of the report to update. Each pair consists of: - Name: The field name to update. - Value: The new value for that field. |
Output
- The output is a JSON object representing the updated report as returned by the TeleFlow API.
- The structure of this JSON depends on the API response but typically includes the updated fields and possibly metadata about the report.
- 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 credentials.
- Proper permissions on the API key are necessary to perform update operations on reports.
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 insufficient permissions can cause HTTP request failures. Verify API key validity and network connectivity.
- Field Validation Errors: If the fields provided do not match expected API schema or contain invalid values, the API may reject the update. Double-check field names and values.
- 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 URL)
- n8n HTTP Request Node Documentation