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 Email Template resource and the Update operation, it updates an existing email template by its unique ID with specified fields.
This node is beneficial when you need to programmatically modify email templates stored in TeleFlow, such as updating the template's content or metadata without manual intervention. For example, automating updates to notification templates or marketing emails based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the email template to update. This is required. |
| Fields | A collection of field-value pairs specifying which properties of the email template to update. You can add multiple fields, each with a name and corresponding value. |
Output
- The output JSON contains the response from the TeleFlow API after updating the email template.
- Typically, this will include the updated email template object with its current properties reflecting the changes made.
- No binary data output is produced by this node.
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.
- The node uses HTTP methods (PUT) to communicate with the API endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node throws 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 field names may cause the API request to fail. Check the API key validity, endpoint URL, and field names.
- Field Validation: Providing invalid or unsupported field names/values in the "Fields" collection may result in errors from the API. Verify field names against TeleFlow API documentation.
- 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: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- General n8n Credential Setup Guide: https://docs.n8n.io/credentials/overview/