Braze Content BlocksInstall

Overview

This node manages reusable content blocks for Braze email templates. It allows users to create, retrieve detailed information about, list, and update content blocks that can be reused across email campaigns in Braze. This is useful for marketers or developers who want to maintain consistent content snippets (like headers, footers, disclaimers) centrally and reuse them in multiple email templates.

A common scenario is listing all content blocks with optional filters such as modification date range and pagination controls, enabling efficient management and retrieval of relevant content blocks.

Example use cases:

• Fetching a paginated list of content blocks modified within a specific timeframe.
• Creating a new content block with specified content and tags.
• Updating an existing content block’s content or metadata.
• Retrieving detailed info about a particular content block including inclusion data.

Properties

These properties apply when the operation is List Content Blocks.

Output

The node outputs an array of JSON objects representing the content blocks retrieved or affected by the operation. Each item corresponds to one content block or the result of the requested operation.

For the List Content Blocks operation, the output JSON contains the response from Braze's API endpoint /content_blocks/list, which includes details about each content block such as its ID, name, content, state, description, tags, and timestamps.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the Braze API.
• The node uses the Braze API base URL configured via the instance parameter in credentials.
• Network access to Braze API endpoints is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing API key will cause authentication failures.
  • Incorrect date formats for "Modified After" or "Modified Before" may lead to API errors.
  • Exceeding the maximum allowed limit or invalid offset values might cause unexpected results or errors.

• Error messages:

  • Errors returned by the Braze API are captured and presented with their message, HTTP code, and Braze-specific error code.
  • If the node is set to continue on fail, errors are included in the output JSON under an error field.
  • To resolve errors, verify API credentials, ensure correct input formats, and check Braze API documentation for limits and constraints.

Links and References

• Braze Content Blocks API Documentation
• Braze Developer Guide