Resources · Make integration

Zapster API Make integrationAutomate Zapster API with Make.

Need other tools to send messages through your Zapster API account? The Zapster API Make integration gives you 2 actions: Send a Message and Make an API Call. This guide walks ops and support teams through the token setup and a first working scenario.

Try the Zapster API integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zapster API Make integration do for you?

The Zapster API Make integration links your Zapster API account to Make so that a scenario, the automation you build in Make as a chain of modules, can send messages for you. A module is one brick of that chain. Zapster API brings two of them, both actions: they act when something earlier in the scenario hands them data.

Confirm an order without typing it. For an online shop, a new order in the store app starts the scenario, and Send a Message builds its text from the order details Make passes along. Each order becomes one message, sent from your Zapster API account.

Warn the team when a form comes in. A form tool catches a request, Make reads each answer as a bundle (one item flowing from one module to the next), and Send a Message relays it. The same pattern works with the 123FormBuilder Make integration.

Reach an endpoint the list skips. When you need something from the Zapster API that Send a Message does not cover, Make an API Call calls that endpoint with the same connection.

Know the limits before you start. Zapster API has no trigger, so it never starts a scenario by itself: another app or the scenario's schedule does. Make also flags its Zapster API documentation as AI-generated and possibly wrong, so check anything important with Zapster API. The same app may also exist as an n8n node; the n8n vs Make comparison helps you pick a tool, and the Make pricing page explains what each run costs.

Connect

How do you connect your Zapster API account to Make?

  1. 01

    Generate a token in Zapster API

    Sign in to your Zapster API account, open the Tokens section of the dashboard and click Generate Token. Copy the API key that appears on screen. You need an active Zapster API account for this, so create one first if you are new.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the instructions Make shows on screen, then confirm. The connection now appears in the module's dropdown, ready for the next Zapster API module you add.

First scenario

Build your first scenario with Zapster API

GoalWhen a new entry lands in another app, Make sends a message through Zapster API.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since Zapster API has no trigger, pick the trigger of the app where new entries appear, such as your form tool or store.

  2. 02

    Add Send a Message

    Click the + on the right of that first module, search for Zapster API and choose Send a Message. Select your connection, or click Create a connection if this is your first Zapster API module.

  3. 03

    Map the message

    Fill the fields of Send a Message. Click inside a field and Make offers the data from the first module, so the text can reuse a name, an order number or an answer instead of fixed words.

  4. 04

    Test with Run once

    Click Run once, then create a test entry in the first app. Then read the bundles each module received and check the message went out as planned.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation, the unit Make counts on your plan.

Modules

What can the Zapster API modules do?

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

Zapster API1

Make an API Call

ActionIn the docs only

Reach any endpoint of the Zapster API from your scenario, reusing the connection you already created, so you are not limited to what the ready-made module offers.

When to use it
the thing you need from Zapster API is not a plain message send, and no other module in the list covers it.
Watch out
you describe the request yourself, so read the Zapster API documentation first and verify it, since Make's copy may contain mistakes.
Zapster API2

Send a Message

ActionIn the docs only

Get a message sent from your Zapster API account each time the scenario reaches this module, with its text built from data earlier modules passed along.

When to use it
an event in another app, like a paid order or a new form entry, should turn into a message without anyone copying details by hand.
Watch out
the module runs once per bundle it receives, so a list of ten entries sends ten messages; test with Run once before switching on.
Need help

Need help automating Zapster API with Make?

A person reads every message.

FAQ

Zapster API and Make: common questions

01Is the Zapster API Make integration free?
Yes, on the Make side. Zapster API is a standard app, so it is available 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 and remove the cap on active scenarios. Your Zapster API subscription is separate and depends on Zapster API's own pricing page.
02What do you need to connect Zapster API to Make?
You need an active Zapster API account and an API token. In the Zapster API dashboard, open the Tokens section, click Generate Token and copy the key shown on screen. In Make, add a Zapster API module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves both modules, Send a Message and Make an API Call, in every scenario you build.
03Can Zapster API start a Make scenario in real time?
No. Zapster API has no trigger module in Make, so it cannot start a scenario on its own. The scenario opens on another app instead: an instant trigger, which that app calls through a webhook as soon as something happens, or a scheduled trigger, which Make checks at the interval you set on the first module, every 15 minutes by default. Zapster API then acts further down the chain, through Send a Message or Make an API Call.
04What if the Zapster API module you need is missing in Make?
Use Make an API Call. It lets the scenario call any endpoint of the Zapster API with the connection you already set up, so anything the API offers beyond Send a Message stays within reach. You write the request yourself, which means reading the Zapster API documentation first. Make flags its own Zapster API pages as AI-generated and possibly inaccurate, so confirm important details with Zapster API before relying on a request in production.
05Should you use Make or n8n for Zapster API?
It depends on the tool your team already works in. This page only documents the Make side: 2 modules, Send a Message and Make an API Call, one token-based connection and no trigger. Many apps also have an n8n node, so check whether Zapster API is one of them before you decide. The choice comes down to which editor your team prefers, and the n8n vs Make comparison linked above lays out the criteria side by side without a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations