Resources · Make integration

Swift Missive Make integrationAutomate Swift Missive with Make.

Can Make push your contacts and events into Swift Missive? Yes. The Swift Missive Make integration has 1 module, Make an API Call, which reaches the Swift Missive API with your own keys. This guide shows marketers how to connect the account and build a first working scenario.

Try the Swift Missive integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Swift Missive Make integration do for you?

The Swift Missive Make integration links your paid Swift Missive account to Make, so a scenario (the automation you build in Make, a chain of modules) can send data to Swift Missive without anyone copying it by hand. It offers one module, a brick of the scenario: Make an API Call.

A module that calls the API sounds technical, but the idea is plain. Another app starts the scenario, and Make an API Call hands the data to Swift Missive. The Swift Missive documentation on Make describes two such requests: sending a contact, which needs at least an email, and sending an event, which needs the contact's email plus the event name.

Picture a web form that collects sign-ups. Each new entry becomes a contact in Swift Missive, email included, as soon as the form app's module hands it to Make. Or take an online shop: a completed order becomes an event tied to the buyer's email, so the right follow-up can start. A third pattern skips any outside trigger and runs on Make's clock, reading rows from a spreadsheet and sending each one as a contact.

Know the limits before you start. Swift Missive has no trigger in Make, so nothing in Swift Missive can start a scenario by itself. There is also no ready-made action for each task: every request goes through Make an API Call. If that feels new, the Make training covers the editor from scratch, and Make pricing explains how operations are counted.

Many apps also have an n8n node. If you are weighing both tools, the n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect Swift Missive to Make?

  1. 01

    Copy your two keys in Swift Missive

    Log in to Swift Missive and open Account > Integrations. Copy the API key and the Gateway key, then keep both somewhere safe. Make asks for the two values, and one without the other will not do.

  2. 02

    Open the connection window in Make

    Add the Swift Missive module to your scenario and click Create a connection. A connection is your Swift Missive account linked to Make once and reused later. You can type a label in Connection name if you like.

  3. 03

    Paste the keys and save

    Put the first value in the API key field and the second in Gateway key, then click Save. If Swift Missive asks you to authenticate, confirm access, and the connection is ready.

First scenario

Build your first scenario with Swift Missive

GoalWhen a new sign-up lands in another app, Make sends it to Swift Missive as a contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your sign-ups arrive, such as a form tool, and choose its module that brings in new entries.

  2. 02

    Set up the first module

    Connect that app and fill its fields. Make lists what it can read once the connection exists, so you pick the form instead of typing its name. Each entry becomes a bundle, one item passed to the next module.

  3. 03

    Add Make an API Call

    Click the + on the right, search for Swift Missive and choose Make an API Call with your connection. Aim it at the contact request and map the email from the first module into it.

  4. 04

    Test with Run once

    Submit a test entry, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can confirm the contact reached Swift Missive with its email.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, the minimum on the Free plan. Keep that or pick another interval, then switch the scenario on.

Modules

The Swift Missive module in Make

Swift Missive gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Send a Contact Requirements: The contact record must include the Email at least.

Send an Event The event record must include at least the Email of the contact that performed the event, as well as the Event Name.

Swift Missive1

Make an API Call

ActionIn the docs only

This module gives you access to any endpoint of the Swift Missive API from inside your scenario, using the same connection and keys you saved once. Since it is the only Swift Missive module, every task on this page goes through it.

When to use it
a contact or an event must reach Swift Missive right after something happens in another app.
Watch out
the documentation requires at least an email for a contact, and an email plus an event name for an event, so map both before testing.
Need help

Need help automating Swift Missive with Make?

A person reads every message.

FAQ

Questions about the Swift Missive Make integration

01Is the Swift Missive Make integration free?
Yes, on the Make side. Swift Missive is a standard app, so it works from the Free plan, which allows 2 active scenarios, 15 minutes at least between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Each operation, meaning one module run on one bundle, counts toward your plan. Swift Missive itself still needs a paid account, according to its documentation.
02What do you need to connect Swift Missive to Make?
You need a paid Swift Missive account with its onboarding completed, plus two values from Account > Integrations in Swift Missive: the API key and the Gateway key. In Make, you add the Swift Missive module, click Create a connection, paste both keys into their fields and save. If Swift Missive asks you to authenticate, you confirm access. The connection is then reused by every Swift Missive module in your scenarios, so this setup happens only once per account.
03Can Swift Missive start a Make scenario in real time?
No, Swift Missive has no trigger in Make, so it cannot start a scenario on its own. The scenario starts elsewhere. Either another app's trigger opens the flow, for example an instant trigger that the app fires through a webhook as soon as a form is sent, or you run the scenario on Make's schedule, every 15 minutes by default. Swift Missive comes next: Make an API Call receives the data from the module before it.
04What if the Swift Missive module you need is missing in Make?
It depends on what you need, but Make an API Call is the answer in most cases. This module can call any endpoint of the Swift Missive API with the connection you already set up, which covers what a dedicated module would do. The documentation mentions sending a contact and sending an event, with the email as the minimum for both and the event name for events. The documentation gives no numeric limit for the app, so none is quoted here. If a request still fails, read the bundles Make shows after Run once.
05Should you use Make or n8n for Swift Missive?
It depends on the tool your automations already live in. On Make, Swift Missive comes with one module, Make an API Call, a connection based on your API and Gateway keys, and availability from the Free plan. Many apps also have an n8n node, so check whether one exists for Swift Missive before deciding. Compare what each one offers for this specific app and pick the one that fits the rest of your stack.
Same platform

Other docs you might need on this stack.

Browse all integrations