Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
The node interacts with the TeleFlow API to manage various resources, including accounts. Specifically, for the Account - Update operation, it updates an existing account's details by sending a PUT request to the TeleFlow API with the specified account ID and new data.
This node is useful in scenarios where you need to programmatically update account information within TeleFlow, such as changing the account name or other editable fields. For example, you might use this node in an automation workflow that synchronizes account names from another system or updates account details based on user input.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the account to update. Required to specify which account to modify. |
| Name | The new name for the account. A descriptive name to update the account with. |
| Fields | Additional field-value pairs to include in the request (not used directly in update). |
| Additional Details | Informational notice displayed in the UI (no direct effect on execution). |
Output
The node outputs the JSON response returned by the TeleFlow API after updating the account. This typically includes the updated account object with its current properties reflecting the changes made.
Example output structure (simplified):
{
"id": "account-id",
"name": "Updated Account Name",
// other account properties...
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The base URL for the TeleFlow API must be set in the node credentials.
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 you provide a valid account ID.
- API Request Failures: Network issues, invalid credentials, or incorrect base URL configuration can cause HTTP request failures. Verify your API credentials and endpoint settings.
- Invalid Field Values: Providing invalid or unsupported values for the "Name" property may result in API errors. Confirm that the new name meets TeleFlow's requirements.
- Continue On Fail: 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
- n8n Custom Node Development Guide