Resources · Make integration

Resend Make integrationAutomate Resend with Make.

Can Make send your emails through Resend without a line of code? Yes. The Resend Make integration gives you 3 modules: one instant trigger and 2 actions. This guide is for builders who already use Resend, and it walks you from the API key to a working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Resend Make integration do?

The Resend Make integration links your Resend account to Make, a visual tool where you build a scenario (the automation itself, a chain of blocks called modules). Once linked, Make can send emails through Resend, react to events on your Resend account, and call any part of the Resend API, all without writing code.

Transactional emails driven by other tools. A new order, a signup or a booking in another app starts the scenario, and Send an Email ships the message through Resend with the data Make just received. Your product code stays out of it.

Follow-up on what happens to your emails. Watch Events fires the moment Resend reports a new event, so you can log it in a spreadsheet or alert a teammate in a chat tool.

Everything the two other modules skip. Make an API Call reuses your connection to reach any endpoint of the Resend API, which covers needs the ready-made modules do not.

One honest limit: the Make documentation for Resend is flagged as AI-generated, so check important details against Resend itself. If a scenario misbehaves, the Make troubleshooting guide helps you read the error. Weighing tools before you commit? The n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect Resend to Make?

  1. 01

    Copy your Resend API key

    In Resend, open the dashboard, click Settings in the sidebar, then API Keys. Copy the key shown on screen. You need an active Resend account for this; the key is what lets Make act on your behalf.

  2. 02

    Add a Resend module in Make

    Log in to Make, add any Resend module to your scenario and click Create a connection. A connection is your Resend account linked to Make once, then reused by every Resend module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, and save. Make keeps the link for every later module.

First scenario

Your first scenario with Resend and Make

GoalWhen a new entry lands in another app, Make sends an email to that person through Resend.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. The first module you add decides when the scenario starts, so pick the app where your new entries appear.

  2. 02

    Set the starting module

    Search that app by name, choose its trigger and link your account. Fill its fields: Make lists what it can read, such as a sheet or a form, once the connection exists.

  3. 03

    Add Send an Email

    Click the + on the right of the first module, search Resend and pick Send an Email. Select your Resend connection, then map the recipient and the content from the data the first module passes along.

  4. 04

    Test with Run once

    Click Run once and create a test entry in the source app. Each module shows the bundles it received (a bundle is one item passed along, here one entry), so you can check the email went out as planned.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Save, then switch the scenario on.

Triggers

What triggers a Resend scenario?

1 module starts a scenario when something happens in Resend. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Resend as soon as it happens.

Resend1Watch Events

Watch Events

Instant trigger

In MakeTriggers when a new event has happened.

Watch Events starts your scenario whenever Resend reports a new event on your account, so the reaction happens without anyone checking the dashboard. Each event reaches Make as its own bundle, ready to be logged, forwarded or used to decide the next step.

How it fires
it is an instant trigger, meaning Resend calls Make through a webhook as soon as the event happens, with no polling interval to wait for.
When to use it
pick it when a Resend event should push work somewhere else, such as a row in a tracking sheet or a message to support.
Watch out
click Create a webhook before Create a connection, and avoid sending an email from the same scenario, or each email could fire the trigger again.
Modules

What can Make do in Resend?

Resend gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Resend1

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

This module opens the whole Resend API to your scenario, with the connection you already set up, so you are not limited to what the other modules offer.

When to use it
reach for it when Send an Email and Watch Events do not cover the task, and the Resend API documentation shows an endpoint that does.
Watch out
you describe the request yourself, so read the Resend API reference before running it.
Resend2

Send an Email

Action

In MakeSends an email.

Send an Email delivers a message through your Resend account, built from the data earlier modules pass along, so every new record in another tool can become a personal email.

When to use it
choose it for one-to-one messages triggered by an event elsewhere, such as a signup confirmation after a form entry.
Watch out
each email counts as an operation on your Make plan, so test with Run once before switching the scenario on.
Need help

Need help automating Resend with Make?

A person reads every message.

FAQ

Resend and Make: common questions

01Is the Resend Make integration free?
Yes, on the Make side. Resend is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Resend subscription is separate and follows Resend's own pricing.
02What do you need to connect Resend to Make?
An active Resend account and an API key. In Resend, go to the dashboard, open Settings in the sidebar, then API Keys, and copy the key. In Make, add a Resend module, click Create a connection, give the connection a name if you like, and paste the key. For the instant Watch Events trigger, click Create a webhook first, then Create a connection. The same connection then serves all 3 Resend modules.
03Does the Resend trigger in Make work in real time?
Yes. Watch Events is an instant trigger: Resend calls Make through a webhook as soon as a new event happens, so the scenario starts right away instead of waiting for a polling interval. The lightning badge on the module marks this. Scenarios that start from another app with a scheduled trigger behave differently: they run on the schedule you set, every 15 minutes by default, and never faster than 15 minutes on the Free plan.
04What if the Resend module you need is missing in Make?
Use Make an API Call. It reuses your Resend connection and can call any endpoint of the Resend API, so a task that neither Send an Email nor Watch Events covers is still within reach. You write the request yourself, based on the Resend API reference. Keep in mind that the Make documentation for Resend is marked as AI-generated and may contain mistakes, so confirm important details with Resend before relying on them.
05Should you use Make or n8n for Resend?
It depends on how you prefer to build. On Make, Resend comes with 3 modules: an instant trigger, a sending action and a universal API call, all set up through the visual editor with a single connection. Many apps also have an n8n node, so check whether one exists for Resend before choosing. Compare the modules each tool offers for your use case and pick the editor your team is most at ease with.