Actions82
- 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
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, you might update an email template's name or body dynamically based on workflow inputs or external triggers.
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. Each pair includes: - Name: The field name to update (e.g., "name", "subject", "body"). - Value: The new value for that field. |
Output
- The output is a JSON object representing the updated email template as returned by the TeleFlow API.
- The structure depends on the API response but typically includes the updated fields of the email template.
- 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 credentials configuration.
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 of the email template to update is correctly supplied.
- Invalid Field Names: Providing incorrect or unsupported field names in the "Fields" collection may cause the API to reject the request or ignore those fields. Verify field names against TeleFlow API documentation.
- API Connection Issues: Network problems or invalid credentials can cause HTTP request failures. Check API credentials and network connectivity.
- Partial Updates: Only fields included in the "Fields" collection are updated; others remain unchanged.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)