Resources · Make integration

Smaily Make integrationAutomate Smaily with Make.

Keep Smaily in step with the rest of your tools, without writing code. The Smaily Make integration offers 16 modules, 9 actions and 7 searches. This guide takes Smaily marketers from the connection to a first live scenario.

Try the Smaily integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Smaily Make integration do for you?

The Smaily Make integration links your Smaily account to Make, a no-code tool where you build a scenario: a chain of modules that runs on its own. Each module is one brick of that chain. For Smaily, a module either changes something (an action) or reads data back (a search). Smaily has no trigger, so another app or a schedule starts the flow.

Signups that land in the right workflow. A form tool or an online shop hands over the new contact, Update Subscriber Data stores it with its custom parameters, and Trigger Automation Workflow starts the welcome sequence you already designed in Smaily.

Campaign reports without manual exports. List Campaigns finds the sends you care about, Get Campaign Statistics reads each one, and the numbers go to a spreadsheet or a BI tool. For experiments, List A/B Tests and Get A/B Test Statistics do the same job.

Privacy requests handled cleanly. When a deletion request reaches your helpdesk, Forget Subscriber erases the person's data through a call built for GDPR requests.

Some things stay out of reach. Smaily cannot start a scenario on its own: nothing fires when someone clicks or opts out, so a schedule (every 15 minutes by default) or another app has to kick things off. Both action logs only go back 30 days. For an endpoint without a module, Make an API Call fills the gap.

Before building, the Make review walks through the editor, Make pricing explains how operations are counted, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect Smaily to Make?

  1. 01

    Add a Smaily module

    Log in to Make, open your scenario and add any Smaily module. In the module window, click Create a connection. A connection is your Smaily account linked to Make once, then reused by every Smaily module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps as soon as you manage more than one Smaily account, for instance one per brand or per client. Pick something you will recognize in a list.

  3. 03

    Paste your Smaily credentials

    Enter the subdomain, username and password you copied from Smaily, or follow the instructions on screen. Make saves the connection, and the module can now list the data it reads from your account.

First scenario

Your first scenario with Smaily

GoalWhen a form app records a new signup, Make updates the contact in Smaily and starts your welcome workflow.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Add the first module from your form app, the one that reacts to each new submission.

  2. 02

    Add Update Subscriber Data

    Click the + on the right of the form module, search for Smaily and pick Update Subscriber Data. Click Create a connection and paste your subdomain, username and password.

  3. 03

    Map the signup

    Fill the module by mapping the answers of the form module into the subscriber fields Make shows. Each signup travels as one bundle, a single item passed from one module to the next.

  4. 04

    Start the welcome workflow

    Click the + again and choose Trigger Automation Workflow. Select the workflow prepared in Smaily and map the address from the form. The same connection is reused.

  5. 05

    Test with Run once

    Click Run once, send a test entry through the form, then open the bundles each module received to check the contact reached Smaily with the right data.

  6. 06

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on, and every new signup now follows the same path.

Modules

What each Smaily module does in Make

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

Smaily1

Create and Launch Campaign

Action

In Make“Launches a new campaign with a custom HTML template to an existing list.”

Sends a brand-new campaign, built from your own HTML template, to a list that already exists in Smaily. You get a finished send straight from the scenario, without opening the Smaily editor.

When to use it
your CMS or a design tool has produced the newsletter layout and it should reach its audience as soon as it is ready.
Watch out
the list must exist beforehand; check it with List Subscribers from Filter if you are unsure who will receive it.
Smaily2

Forget Subscriber

Action

In Make“Forgets a subscriber's personal data, a GDPR-compliant API-call.”

Erases one subscriber's personal data from Smaily through a call designed for GDPR requests, so a deletion request is honored by the scenario instead of by hand.

When to use it
a customer asks to be forgotten through your helpdesk or a privacy form, and the request should reach Smaily without anyone copying addresses around.
Watch out
no module restores erased data, so treat the step as final and run Get Subscriber Data first if you need a trace of what was removed.
Smaily3

