What you need
- A Denada project with an email ready to push
- A Zeta REST API key — a 32-character key from Settings > Integrations > Keys & Apps in the Zeta Marketing Platform
- Your Zeta site ID
Connect Denada to Zeta
1
Open the Integrations dialog
Click Share on any project, then under Integrations, click Configure. (You can also open your team’s Settings page and click Add integration in the Integrations panel — manager access required.)
2
Select Zeta
Choose Zeta from the list of platforms.
3
Enter your credentials
- Name — optional, e.g. “Production”.
- API key — your Zeta REST API key.
- Site ID — the site the exports should go to.
4
Validate and save
Click Validate to confirm the key and site ID work, then click Save.
Push an email to Zeta
- Open the project and click Share.
- Under Integrations, select Export to Zeta.
- Fill in the export dialog:
- Template name — the name that will appear in Zeta. Defaults to your project’s name.
- Upload images to Zeta — optional. When checked, Denada uploads your email’s images into the Zeta Asset Library and rewrites the HTML to use Zeta-hosted URLs. Click Choose… to pick the destination folder — the Select folder picker browses your Asset Library, and you can create new folders with Create folder right from the picker. When unchecked, images stay hosted on Denada’s CDN.
- Click Export.
How updates work
- Re-exporting updates in place. If you’ve pushed this project to Zeta before, the export dialog shows a Previous export option: choose Overwrite to update the same Zeta content template, or Create new to make a separate one.
- Images update instead of duplicating. Uploaded images get stable filenames derived from the image itself, so re-exporting to the same Asset Library folder updates the existing assets in place — even after you re-crop an image in Denada — rather than orphaning old copies. If you export to a different folder, images are uploaded fresh there (Zeta assets are folder-bound).
Zeta doesn’t get a name-collision check like some other platforms — use the Previous export option to control whether you update or duplicate.
Troubleshooting
Validation fails
Validation fails
Confirm the API key is the 32-character REST key from Settings > Integrations > Keys & Apps, and that the Site ID matches the site that key belongs to.