Update Content Block
AI-generatedOverview
The node manages reusable content blocks for Braze email templates via the Braze API. It supports operations to create, retrieve information about, list, and update content blocks. This is useful in marketing automation workflows where dynamic or reusable email content needs to be managed programmatically.
For the Update Content Block operation specifically, the node updates an existing content block's properties such as its name, content (HTML or text), description, state (active or draft), and tags. This allows users to maintain and modify email template components without manual intervention in the Braze dashboard.
Practical example:
A marketing team automates updating promotional banners or disclaimers across multiple email campaigns by modifying a single content block through this node, ensuring consistent messaging and saving time.
Properties
| Name | Meaning |
|---|---|
| Content Block ID | The unique API identifier of the content block to update (required). |
| Content Block Name | New name for the content block; leave empty to keep the current name. |
| Content | HTML or text content of the content block; leave empty to keep the current content. |
| Description | Description for the content block; leave empty to keep the current description. |
| State | State of the content block; options are: "Active" or "Draft". |
| Tags | Comma-separated list of tags to assign to the content block. |
Output
The node outputs JSON data representing the response from the Braze API after attempting to update the content block. The structure includes details of the updated content block or error information if the update failed.
If the update is successful, the output JSON contains the updated content block's metadata as returned by Braze.
If an error occurs, the output JSON includes:
error: A descriptive error message.originalError: The original error message from the HTTP request.httpCode: The HTTP status code returned by the Braze API.brazeErrorCode: Specific error code from Braze if available.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Braze API.
- Needs the Braze instance URL or identifier to construct API endpoints.
- The node uses HTTP requests to communicate with Braze's REST API.
Troubleshooting
Common issues:
- Invalid or missing Content Block ID will cause the update to fail.
- Providing empty strings for optional fields means those fields remain unchanged.
- Incorrect API key or instance configuration leads to authentication errors.
- Malformed tags string (e.g., improper commas) may result in unexpected tag assignments.
Common error messages:
- Errors returned from Braze API include detailed messages and codes; these are surfaced in the node output.
- HTTP 401 or 403 indicates authentication or permission issues—verify API credentials.
- HTTP 400 usually means invalid input parameters—check that required fields are correctly set.
Resolution tips:
- Ensure the Content Block ID exists and is correct.
- Validate API credentials and instance settings.
- Use the node’s error output to diagnose specific Braze API errors.
- When using tags, ensure they are comma-separated without trailing commas or extra spaces.