Resources · Make integration

Flexmail Make integrationAutomate Flexmail with Make.

Can Make send and track your Flexmail emails without code? Yes. The Flexmail Make integration gives you 15 modules: 1 scheduled trigger, 11 actions and 3 searches. This guide is for marketers and ops teams, and takes you from the connection to a first working scenario.

Try the Flexmail integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Flexmail Make integration do for you?

The Flexmail Make integration links your Flexmail account to Make, a tool that chains apps together without code. You build a scenario, the automation itself, out of modules, the bricks that each do one job: spot new messages, send an email, manage senders and sending domains, or pull statistics.

Emails that go out on their own. A form entry, a signed quote or a paid invoice in another app can start a scenario that ends with Send a Message, so the right person gets the right email without anyone copying details across tools.

A tidy sending setup. Register a Sending Domain, Get a Sending Domain and List Sending Domains let an ops team add a domain, read its authentication status and keep an eye on the whole list from one scenario. Add a Sender and Delete a Sender follow the arrivals and departures in the team.

Numbers where people read them. Get Statistics brings the overall performance of your messages into a report, while Watch Messages and Get a Message log each new message in a shared sheet.

Whatever the listed modules leave out, Make an API Call can reach through the Flexmail API with the same connection. The Flexmail documentation on the Make side is flagged as AI-generated, so confirm important details with Flexmail. To size up Make itself, read the Make review, weigh it against n8n in n8n vs Make, or look at Make pricing.

Connect

How do you connect Flexmail to Make?

  1. 01

    Copy your Flexmail credentials

    In Flexmail, open Settings and copy the Account ID shown on that page. Then go to Settings, API, Personal access tokens, create a new personal access token and copy it as soon as it is displayed. Make needs both values.

  2. 02

    Add a Flexmail module to your scenario

    In your Make scenario, add any Flexmail module and click Create a connection. A connection is your Flexmail account linked to Make once, then reused by every Flexmail module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the credentials and confirm

    Enter the Account ID and the personal access token you copied, then follow the on-screen instructions to finish. Once the connection exists, Make can list what it reads in Flexmail while you fill the module fields.

First scenario

Your first Flexmail scenario: welcome a new lead by email

GoalWhen a new lead lands in another app, Make sends them a message through Flexmail.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. That first module belongs to the app where your leads arrive, such as your form tool or your CRM.

  2. 02

    Add Send a Message

    Click the + on the right of the first module, search for Flexmail and pick Send a Message. Choose your connection, or click Create a connection if this is your first Flexmail module.

  3. 03

    Map the lead into the email

    Fill the module fields and map the details received by the first module, like the lead's name and email address. A bundle is one item passed along, here one lead, so each lead gets its own email.

  4. 04

    Test with Run once

    Click Run once, then add a test lead in the first app with your own address. Open the bundles each module received to check the email left with the right details.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. From there, every new lead receives its welcome email at the next run, with nobody copying and pasting.

Triggers

What starts a Flexmail scenario

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

Flexmail1Watch Messages

Watch Messages

Scheduled trigger

In Make“Watches for new messages.”

Watch Messages picks up new messages in your Flexmail account and hands each one to the rest of the scenario as a bundle, so every new message can start a follow-up without anyone checking the account by hand.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, so a message reaches the scenario at the next check.
When to use it
when each new message should leave a trace elsewhere, like a row in a shared sheet or a note to the team that owns the campaign.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes; paid plans go down to 1 minute.
Modules

What Flexmail can do in Make

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

Flexmail1

Add a Sender

Action

In Make“Adds a sender for your email communication.”

Add a Sender creates a new sender for your email communication straight from a scenario, so nobody has to open the Flexmail settings each time the team grows.

When to use it
when a new colleague or a new brand is approved in your onboarding tool and should be able to send under its own name.
Watch out
if the scenario can fire twice for the same person, run List Senders first to avoid a duplicate.
Flexmail2

Delete a Sender

Action

In Make“Deletes a sender from email communication.”

With Delete a Sender, a sender you no longer use leaves your Flexmail account, which keeps the list short and clear for everyone who sends from it.

When to use it
when someone leaves the company and their offboarding checklist is closed in your HR or project tool.
Watch out
treat a deletion as final; place Get a Sender just before it to confirm you remove the right one.
Flexmail3

Delete a Sending Domain

Action

In Make“Deletes a registered sending domain.”

Delete a Sending Domain removes a domain you registered in Flexmail, which tidies the account once a brand or a site is out of use.

When to use it
when a campaign site is retired and its domain should disappear from your sending setup along with it.
Watch out
treat a deletion as final and pick the domain from List Sending Domains rather than typing it from memory.
Flexmail4

Get a Message

Action

In Make“Retrieves a single message details.”

Get a Message fetches the details of one message, so the following modules can reuse them: write them to a report, attach them to a ticket or pass them to a teammate.

When to use it
right after Watch Messages or List Messages, when you know which message you want but need its full details before acting.
Watch out
it reads a single message per bundle, and each read counts as one operation on your plan.
Flexmail5

Get a Sender

Action

In Make“Retrieves the details of a sender.”

Need to confirm a sender before using it? Get a Sender returns the details of one sender in your account, ready to map into the next module.

When to use it
as a safety check before Send a Message or Delete a Sender, when the scenario receives a sender from another app and you want to be sure it is the right one.
Watch out
if you do not know which sender to read yet, start with List Senders.
Flexmail6

Get a Sending Domain

Action

In Make“Retrieves the details of a configured sending domain, including its authentication status.”

Get a Sending Domain tells you where one of your domains stands, including its authentication status, so a scenario can react before anyone relies on it.

When to use it
after Register a Sending Domain, to check the status of the new domain before it goes into a campaign.
Watch out
it reports the status Flexmail holds; if the authentication is not in place, the fix happens outside Make.
Flexmail7

Get Statistics

Action

In Make“Retrieves statistics that gives insights about the overall performance of your messages.”

Get Statistics brings back figures on the overall performance of your messages, so the numbers land in a report or a dashboard without any manual export.

When to use it
when a campaign closes and the marketing lead wants its results in the shared sheet the team already reads.
Watch out
the figures describe your messages as a whole; to read the details of one specific email, use Get a Message.
Flexmail8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the way out when no listed module does the job: it calls any endpoint of the Flexmail API, using the connection you already set up.

When to use it
when you need a Flexmail feature that none of the other modules on this page covers.
Watch out
you write the request yourself, so keep the Flexmail API documentation open next to the module while you build it.
Flexmail9

Register a Sending Domain

Action

In Make“Registers a new sending domain.”

Register a Sending Domain adds a new domain to your Flexmail account from a scenario, so a fresh brand or client site joins your setup without a trip to the settings.

When to use it
when a new site goes live in your project tool and its domain should be registered as part of the launch.
Watch out
follow it with Get a Sending Domain to see the authentication status Flexmail reports for that domain.
Flexmail10

Send a Message

Action

In Make“Sends a new message.”

Send a Message is the module that actually emails someone: it sends a new message through Flexmail, with details mapped from earlier modules such as a contact's name.

When to use it
when an event in another app, like a signed quote or a new form entry, should end with an email to the person concerned.
Watch out
test with Run once on your own address first; once the scenario is on, every run reaches real people.
Flexmail11

Update a Sending Domain

Action

In Make“Updates a registered sending domain.”

Update a Sending Domain changes a domain already registered in Flexmail, so you keep it in step with your records instead of deleting it and starting over.

When to use it
when the information about a domain changes on your side and Flexmail should follow without a manual edit.
Watch out
select the domain through List Sending Domains or Get a Sending Domain first, so the update lands on the right one.
Flexmail12

List Messages

Search

In Make“Retrieves a list of messages.”

List Messages returns the messages in your account as separate bundles, one per message, so each can travel through the rest of the scenario on its own.

When to use it
for a one-off audit, when you want every message in a sheet rather than only the new ones Watch Messages would catch.
Watch out
a search can return zero, one or many bundles, and each module after it runs once per bundle, which adds operations.
Flexmail13

List Senders

Search

In Make“Retrieves the collection of senders in the account.”

Every sender your account holds comes back from List Senders, each as its own bundle, which gives you a quick inventory without opening Flexmail.

When to use it
before Add a Sender, to check the sender does not exist yet, or while you tidy the account after a change in the team.
Watch out
plan for the case where the search returns zero bundles, so the rest of the scenario behaves as you expect.
Flexmail14

List Sending Domains

Search

In Make“Retrieves a collection of the registered sending domains.”

List Sending Domains gives back the domains registered in your account, one bundle each, so a scenario can go through them one by one.

When to use it
paired with Get a Sending Domain, to review the authentication status of every domain in a single pass.
Watch out
each domain it returns runs the next modules once, so a long list means more operations on your plan.
Need help

Need help automating Flexmail with Make?

A person reads every message.

FAQ

Flexmail and Make: common questions

01Is the Flexmail Make integration free?
Yes, on the Make side. Flexmail is a standard app, available from the Free plan. That plan allows 2 active scenarios, a gap of at least 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) bring the minimum interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need an active Flexmail account; for its subscription, the Make documentation points to the Flexmail pricing page.
02What do you need to connect Flexmail to Make?
An active Flexmail account with its Account ID and a personal access token. You find the Account ID on the Settings page of Flexmail. The token is created under Settings, API, Personal access tokens, and it is displayed right after creation, so copy it then. In Make, add any Flexmail module, click Create a connection, give it a name if you like, and paste both values. That connection is then reused by every Flexmail module in your scenarios.
03Does the Flexmail trigger in Make fire in real time?
No. Watch Messages is a scheduled trigger: Make checks Flexmail on the scenario's schedule, every 15 minutes by default, and picks up the new messages at each check. On the Free plan, 15 minutes is also the shortest possible interval. Paid plans let you go down to 1 minute. Flexmail has no instant trigger in Make, so if an email must go out the moment something happens elsewhere, start the scenario from the other app and end it with Send a Message.
04What if a Flexmail module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Flexmail API with the connection you already created, so you can cover what the 15 listed modules leave out. You write the request yourself, which means reading the Flexmail API documentation first. Also note that the Flexmail documentation on the Make side is marked as AI-generated and may contain mistakes, so check important details with Flexmail directly before relying on them in a live scenario.
05Should you use Make or n8n for Flexmail?
It depends on the tool you already work in. On Make, Flexmail comes with 15 ready modules, from sending messages to managing senders and sending domains, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether one exists for Flexmail and what it covers before you choose. Compare the two on the actions your process needs, not on the logo, and pick the one your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations