Skip to main content
The Email Love Figma Plugin connects directly to Make (formerly Integromat) via a Custom Webhook trigger, so you can take a Figma email design and pipe it into any Make scenario: an ESP that doesn’t have a native integration, a CMS, a Notion database, Slack, Airtable, your CRM, etc. Download the Email Love Figma Plugin here

​
How it works

  1. You create a Make scenario starting with a Webhooks → Custom webhook trigger module
  2. Make gives you a webhook URL
  3. You paste that URL into the Email Love plugin’s Make export
  4. When you click Export, the plugin POSTs each selected email (name, subject, preheader, HTML) to the scenario, which then runs whatever modules you set up

​
Prerequisites

  • A Make account
  • The Email Love Figma plugin installed
  • At least one email designed in Figma using the plugin
  • An Email Love Footer with an Unsubscribe link in your design
1

Create the Scenario and Get a Webhook URL

There’s a How to get a Make webhook URL link in the export panel that jumps to Make’s docs. The short version:
  1. In Make, click Create a new scenario
  2. Add a module and search for Webhooks
  3. Choose the Custom webhook trigger
  4. Click Add to create a new webhook, give it a name (e.g. “Email Love Export”), and click Save
  5. Make displays a webhook URL like https://hook.eu2.make.com/abc123.... Copy it.
  6. Leave the webhook listening. Make will say “Successfully determined” once it receives a sample.
2

Set Up the Export in the Plugin

  1. Select the email frame(s) you want to export. Multi-select to fire several templates through the same scenario.
  2. Click the Export button in the top right of the plugin
  3. Pick Make from the Export dropdown
  4. Paste the Make webhook URL into the Make Webhook URL field
  5. (Optional) Custom headers: JSON object for request headers, e.g. auth tokens. Most Make webhooks don’t need this.
  6. (Optional) Extra JSON data: JSON object merged into the payload body, e.g. workspace IDs, tags
  7. Give it a name in the Make connection name field so you can reuse this config later
  8. Click Save Connection
The saved connection appears under API Connections → Connect with an existing API Key so you can switch between Make scenarios without re-entering URLs.
3

Set Output Options

Two toggles at the bottom of the panel:
  • Upload hosted images URLs (on by default): Uploads your images to Email Love’s CDN and references them as src URLs in the HTML payload, so Make receives a complete email that renders in any inbox. Leave on.
  • HTML Minification (off by default): Strips whitespace from the output HTML. Optional.
4

Set Subject and Preheader per Frame

Each selected frame has its own Email Subject line and Preheader text inputs at the bottom of the export panel, with a Preview icon to see them in context. These values are sent in the payload as the subject and preheader fields, so set them before exporting.If you multi-select multiple frames, each frame gets its own subject and preheader inputs, so you can customise each one before a batch export.
5

Send a Sample Payload

Before building the rest of the scenario, send Make a sample payload so it can detect the data structure for later modules.
  1. With the Make webhook still listening, click Export to MAKE in the plugin
  2. Switch to Make. The Custom webhook module should now show Successfully determined, with the name, subject, preheader, and html fields available for mapping downstream.
6

Build the Rest of the Scenario

Add whatever modules you need. Common patterns:
  • Gmail → Create a Draft with html as the body
  • HTTP → Make a request to push the HTML into an ESP without a native Email Love integration
  • Notion → Create a Database Item to log every export
  • Slack → Create a Message to notify a #email channel
Map the fields from Step 5 into your modules. The html field is the full ready-to-send email.
7

Activate the Scenario

Flip the scenario’s switch to ON in Make. From then on, every time you click Export to MAKE in the plugin, the scenario runs.

​
Payload Format

Each template is sent as its own POST request: 
{
  "name": "Frame name from Figma",
  "subject": "Email subject line",
  "preheader": "Preheader text",
  "html": "<html><head>...</head><body>...</body></html>"
}
If you multi-select multiple frames, each one is POSTed individually. The scenario runs once per template.

​
Adding Custom Fields or Headers

The Custom headers and Extra JSON data fields work the same way as in the Custom Webhook export. Use them to send auth headers, tags, workspace IDs, or any other data your scenario needs.

​
Troubleshooting

Make never received the test: Check the webhook URL. Make’s URLs start with https://hook.<region>.make.com/. Webhook module shows the wrong field structure: Right-click the module and choose Redetermine data structure, then re-export from the plugin. Scenario fires but html is empty: Make sure your design has at least one Email Love section/component. Empty frames don’t generate HTML. Subject or preheader is empty in Make: Each frame has its own Subject and Preheader inputs at the bottom of the export panel. Scroll down to the frame’s section and fill them in before clicking Export. Got several runs from one export: Each frame is sent as its own request, so each frame triggers the scenario once. If you only wanted one run, select a single frame. Scenario eating ops faster than expected: Each export = one run per scenario, plus one op per module that fires. For high-volume sends, export fewer frames at a time or simplify the scenario. Unsubscribe link not working: Make sure your design includes an Email Love Footer with an Unsubscribe link. Need help? Reach out at hello@emaillove.com or join our Discord community.