Create
AI-generatedOverview
The Braze Email Template node allows users to manage email templates within the Braze platform. It supports operations such as creating new email templates, retrieving detailed information about existing templates, listing all templates with optional filters, and updating existing templates.
This node is beneficial in marketing automation workflows where dynamic management of email templates is required without manually accessing the Braze dashboard. For example, a user can automate the creation of personalized email templates based on campaign data or update templates programmatically when content changes.
Practical examples:
- Automatically create a new email template for a promotional campaign with specific subject lines and HTML body.
- Retrieve details of an existing email template to verify its content before sending.
- List all email templates modified within a certain date range to audit recent changes.
- Update an existing email template’s body or tags as part of a content refresh process.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform: Create, Get Info, List, or Update an email template. |
| Template Name | Name of the email template (required for create and update operations). |
| Subject | Subject line of the email template (required for create operation). |
| Body (HTML) | HTML content of the email template body (required for create operation). |
| Plain Text Body | Plain text version of the email template body (optional for create and update operations). |
| Preheader | Email preheader text used for preview snippets in some email clients (optional for create/update). |
| Tags | Comma-separated list of tags associated with the template; tags must already exist in Braze (optional for create/update). |
| Should Inline CSS | Boolean flag indicating whether to inline CSS styles in the email template (optional for create/update). |
Additional properties related to listing and info operations (not detailed here) include filters like modifiedAfter, modifiedBefore, limit, offset, and emailTemplateId for identifying specific templates.
Output
The node outputs JSON data representing the response from the Braze API for each executed operation:
- Create: Returns the newly created email template details including its ID and metadata.
- Get Info: Returns detailed information about a specific email template identified by its ID.
- List: Returns a list of email templates, optionally filtered by modification dates, with pagination support.
- Update: Returns the updated email template details confirming the applied changes.
If an error occurs during any operation, the output JSON will contain an error field describing the issue along with additional error metadata such as HTTP status code and Braze-specific error codes.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Braze REST API.
- Needs the Braze instance URL or endpoint configured via credentials.
- Uses HTTP requests to communicate with Braze's email template endpoints.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing non-existent tag names in the Tags property will result in errors since tags must pre-exist in Braze.
- Missing required fields like Template Name, Subject, or Body during creation will cause validation errors.
- Incorrect email template IDs for info or update operations will lead to "not found" errors.
Error messages:
- Errors returned from Braze are captured and surfaced in the node output under the
errorfield. - HTTP status codes and Braze error codes are included to help diagnose issues.
- To resolve errors, verify that all required parameters are correctly set, credentials are valid, and referenced resources (tags, template IDs) exist in Braze.
- Errors returned from Braze are captured and surfaced in the node output under the
Handling failures:
- The node supports continuing execution on failure if enabled, allowing workflows to handle partial successes gracefully.