Resources · Make integration

SparkPost Make integrationAutomate SparkPost with Make.

Can your other tools send SparkPost emails on their own? The SparkPost Make integration gives you 3 modules: 1 instant trigger and 2 actions. This page shows you how to link your account and build a first scenario that sends an email without any code.

Try the SparkPost integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SparkPost Make integration let you automate?

The SparkPost Make integration links your SparkPost account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. Other apps can then ask SparkPost to send an email, and SparkPost can tell Make when it processes a new event.

Reply to a lead the moment they sign up. A form tool or a CRM starts the scenario, and Send an Email mails the new contact through your SparkPost account, with the name and details mapped from the previous module.

Pass SparkPost events to the rest of your stack. Watch New Events is an instant trigger: SparkPost calls Make through a webhook as soon as it processes a new event, and the next modules can log it in a sheet or alert your team.

Reach what the list does not cover. Make an API Call calls any endpoint of the SparkPost API with the same connection, so you are not stuck with two actions.

What Make does not do here: there is no search module, and the SparkPost doc in Make is flagged as AI-generated content, so check the important details with SparkPost itself. The same app often has an n8n node too; the n8n vs Make comparison helps you pick. To go further, read the Make review or the Make troubleshooting guide.

Connect

How do you connect SparkPost to Make?

  1. 01

    Create an API key in SparkPost

    In SparkPost, open the side navigation, click API Keys under Configuration, then Create API Key. Give it a name, tick the permissions you need, confirm, and copy the key shown on screen.

  2. 02

    Add a SparkPost module in Make

    In your scenario, add any SparkPost module and click Create a connection. The Connection name field is optional: a clear name helps when you later run several SparkPost accounts side by side.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the on-screen instructions, and save. The connection is your SparkPost account linked to Make once; every SparkPost module of your scenarios reuses it.

First scenario

Your first scenario: send a SparkPost email when a form arrives

GoalWhen a new entry lands in your form tool, SparkPost sends that person an email through Make.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the trigger of the app that collects your sign-ups.

  2. 02

    Add Send an Email

    Click the + on the right of that first module, search for SparkPost, pick Send an Email and choose the connection you created, or click Create a connection.

  3. 03

    Map the contact data

    Fill the module fields and map the email address and the name coming from the first module. Each bundle, one form entry here, becomes one email.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry to your form. Open each module to read the bundles it received and check that the email reached your inbox.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default, the shortest gap on the Free plan) and switch the scenario on. Each module run counts as one operation.

Triggers

What can start a SparkPost scenario?

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

SparkPost1Watch New Events

Watch New Events

Instant trigger

In Make“Triggers when a new event is processed.”

Watch New Events starts your scenario each time SparkPost processes a new event, so what happens in your sending account can flow into your other tools without anyone copying it by hand.

How it fires
instant: SparkPost calls Make through a webhook as soon as the event is processed, shown by the lightning badge on the module.
When to use it
you want a sheet, a chat channel or a CRM to hear about SparkPost activity as it happens.
Watch out
this module asks you to click Create a webhook before Create a connection; skip that step and Make has no address where SparkPost can send its events.
Modules

What can SparkPost do inside a Make scenario?

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

SparkPost1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the SparkPost API while reusing the connection you already set up, so you are not limited to the two ready-made actions.

When to use it
the job you need has no module of its own and the SparkPost API covers it.
Watch out
you write the request yourself, so the SparkPost API reference becomes your guide, and your API key must carry the permissions that endpoint expects.
SparkPost2

Send an Email

Action

In Make“Sends an email with your SparkPost.com account. You'll need an API key with at least the "Transmissions: Read/Write" permission.”

Send an Email mails a message through your SparkPost account, using the recipient and content you map from earlier modules, so a sign-up or an order can trigger a proper email.

When to use it
another app delivers a contact and you want SparkPost, not your inbox, to send the message.
Watch out
the API key needs at least the Transmissions: Read/Write permission, otherwise the module fails.
Need help

Need help automating SparkPost with Make?

A person reads every message.

FAQ

SparkPost and Make: common questions

01Is the SparkPost Make integration free?
Yes, on the Make side. SparkPost is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the gap down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, where each operation is simply one module running on one bundle of data. For the SparkPost subscription itself, check the SparkPost pricing page.
02What do you need to connect SparkPost to Make?
You need an active SparkPost account and a valid API key. Create the key in SparkPost under Configuration, then API Keys, give it a name and the permissions your scenario requires, and copy it. In Make, click Create a connection on a SparkPost module and paste the key. For Send an Email, the key has to carry at least the Transmissions: Read/Write permission. For the instant trigger, Make asks you to create a webhook first, then the connection.
03Does the SparkPost trigger in Make react in real time?
Yes. Watch New Events is an instant trigger: SparkPost calls Make through a webhook as soon as it processes a new event, so the scenario starts right away instead of waiting for a scheduled check. That is the lightning badge on the module. Scenarios that start from another app use that app's trigger instead, and a scheduled one runs every 15 minutes by default, which you change in the scheduling settings of the first module.
04What if the SparkPost module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the SparkPost API with the same connection, so tasks without a dedicated module stay within reach. You build the request from the SparkPost API reference, and your key needs the matching permissions. Keep in mind that the SparkPost documentation in Make is marked as AI-generated and may contain mistakes, so verify important details directly with SparkPost before you rely on them.
05Should you use Make or n8n for SparkPost?
It depends on the tool your team already works in. SparkPost often has an n8n node as well, so both can send its emails. On Make, you get 3 ready modules, an instant trigger through a webhook, and Make an API Call to reach the rest of the API. The fair test is to list the SparkPost tasks your scenario needs, check each one against the modules on both sides, and pick the platform where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations