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 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, automating account renaming based on external triggers or synchronizing account details from another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the account to update. This is required to specify which account to modify. |
| Name | The new name for the account. A descriptive string to update the account's name field. |
| Fields | Additional field-value pairs to include in requests (not used directly in update but available for other operations). |
| Additional Details | Informational notice displayed in the UI (no direct effect on execution). |
Output
- The output is an array of JSON objects representing the updated account data returned from the TeleFlow API after the update operation.
- Each item corresponds to one input item processed.
- No binary data output is produced by this operation.
Example output structure:
{
"id": "account-id",
"name": "Updated Account Name",
// ... other account properties returned by the API
}
Dependencies
- Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
- The base URL for the API is taken from the credential configuration.
- The node uses HTTP methods (PUT) to communicate with the TeleFlow REST API endpoints.
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 base URL can cause HTTP request failures. Verify API credentials and connectivity.
- Invalid Field Values: Providing invalid or unsupported values for the "Name" or other fields may result in API errors. Confirm that the values conform to TeleFlow API requirements.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide