Resources · Make integration

SwarmNode Make integrationAutomate SwarmNode with Make.

Your SwarmNode agents can start on their own when something happens in your other tools. The SwarmNode Make integration gives you 3 action modules and no trigger. This page shows how to link your account, build a first scenario and pick the right module.

Try the SwarmNode integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SwarmNode Make integration do for you?

The SwarmNode Make integration lets a Make scenario (the automation you build in Make, a chain of bricks called modules) start one of your SwarmNode agents and then fetch what that run produced. The event that kicks things off comes from another app or from a schedule, because SwarmNode has no trigger in Make.

An agent that reacts to your CRM. A sales rep adds a lead in another app, and that app's trigger starts the scenario. Execute an Agent hands the lead to the SwarmNode agent you built for it. No copy and paste between tabs.

A result you can reuse. Chain Get an Execution right after, so the scenario reads the run it just started and passes the output to the next module: a spreadsheet row, a message, a ticket. Each item that moves between modules is a bundle.

A call the listed modules do not cover. Make an API Call reaches any endpoint of the SwarmNode API with the same connection, which helps when you need something the two other modules skip.

Be aware of one limit: the Make documentation for SwarmNode is thin, and Make itself says it lacks public information about this app. Expect to read field names inside the module rather than in a guide. If a run fails, the Make troubleshooting page walks through the usual causes. Still unsure between tools? The n8n vs Make comparison and the Make pricing breakdown help you decide.

Connect

How do you connect SwarmNode to Make?

  1. 01

    Add a SwarmNode module

    In your scenario, click the +, search for SwarmNode and pick any of its modules. Then click Create a connection. A connection is your SwarmNode account linked to Make once and reused by every SwarmNode module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as your workspace or client pays off the day you run several SwarmNode accounts in the same Make organization. Make shows that name in every module dropdown.

  3. 03

    Authorize Make and save

    Depending on what the window asks, either approve Make on the SwarmNode page or paste the key SwarmNode gives you. Click Save. Make can now list the SwarmNode objects it is allowed to read.

First scenario

Build your first scenario with SwarmNode

GoalWhen a new lead lands in another app, Make runs your SwarmNode agent on it and reads back the execution.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since SwarmNode has no trigger, the first module comes from the app where your leads arrive, or you start on a schedule.

  2. 02

    Add Execute an Agent

    Click the + to the right of that first module, search SwarmNode and pick Execute an Agent. Choose your connection, or click Create a connection if this is your first SwarmNode module.

  3. 03

    Fill the fields

    Once the connection exists, Make lists what it can read on SwarmNode, so check whether your agent appears there before typing anything. Map the lead data from the first module into the fields the module shows.

  4. 04

    Read the run with Get an Execution

    Add Get an Execution after it and map the data returned by Execute an Agent. The scenario now reads the run it just started and can pass the result along.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, so you see exactly what SwarmNode sent back before anything goes live.

  6. 06

    Schedule and switch it on

    On the first module, set the schedule (every 15 minutes by default, 15 minutes minimum on the Free plan) and switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What each SwarmNode module does

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

SwarmNode1

Execute an Agent

ActionIn the docs only

Starts one of your SwarmNode agents from inside a scenario, so the work you designed in SwarmNode runs when another app hands over new data.

When to use it
a form, a lead or a support request arrives elsewhere and you want the agent to process it without anyone opening SwarmNode.
Watch out
Make documents no fields for this module, so run it once and check what it returns before chaining more steps.
SwarmNode2

Get an Execution

ActionIn the docs only

Gives you back the details of a SwarmNode execution, which is how the rest of the scenario gets to see what an agent run produced.

When to use it
place it after Execute an Agent when you need the output in a sheet, a message or a CRM record.
Watch out
the documentation says nothing about how long a run takes, so test with Run once and confirm the execution holds the data you expect.
SwarmNode3

Make an API Call

ActionIn the docs only

Opens the whole SwarmNode API to your scenario through the connection you already set up, with no second login to manage.

When to use it
you need an endpoint that neither Execute an Agent nor Get an Execution covers.
Watch out
Make lists no endpoints for SwarmNode, so you need the SwarmNode API reference open to know the path and the body to send.
Need help

Need help automating SwarmNode with Make?

A person reads every message.

FAQ

SwarmNode and Make: common questions

01Is the SwarmNode Make integration free?
Yes, on the Make side. SwarmNode is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and lift the active scenario cap. Make counts usage in credits, one operation each time a module runs on a bundle. Your SwarmNode subscription is a separate matter this page does not cover.
02What do you need to connect SwarmNode to Make?
A SwarmNode account and a Make account. Make's documentation lists no prerequisite for this app and gives no official connection steps, so you follow the generic flow: add a SwarmNode module, click Create a connection, optionally name it, then either authorize Make on the SwarmNode page or paste the key SwarmNode provides, and click Save. The connection is then reused by all 3 SwarmNode modules in every scenario, so you only go through these steps once.
03Does SwarmNode trigger Make scenarios in real time?
No. SwarmNode has no trigger module in Make, neither scheduled nor instant, so SwarmNode itself never starts a scenario. You have two ways to begin anyway. Put a trigger from another app first, for example a new form entry or a new CRM lead, and add Execute an Agent after it. Or start on a schedule: the clock on the first module runs every 15 minutes by default, down to 1 minute on paid plans. Instant starts only happen if that other app offers an instant trigger.
04What if the SwarmNode module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SwarmNode API with the same connection, so you are not limited to Execute an Agent and Get an Execution. The catch is documentation: Make says it lacks public information on SwarmNode, so it publishes no field list or endpoint guide for this app. Keep the SwarmNode API reference at hand, build the request, then click Run once to check the response before you activate the scenario.
05Should you use Make or n8n for SwarmNode?
It depends on your criteria, not on a ranking. On Make, SwarmNode offers 3 action modules, one of them Make an API Call for anything else, and it runs from the Free plan. What this page cannot confirm is whether n8n has a dedicated SwarmNode node, so check that first. Then weigh how you like to build, how your team already works and what your volume looks like. The n8n vs Make comparison page lays out both tools side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations