Resources · Make integration

SMTP2GO Make integrationAutomate SMTP2GO with Make.

What if every piece of data SMTP2GO produces landed in your other tools on its own? The SMTP2GO Make integration offers 1 instant trigger. This guide shows how to link your account and build a first scenario that passes that data along.

Try the SMTP2GO integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SMTP2GO Make integration automate?

The SMTP2GO Make integration lets SMTP2GO start a scenario, which is the automation you build in Make, whenever it has data to hand over. It does this through a single module, Watch Events, and everything that follows it comes from other apps.

Think of Watch Events as a door. SMTP2GO pushes data through it, and each item arrives as a bundle, one item that flows from a module to the next. What you do with that bundle is up to the modules you place after it.

Keep a log your whole team can read. Send each bundle to a table, for example with the Airtable Make integration, so the history no longer lives only inside SMTP2GO.

Put SMTP2GO data next to your contacts. Pass it to a CRM such as the one covered in the Agile CRM Make integration, and sales sees what happened without opening another dashboard.

Warn someone when it matters. Add a filter between modules and route only the items you care about to a chat or an inbox.

Be clear about the limits. Make has no action module for SMTP2GO, no search and no "Make an API Call" module, so this page will not show you how to send emails from Make with it. Make itself flags its SMTP2GO documentation as AI-generated and advises checking important details with SMTP2GO directly. If you also look at n8n, the n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect SMTP2GO to Make?

  1. 01

    Add the trigger and open the connection

    In your scenario, search for SMTP2GO, choose Watch Events, then click Create a connection. A connection is your SMTP2GO account linked to Make once, then reused by every SMTP2GO module.

  2. 02

    Give the connection a clear name

    This step is optional, but a name like the account or the sending domain helps a lot once a colleague opens the scenario and needs to know which SMTP2GO account it talks to.

  3. 03

    Paste your API key and save

    Make asks for an SMTP2GO API key, so keep it at hand. Paste the key from your SMTP2GO account into the connection form and click Save. The connection is now ready for Watch Events.

First scenario

Build your first scenario with SMTP2GO

GoalWhen SMTP2GO sends data to Make, Make passes it straight to another app of your choice.

  1. 01

    Create an empty scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle becomes the first module of your automation.

  2. 02

    Place Watch Events first

    Type SMTP2GO in the search box, pick Watch Events and select the connection you built with your API key. This trigger now waits for SMTP2GO to send something.

  3. 03

    Add where the data should go

    Click the + on the right of Watch Events and choose the destination app, a sheet or a CRM for instance. Map the values coming from Watch Events into the fields of that module.

  4. 04

    Test it with Run once

    Click Run once, then wait for SMTP2GO to send data. Open the bubble above each module to read the bundle it received and confirm the mapping lands where you expect.

  5. 05

    Switch the scenario on

    Turn the scenario on from the editor. Since Watch Events is an instant trigger, the scenario reacts each time SMTP2GO calls Make, not on a clock you have to tune.

Triggers

What starts an SMTP2GO scenario?

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

SMTP2GO1Watch Events

Watch Events

Instant trigger

In Make“Watch All Data from SMTP2GO”

Watch Events gives you a scenario that starts on its own whenever SMTP2GO has data to hand over, so nobody has to copy anything out of the SMTP2GO dashboard. Each item it receives becomes a bundle that the next modules can read and reuse.

How it fires
instant: SMTP2GO calls Make through a webhook as soon as it happens, which is why the module carries the lightning badge instead of a clock.
When to use it
pick it when what happens in SMTP2GO should reach a spreadsheet, a CRM or a team chat without anyone waiting for a check.
Watch out
it is the only SMTP2GO module in Make, so every step after it has to come from another app or from Make's own tools.
Need help

Need help automating SMTP2GO with Make?

A person reads every message.

FAQ

SMTP2GO and Make: common questions

01Is the SMTP2GO Make integration free?
Yes. SMTP2GO is a standard app in Make, so you can use it from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two 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, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one execution of one module on one bundle. Your SMTP2GO subscription is a separate matter handled by SMTP2GO.
02What do you need to connect SMTP2GO to Make?
You need two things: an active SMTP2GO account and an API key from that account. In Make, add the Watch Events module, click Create a connection, give it a name if you like, paste the key and click Save. The connection is stored once and reused by any SMTP2GO module you add later. If you have no SMTP2GO account yet, create one first; SMTP2GO lists its subscription options on its own pricing page, and Make does not sell or include an SMTP2GO account.
03Does the SMTP2GO trigger in Make react in real time?
Yes. Watch Events is an instant trigger: SMTP2GO calls Make through a webhook as soon as something happens, and the scenario starts right away. In the editor it shows a lightning badge rather than the clock you see on scheduled triggers, which Make checks on the scenario's schedule. So the 15 minute default interval of a new scenario does not slow this trigger down. Keep in mind that the scenario must be switched on for SMTP2GO's calls to start anything.
04What if the SMTP2GO module you need is missing in Make?
It depends on what you need. Make offers only one SMTP2GO module, Watch Events, and this app has no Make an API Call module, so there is no generic way inside Make to reach other SMTP2GO features. What you can do is combine Watch Events with modules from other apps to act on the data it receives. If your process needs something beyond that, the team behind this page can look at your case and suggest another route before you build.
05Should you use Make or n8n for SMTP2GO?
It depends on where the rest of your automations already live. In Make, SMTP2GO gives you one instant trigger, Watch Events, that you pair with modules from other apps in a visual editor. If your team already runs its workflows in n8n, check what n8n offers for SMTP2GO before moving anything. Compare the tools on the modules you actually need and on how your team likes to work, not on reputation. The n8n vs Make comparison linked earlier on this page goes through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations