Resources · Make integration

Robolytix Make integrationAutomate Robolytix with Make.

Can you use Robolytix in a Make scenario without a single line of code? The Robolytix Make integration gives you 1 action module, Sonar, and no trigger. This guide is for teams that already use Robolytix: it shows how to link your API key and build a first working scenario.

Try the Robolytix integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Robolytix Make integration let you do?

The Robolytix Make integration links your Robolytix account to Make, a tool where you build a scenario, meaning an automation made of modules placed one after the other. Robolytix brings a single module, an action called Sonar, which runs whenever an earlier step or the schedule of the scenario reaches it.

Because Robolytix has no trigger, something else has to start the flow. That can be another app you already connect to Make, or the clock of the scenario itself, which runs every 15 minutes by default. Sonar then comes right after, and every bundle, meaning one item passed from one module to the next, goes through it.

A few honest limits. The official documentation gives no description of Sonar, so this page does not guess its fields: once your connection exists, open the module and read what Make lists. There is no Make an API Call module for Robolytix either, so if Sonar does not cover your need, the answer sits outside this app.

Robolytix sits in the Business Intelligence category of the Make documentation. The same app may also exist as a node in n8n; if you are still choosing a tool, read n8n vs Make. To learn the editor properly before you build, the Make training starts from zero, and the Make pricing page explains how operations are counted.

Connect

How do you connect Robolytix to Make?

  1. 01

    Create an API key in Robolytix

    In Robolytix, pick the right account in the account selection dropdown, open Settings in the left menu, then API keys. Click New API key and copy the key shown in the dialog.

  2. 02

    Open the connection window in Make

    Add the Sonar module to your scenario and click Create a connection. A connection is your Robolytix account linked to Make once, then reused by every Robolytix module. You may fill Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. From that point, Make can list what it is able to read from your Robolytix account inside the module.

First scenario

Your first scenario with Robolytix

GoalWhen the first module of your scenario hands over a bundle, Make runs Sonar on it for your Robolytix account.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module decides when everything starts, so pick the app or the Make tool that holds your data.

  2. 02

    Add the Sonar module

    Click the + on the right of that first module, search for Robolytix and choose Sonar. Click Create a connection and paste your API key if this is your first Robolytix module.

  3. 03

    Map the data

    Fill the fields Make shows in Sonar and map values from the previous module by clicking them. Once the connection is saved, Make lists what it can read from Robolytix.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, and check in Robolytix that the result looks the way you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on, each run costs operations, one per module and per bundle, counted on your plan.

Modules

What the Robolytix module does

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

Robolytix1

Sonar

ActionIn the docs only

Sonar is the only Robolytix module in Make, an action that works on one bundle at a time and and the name suggests it passes your scenario's data to Robolytix, a guess, since the documentation gives it no description. Trust the fields Make displays once your connection is ready.

When to use it
after any module that produces the item you want Robolytix to receive, placed right behind it in the flow.
Watch out
each bundle that reaches Sonar is one operation, so filter upstream if only some items matter.
Need help

Need help automating Robolytix with Make?

A person reads every message.

FAQ

Robolytix and Make: common questions

01Is the Robolytix Make integration free?
Yes, on the Make side. Robolytix is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes 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 and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Robolytix account, whose subscription is described on the Robolytix pricing page.
02What do you need to connect Robolytix to Make?
An active Robolytix account and an API key. In Robolytix, select the account in the dropdown, open Settings, then API keys, click New API key and copy it. In Make, add the Sonar module, click Create a connection, give it a name if you want, and paste the key. The connection is then reused by every Robolytix module in your scenarios, so this setup happens only once per account. If you later switch accounts, create a new key for that account.
03Can Robolytix start a Make scenario by itself?
No. Robolytix has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario on its own. Open the flow with another element instead: a trigger from another app you use, or simply the schedule of the scenario, which runs every 15 minutes by default and can go down to 1 minute on a paid plan. Sonar then sits after that first module and receives each bundle it produces.
04What if the Sonar module does not do what you need?
Then the answer is outside this app. Robolytix has no Make an API Call module in Make, so you cannot send a custom request to its API from a generic module. The practical options are to handle the missing part with another app in the same scenario, or to ask the team for help with the design. Before that, open Sonar after connecting and read every field Make shows, since the documentation does not list them.
05Should you use Make or n8n with Robolytix?
It depends on the tool your team already uses. In Make, Robolytix offers one action, Sonar, and no trigger, available from the Free plan. The same app often has a node in n8n too, so the choice comes down to where your other automations live and which editor your team prefers to maintain. Neither tool is ranked here: compare the Robolytix operations each one offers against your actual process before you decide.
Same platform

Other docs you might need on this stack.

Browse all integrations