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 tenants. Specifically, for the Tenant - Update operation, it updates an existing tenant's information by sending a PUT request to the TeleFlow API with the tenant's ID and new data.
This node is useful in scenarios where you need to programmatically update tenant details within TeleFlow, such as changing the tenant's name or other attributes. For example, if your organization restructures and tenant names need to be updated across systems, this node can automate that process.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the tenant to update. Required to specify which tenant to modify. |
| Name | The new name to assign to the tenant. This is a required field when updating a tenant. |
| Fields | Additional field-value pairs to include in requests (used mainly for filtering in other operations, not directly for update). |
Output
The output is a JSON object representing the updated tenant resource as returned by the TeleFlow API after a successful update operation. It typically includes the tenant's properties such as its ID, name, and any other relevant metadata.
No binary data output is produced by this node.
Example output structure (simplified):
{
"id": "tenant-id",
"name": "Updated Tenant Name",
...
}
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- 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 for the update operation, the node will throw an error stating that the ID is required. Ensure the tenant ID is correctly specified.
- API request failures: Network issues, invalid credentials, or incorrect base URL configurations can cause HTTP request errors. Verify API credentials and endpoint settings.
- Invalid field values: Providing invalid or unsupported field values may result in API errors. Confirm that the "Name" value 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