What you need
- A Denada project with an email ready to push
- A Salesforce Marketing Cloud account with administrative permissions (to create an Installed Package)
Step 1: Configure an SFMC Installed Package
Create a dedicated package in SFMC for the Denada integration:- Log in to your Salesforce Marketing Cloud account.
- Navigate to Setup.
- Under Platform Tools, select Apps, then click Installed Packages.
- Click New to create a new package.
- Name the package “Denada Integration” and provide a description (e.g., “Package for Denada SFMC data synchronization”).
- Click Save.
- Under the new package details, click Add Component.
- Set the component type to API Integration, then choose Server-to-Server.
- Define the required permissions:
- Documents & Images: Read, Write
- Assets: Read, Write
- Saved Content: Read, Write
- Email: Read, Write
- Provisioning Accounts: Read
- Click Save.
- Copy the Client ID and Client Secret generated for this component — you will need them in the next step.

Your SFMC Installed Package should look like this when complete.
Step 2: Connect Denada to Salesforce
- In Denada, open your team’s Settings page, find the Integrations panel, and click Add integration (manager access required). You can also get there from any project via Share > Integrations > Configure.
- Select Salesforce from the list.
- Enter the following details:
- Click Validate to ensure the integration is working.
- Click Save.
Push an email to Salesforce
When you are ready to send a project to SFMC:- Open the project and click Share.
- Under Integrations, select Export to Salesforce (if you have several Salesforce configurations, each appears with its configuration name).
- Choose the destination Content Builder folder (defaults to your configured default folder, but you can pick a different one).
- Give the asset a name — this is how it will appear in Content Builder.
- Next to Images, click Change and choose how images are hosted:
- Upload HTML only — uploads HTML with Denada-hosted images. The fastest option.
- Upload images to same folder — uploads HTML and hosts your images in SFMC, replacing image URLs in the HTML with SFMC-hosted URLs. All files go in one folder.
- Upload images to subfolder — same as above, but images are placed in a nested subfolder (you choose its name) to keep things organized.
- Upload images to another folder — hosts your images in a folder you pick, separate from the email. Use this if your team keeps one shared images folder instead of a folder per email. Denada remembers the folder for each Marketing Cloud account.
- Click Export here.

Choose how images are hosted when exporting to SFMC.
Preheader
By default, the preheader you write in a project is included in the email’s HTML as hidden preview text. If your team would rather review it in the email’s own preheader field in SFMC, turn on Preheader in SFMC’s preheader field. You’ll find it under Settings when you open your Salesforce configuration in your team’s Integrations panel. With it on, every export to that configuration:- Leaves the preheader out of the email’s HTML.
- Puts it in the email’s preheader field in Content Builder instead.
- Updates the field when you export again, including clearing it if you remove the preheader from the project.
This is a setting on the integration, so it applies to everyone exporting through that configuration. Hidden padding that some libraries add after the preheader text is part of the HTML, so it isn’t included either.
Code snippets
You can export part of an email as a code snippet in Content Builder, so your team can reuse it in emails they build in SFMC.- In the editor, open a block’s menu and choose Export as content block.
- Name the snippet. The name becomes the snippet’s customer key, which emails use to find it, so choose it carefully. Names can use letters, numbers, hyphens, and underscores, up to 36 characters.
- Export as usual. Denada creates the snippet next to the email and leaves this reference in its place:

A snippet keeps its key after it is created. Renaming the block’s snippet name later creates a new snippet and leaves the old one in Content Builder.
How updates work
Re-exporting a project to the same folder with the same name updates the email you exported before, in place, with nothing to confirm. If the name is already used by an email that wasn’t exported from this project, Denada tells you and asks before replacing it. Choose Replace to update that email, or Use different name to go back and change the name or folder. Images are never replaced. If an identical image is already in the folder, Denada reuses it. If a file with the same name but different contents is there, such as a genericimage.gif shared with other emails, the new image is uploaded under a slightly different name so nothing else is affected.
Troubleshooting
'Invalid credentials' error during validation
'Invalid credentials' error during validation
Make sure you are using a Server-to-Server API integration, not a Web App or Public App type. Double-check that the Client ID, Client Secret, and Tenant subdomain are correct.
Export fails with a permissions error
Export fails with a permissions error
Verify that your Installed Package has the required permissions: Documents & Images, Assets, Saved Content, and Email all need Read and Write access.
Images not appearing in SFMC
Images not appearing in SFMC
If you chose Upload HTML only, images are hosted by Denada and should display automatically. If you chose one of the SFMC-hosted options, check that the Assets permission includes Write access.
The preview hides my AMPscript
The preview hides my AMPscript
The project preview tidies away AMPscript it can’t run, such as setup blocks and
IF/ELSE tags, so you see the email rather than the code. Exports are never changed. To see everything, turn on Show scripting. See Seeing the raw scripting.