Get A/B Test Statistics

Action

In Make“Endpoint can be used to retrieve overview and detailed statistics of an A/B test.”

Brings back the overview and the detailed figures of one A/B test, ready to be written into a report, a sheet or a message to your team.

When to use it
a subject line test has run and the marketing team wants the results next to the rest of its numbers, not buried in Smaily.
Watch out
the module reads one test at a time; place List A/B Tests before it to get the tests you want to read.
Smaily4

Get Campaign Statistics

Action

In Make“Retrieves a campaign's information, including addresses sent to and statistics.”

Pulls one campaign's information, including the addresses it was sent to and its statistics, into the scenario so you can file or share it.

When to use it
results of each send should land in a spreadsheet or a CRM without anyone exporting a report by hand.
Watch out
it covers a single campaign; pair it with List Campaigns to process several, each campaign arriving as its own bundle and costing its own operation.
Smaily5

Get Subscriber Data

Action

In Make“Loads all of a subscriber's parameters from database.”

Loads every parameter Smaily holds about one subscriber, so the next modules can use the full profile rather than just an address.

When to use it
before updating a CRM record or answering a support ticket, you want to see what the newsletter tool knows about that person.
Watch out
this is a one-person lookup; to fetch a whole segment, List Subscribers from Filter is the better pick.
Smaily6

Send Message

Action

In Make“Sends a transactional message, optionally with attachments. Does not trigger automation workflows.”

Delivers a transactional email to one person the moment the scenario runs, with attachments when the message needs them.

When to use it
an order confirmation, an invoice or an account notice that has to follow an event recorded in another app.
Watch out
this send does not start any automation workflow; if the recipient should also enter a sequence, add Trigger Automation Workflow right after it.
Smaily7

Trigger Automation Workflow

Action

In Make“Triggers an automation workflow for addresses sent with the API-call.”

Starts one of your Smaily automation workflows for the addresses you pass in, so a nurture or onboarding sequence begins without a click inside Smaily.

When to use it
a lead fills a form or a deal changes stage in your CRM, and the matching email sequence should follow on its own.
Watch out
every address mapped into the module enters the workflow, so double-check the mapping with Run once before switching the scenario on.
Smaily8

Unsubscribe Subscriber from Specific Campaign

Action

In Make“Unsubscribes a subscriber from a specific campaign. Useful for custom opt-out landing pages.”

Opts one subscriber out of a specific campaign, which lets your own opt-out page carry the choice back to Smaily.

When to use it
you host a custom unsubscribe landing page, with your branding and your wording, and its answers must reach Smaily without manual edits.
Watch out
the module targets one campaign, so make sure the page tells people exactly what they are leaving.
Smaily9

Update Subscriber Data

Action

In Make“Updates a subscriber and their custom parameters in database.”

Writes changes to a subscriber, custom parameters included, so Smaily holds the same information as your shop, CRM or form tool.

When to use it
a customer edits a profile elsewhere and your Smaily segments depend on those values, such as a city or a plan name.
Watch out
each subscriber sent through counts as one operation, the unit Make counts on your plan, so a large sync adds up quickly.
Smaily10

List A/B Tests

Search

In Make“This endpoint can be used to list A/B tests of an organization. Status and tag-based filters can be applied to return specific A/B tests.”

Returns the A/B tests of your Smaily organization, narrowed by status or by tag, with one bundle for each test found.

When to use it
you tag tests per product line and want only the tests with a given tag or status to flow into Get A/B Test Statistics.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
Smaily11

List Automation Workflows

Search

In Make“This endpoint returns a list of automation workflows of an organization.”

Gives you the automation workflows set up in your Smaily organization, handy for keeping an inventory or for picking one to start later in the scenario.

When to use it
several teams build workflows in the same account and you want a shared sheet that shows what exists.
Watch out
if the search comes back empty, nothing after it runs, which is worth knowing when a Run once test seems to do nothing.
Smaily12

