Skip to main content
Denada integrates with Salesforce Marketing Cloud so you can design emails in Denada and push them directly into SFMC’s Content Builder.

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:
  1. Log in to your Salesforce Marketing Cloud account.
  2. Navigate to Setup.
  3. Under Platform Tools, select Apps, then click Installed Packages.
  4. Click New to create a new package.
  5. Name the package “Denada Integration” and provide a description (e.g., “Package for Denada SFMC data synchronization”).
  6. Click Save.
  7. Under the new package details, click Add Component.
  8. Set the component type to API Integration, then choose Server-to-Server.
  9. Define the required permissions:
    • Documents & Images: Read, Write
    • Assets: Read, Write
    • Saved Content: Read, Write
    • Email: Read, Write
    • Provisioning Accounts: Read
  10. Click Save.
  11. Copy the Client ID and Client Secret generated for this component — you will need them in the next step.
SFMC Installed Packages screen showing the Denada Integration package with API Integration component and permissions

Your SFMC Installed Package should look like this when complete.

Step 2: Connect Denada to Salesforce

  1. 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.
  2. Select Salesforce from the list.
  3. Enter the following details:
  1. Click Validate to ensure the integration is working.
  2. Click Save.

Push an email to Salesforce

When you are ready to send a project to SFMC:
  1. Open the project and click Share.
  2. Under Integrations, select Export to Salesforce (if you have several Salesforce configurations, each appears with its configuration name).
  3. Choose the destination Content Builder folder (defaults to your configured default folder, but you can pick a different one).
  4. Give the asset a name — this is how it will appear in Content Builder.
  5. Choose your upload type:
  • 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.
  1. Click Export here.
SFMC export dialog showing the image upload options

Choose how images are hosted when exporting to SFMC.

If you are unsure which upload type to use, Upload images to subfolder is the simplest option and works well for most teams.

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.
  1. In the editor, open a block’s menu and choose Export as content block.
  2. 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.
  3. Export as usual. Denada creates the snippet next to the email and leaves this reference in its place:
By default the snippet is created in the same folder as the email. If your team keeps snippets in a shared folder, use Change next to “Code snippets will be created in…” in the export dialog to pick one. This line only appears when the project has a block exported as a snippet, and Denada remembers the folder for each Marketing Cloud account. Exporting again updates the same snippet in place, so every email that uses it picks up the change. Snippets stay where they were first created, even if you later choose a different folder. If a snippet with that name already exists and was not created from this project, Denada asks before replacing it, because the change affects every email that references it.
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 generic image.gif shared with other emails, the new image is uploaded under a slightly different name so nothing else is affected.

Troubleshooting

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.
Verify that your Installed Package has the required permissions: Documents & Images, Assets, Saved Content, and Email all need Read and Write access.
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.
For general information about how integrations work, see Integrations overview.

Need help?

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