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 multiple resources, including Billing Entries. Specifically, for the Billing Entry - Delete operation, it allows users to delete a billing entry by specifying its unique ID.
Common scenarios where this node is beneficial include:
- Automating cleanup of obsolete or incorrect billing entries.
- Integrating billing management workflows where entries need to be programmatically removed.
- Managing billing data as part of larger telecommunication or account management processes.
For example, you might use this node in an automation that deletes billing entries older than a certain date or removes entries related to canceled services.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the billing entry to delete. This is required to specify which billing entry to remove. |
| Fields | Optional field-value pairs to include in the request for more specific queries (not typically used in delete but available for other operations). |
Note: For the Delete operation on Billing Entry, only the ID property is mandatory and relevant.
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified billing entry. Typically, this will be a confirmation object indicating success or details about the deletion.
Example output structure:
{
"success": true,
"message": "Billing entry deleted successfully",
"id": "the-deleted-entry-id"
}
If the API returns additional metadata or error information, it will also be included in the JSON output.
The node does not output binary data.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token or key configured in the node credentials.
- The base URL for the TeleFlow API must be set in the credentials configuration.
Troubleshooting
- Missing ID Error: If the ID property is not provided, the node throws an error stating that the ID is required for the delete operation. Ensure the ID is correctly set.
- API Authentication Errors: If the API key or token is invalid or missing, requests will fail. Verify credential setup.
- Network or Connectivity Issues: Failures to reach the TeleFlow API endpoint may occur due to network problems or incorrect base URL configuration.
- Permission Denied: The API user associated with the credentials might lack permission to delete billing entries. Check API user roles and permissions.
- Non-existent ID: Attempting to delete a billing entry that does not exist may result in an error or a failure message from the API.
To resolve errors, verify input parameters, credentials, and network connectivity. Enable "Continue On Fail" if you want the workflow to proceed despite individual item failures.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n Documentation on HTTP Request Node
- General n8n Node Development Guide