List Campaigns

Search

In Make“Lists campaigns, can be filtered”

Hands the scenario your campaigns as a list you can filter, each campaign flowing on as a separate bundle.

When to use it
a reporting scenario should walk through past sends and pass each one to Get Campaign Statistics.
Watch out
without a filter you may pull far more campaigns than you need, and each extra bundle spends operations in the modules that follow.
Smaily13

List Message Action Log

Search

In Make“This endpoint can be used to fetch subscriber’s message actions (e.g. sent message, clicks, opt-outs, etc). Note! Message Action Log contains only actions from the last 30 days.”

Shows what happened to the messages a subscriber received: sends, clicks, opt-outs and similar actions, ready to be read by the next module.

When to use it
support needs to know whether a customer clicked the link in a message before answering a complaint.
Watch out
Smaily keeps only the last 30 days in this log, so older activity will not come back.
Smaily14

List Subscriber Action Log

Search

In Make“Endpoint can be used to request a list of subscriber actions in time sorted order (older actions first). Note! Subscriber Action Log contains only actions from the last 30 days.”

Returns a subscriber's actions in time order, which helps you rebuild how that person has interacted with your emails lately.

When to use it
ahead of a sales call, the account manager wants the lead's recent activity pasted into the CRM record.
Watch out
only the last 30 days are kept, and the oldest action comes first, so the most recent one arrives last.
Smaily15

List Subscribers from Filter

Search

In Make“Lists subscribers with all of their additional parameters from a filter / list.”

Fetches the subscribers of a filter or a list with all their additional parameters, one bundle per person.

When to use it
you mirror a Smaily segment into a CRM or a spreadsheet, or you want to check an audience before Create and Launch Campaign sends to it.
Watch out
every subscriber becomes a bundle, and each later module spends an operation on each one of them.
Smaily16

Make an API Call

Search

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Smaily API to your scenario, reusing the same connection, for anything the other 15 modules do not cover.

When to use it
the endpoint you need exists in Smaily but has no ready-made module in Make.
Watch out
you write the request yourself, so keep the Smaily API documentation open next to the editor and test with Run once.
Need help

Need help automating Smaily with Make?

A person reads every message.

FAQ

Smaily and Make: frequent questions

01Is the Smaily Make integration free?
Yes, on the Make side. Smaily is a standard app, so its modules work on 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 and lift the scenario cap. Your Smaily subscription is separate and follows Smaily's own pricing page.
02What do you need to connect Smaily to Make?
An active Smaily account and a set of API credentials. In Smaily, open Preferences from your account name, go to the Integrations tab and click Create a new user under API Passwords. Copy the subdomain, the username and the password displayed. Back in Make, add a Smaily module, click Create a connection, give it a name if you like, and paste those three values. Every Smaily module then reuses that connection.
03Can Smaily start a Make scenario in real time?
No. Smaily has no trigger module in Make, so it cannot start a scenario by itself when a subscriber clicks or opts out. You have two ways around it. Start the scenario with a trigger from another app, such as a form tool or a shop, and put Smaily modules after it. Or run the scenario on a schedule: a new scenario runs every 15 minutes by default, and the Free plan does not go below that.
04What if a Smaily module you need is missing in Make?
Use Make an API Call. It lets the scenario call any endpoint of the Smaily API with the connection you already set up, so you are not limited to the 16 listed modules. You write the request yourself, which asks for a look at Smaily's API documentation. Keep in mind that the two action logs only return the last 30 days; older history is not available through those modules, so export what you need to keep.
05Should you pick Make or n8n for Smaily?
It depends on what you need to cover. On Make, Smaily comes with 16 modules for campaigns, subscribers, workflows and statistics, plus Make an API Call for the rest, and no trigger. This page only documents the Make side, so before choosing, check whether n8n offers a Smaily node with the actions you rely on. The deciding criteria are then the modules available for your use case and the tool your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations