Actions114
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
- Call Actions
- Label Actions
- OpenAI Actions
- N8N Integration Actions
- EvoAI Actions
- Template Actions
- Business Actions
Template → Create Template
AI-generatedOverview
This node interacts with the Evolution API to create a new template within a specified instance. It is useful for automating the creation of message templates categorized by marketing, utility, or authentication purposes, and supports multiple languages. Users can define the template's name, category, language, and various components such as header, body, footer, and buttons, allowing for dynamic and customizable message templates.
Use Case Examples
- Creating a marketing template in English (US) with a text header, body text containing variables, a footer, and quick reply buttons.
- Creating an authentication template in Spanish with an image header and call-to-action buttons.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance where the template will be created. |
| Template Name | The unique name for the template, formatted in lowercase without spaces. |
| Category | The category of the template, such as Marketing, Utility, or Authentication. |
| Language | The language of the template, supporting various locales like English (US), Portuguese (BR), Spanish, French, German, Italian, and Turkish. |
| Components | The components of the template, which can include headers (text, image, video, document), body text with variables, footer text, and buttons (quick reply or call to action). |
Output
JSON
templateId- The unique identifier of the created template.status- The status of the template creation operation.message- Additional information or confirmation message about the template creation.
Dependencies
- Evolution API with authentication credentials
Troubleshooting
- Ensure all required fields (Instance Name, Template Name, Category, Language, and Body text in Components) are provided to avoid validation errors.
- Template Name must be lowercase and contain no spaces; otherwise, the API may reject the request.
- Check API credentials and network connectivity if the node fails to connect to the Evolution API.
- Error messages related to unsupported operations indicate that the selected resource or operation is not implemented in the node.