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
This node integrates with the TeleFlow API to manage various resources, including Email Templates. Specifically, the Create operation for the Email Template resource allows users to create new email templates by sending specified fields to the TeleFlow system.
Common scenarios where this node is beneficial include automating the creation of email templates in bulk or as part of a workflow that manages communication templates dynamically. For example, a marketing automation workflow could generate customized email templates based on user input or external data sources.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs representing the properties of the email template to create. You can add multiple fields, each with a name and corresponding value, to specify the details of the email template. |
The "Fields" property supports multiple entries, allowing you to define several attributes of the email template in one request.
Output
The output of the node is an array of JSON objects, each representing the response from the TeleFlow API after creating an email template. The structure corresponds directly to the API's response for the created resource, typically including identifiers and any other metadata returned by the service.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing Required Fields: If required fields for the email template are not provided, the API may return errors. Ensure all mandatory fields are included in the "Fields" property.
- Authentication Errors: If the API key or base URL is incorrect or missing, authentication will fail. Verify the credential configuration.
- API Request Failures: Network issues or incorrect field names can cause request failures. Check error messages logged by the node for details.
- Error Message: "ID is required for get/update/delete operations": This message appears if those operations are attempted without specifying an ID. For the Create operation, this does not apply.
If the node is set to continue on failure, errors will be returned in the output JSON under an error property instead of stopping execution.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/