Skip to main content
Denada integrates with the email sending platforms (ESPs) your team already uses, so you can design emails in Denada and push them directly to your ESP for sending. No copy-pasting HTML, no manual uploads — just a clean handoff from design to delivery.

​
Supported platforms

Denada supports direct integrations with the following ESPs:
PlatformDescription
IterablePush templates directly to Iterable projects via the server-side API
BrazeExport email templates to Braze for campaign orchestration
HubSpotSend templates to HubSpot’s email marketing tools
KlaviyoExport to Klaviyo for e-commerce email workflows
Salesforce Marketing CloudPush templates to Salesforce for enterprise email campaigns
Campaign MonitorExport to Campaign Monitor for email creation and sending
In addition to ESP integrations, you can always export templates as raw HTML, CSV, or JSON for use with any platform.
You can configure multiple integrations at the same time. For example, if your team uses Iterable for transactional emails and Klaviyo for marketing, you can set up both and export to either one from the same template.

​
Figma integration

Denada also integrates with Figma for importing design assets. If your design team works in Figma, you can bring visual components and brand elements into Denada to use in your Libraries and templates.

​
Setting up an integration

The setup process is similar across all platforms:
  1. Open any template and click Share.
  2. Scroll down to Integrations and click Configure.
  3. Select the platform you want to connect.
  4. Enter your API credentials (typically an API key or token from your ESP’s settings).
  5. Click Validate to verify the connection works.
  6. Give the configuration a name (helpful if you have multiple accounts or projects) and click Save.
Most ESPs require a server-side or admin-level API key. Check the individual integration page for the specific key type and permissions required for your platform.
You can add multiple configurations for the same platform if you work with different accounts or projects. For example, you might have separate Iterable configurations for your staging and production environments.

​
Exporting a template

Once an integration is configured, exporting is straightforward:
  1. Open the template you want to export.
  2. Click Share.
  3. Under Integrations, select Export to [platform name].
  4. Enter a template name (this is the name that will appear in your ESP).
  5. Click Export.
If a template with the same name already exists in your ESP, Denada will ask whether you want to overwrite it.

​
Exporting variations

If your template has Variations, you can export them all at once:
  1. Click Share and toggle Export all variations.
  2. Choose your export format — ZIP (individual HTML files), CSV (structured data), or push each variation to your ESP.
This is particularly useful for A/B testing workflows where you need multiple versions uploaded to your sending platform.

​
What happens during export

When you click Export, Denada performs several steps behind the scenes to make sure your email arrives ready to use:
  1. HTML rendering — your template’s Blocks and Parameter values are combined into final HTML using the Eta templating engine.
  2. Image processing — images from your Image Library are optimized for email delivery (compressed, resized, and hosted on Denada’s CDN).
  3. Platform-specific escaping — special characters and syntax are escaped to prevent conflicts with your ESP’s own templating language. For example, curly braces are escaped for platforms that use Handlebars-style merge tags.
  4. Metadata inclusion — the email subject line and other metadata from your template are included in the export.
  5. Upload — the rendered template is pushed to your ESP via its API, where it appears ready to use in your campaigns.
Denada escapes platform-specific template syntax (like Handlebars merge tags) during export to prevent conflicts. If you need to use your ESP’s personalization tags, add them in your ESP after export.

​
General export formats

Even without an ESP integration, you can export templates in standard formats from the Share menu:
  • HTML — the fully rendered email as a single HTML file, ready to paste into any email tool.
  • CSV — structured export of template data and variations, useful for bulk workflows.
  • JSON — machine-readable format for programmatic use or archival.

​
Troubleshooting

Make sure you have configured at least one integration for that platform. Go to Share > Integrations > Configure to set one up.
Double-check that you are using the correct key type. Most platforms require a server-side or admin API key, not a client-side or mobile key. Refer to the specific integration page for details.
Some ESPs apply their own styling or wrapping to imported templates. Preview the email in your ESP’s built-in preview tool and send a test email to verify rendering. If curly braces or other syntax appear broken, it may be a merge tag conflict — Denada escapes these by default, but check for any that were added manually.
Check the folder or project you are exporting to. If you have multiple configurations for the same platform, make sure you selected the correct one. Also verify that your API key has permission to create templates.

​
Individual integration guides

For platform-specific setup instructions, API key requirements, and troubleshooting, see the dedicated pages:
Additional integration guides for Braze, HubSpot, Klaviyo, Salesforce Marketing Cloud, and Campaign Monitor are coming soon. The general setup and export flow described above applies to all platforms.

​
Need help?

If you run into issues with any integration, reach out to support@heydenada.com or ask in our Community Slack.