Resources · Make integration

SqlBak Make integrationAutomate SqlBak with Make.

Can Make pull your SqlBak jobs and servers into your other tools? The SqlBak Make integration offers 5 modules: 3 actions and 2 searches, with no trigger. This guide is for ops and IT people new to Make, and it walks you from the connection to a first working scenario.

Try the SqlBak integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SqlBak Make integration do?

The SqlBak Make integration lets a Make scenario, meaning the automation you build as a chain of bricks, read what your SqlBak account holds: its basic account details, the list of jobs, the settings of a job and the list of servers. Each brick is a module, and your SqlBak account is linked once through a connection that every module reuses.

A job inventory you never type by hand. Put List All Jobs first, then Get Job Settings on each result, and send the settings wherever your team keeps its records. Every job comes out as a bundle, one item that flows from one module to the next.

A server list that stays current. List All Server returns the servers attached to your account, one bundle each, ready to feed a sheet or a message to whoever looks after the machines. Pair it with Get Basic AccountInformation when the report should also show which account it came from.

Anything the list leaves out. Make an API Call reaches any endpoint of the SqlBak API with the same connection, which is how you cover a need the four named modules do not.

Know the limits before you start. Make itself says its documentation for SqlBak is limited, because too little public information exists about the app, and there is no trigger: something else has to start the scenario. If SqlBak also has an n8n node for you, the n8n vs Make comparison helps you pick the tool. New to the editor? The Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect SqlBak to Make?

  1. 01

    Add a SqlBak module

    In a new scenario, click the +, search for SqlBak and pick any of its modules. Then click Create a connection: this is the link between your SqlBak account and Make, created once and reused by every SqlBak module afterward.

  2. 02

    Name the connection

    Giving the connection a name is optional, yet it pays off as soon as you handle more than one SqlBak account. A clear label, such as the client or the environment it belongs to, saves you from picking the wrong account in a later scenario.

  3. 03

    Authorize and save

    Depending on what SqlBak asks for, either approve access on the SqlBak page that opens, or paste the key SqlBak gives you. Then click Save. The module now shows your connection and you can fill its fields.

First scenario

Your first scenario with SqlBak and Make

GoalWhen the scenario's schedule comes around, Make lists your SqlBak jobs and reads the settings of each one.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. Since SqlBak has no trigger, your first module will be a SqlBak search that the schedule starts.

  2. 02

    Add List All Jobs

    Search for SqlBak, choose List All Jobs and select your connection, or click Create a connection if you have none yet. This search returns one bundle per job in your account.

  3. 03

    Chain Get Job Settings

    Click the + on the right of the first module and add Get Job Settings. Map the job coming out of List All Jobs into it, so each job found gets its settings read.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above each module to read the bundles it received and check that the settings match the jobs you expected.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, and adjust it to how often you need the data. Then switch the scenario on so it keeps running without you.

Modules

What each SqlBak module does in Make

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

SqlBak1

Get Basic AccountInformation

ActionIn the docs only

This action hands your scenario the basic details of the SqlBak account behind the connection, so a report or a message can say which account the data came from.

When to use it
you manage several SqlBak accounts and each summary you send should name its source account, rather than leaving the reader to guess.
Watch out
Make does not document which details come back, so run the module once and read its bundle before you map anything.
SqlBak2

Get Job Settings

ActionIn the docs only

Here you get the configuration of one SqlBak job, returned as a single bundle that later modules can read, copy into a sheet or compare with what you expect.

When to use it
right after List All Jobs, to look inside each job it found instead of stopping at the name.
Watch out
it works on one job at a time, so every job you feed it costs one operation, the unit Make counts on your plan.
SqlBak3

List All Jobs

SearchIn the docs only

Your whole list of SqlBak jobs lands in the scenario, one bundle per job, which gives every later module something to work through.

When to use it
as the opening module of a scheduled scenario that builds an inventory of your jobs or passes each one to Get Job Settings.
Watch out
as a search, it can return zero, one or many bundles; with zero, the modules after it simply do not run, so test on an account that has jobs.
SqlBak4

List All Server

SearchIn the docs only

With this search you see the servers attached to your SqlBak account, each one arriving as its own bundle that you can send on to a sheet, a ticket or a message.

When to use it
when the people who look after the machines need an up-to-date server list without logging into SqlBak.
Watch out
the module name reads Server, singular, yet it is a search, so plan for several bundles and add a filter if you only care about some of them.
SqlBak5

Make an API Call

ActionIn the docs only

This module opens the rest of the SqlBak API to your scenario: it calls any endpoint you name, using the connection you already created, with no second login.

When to use it
the four named modules do not cover what you need, and the SqlBak API does.
Watch out
you write the request yourself, and Make's SqlBak documentation is limited, so build one request at a time and read what comes back with Run once.
Need help

Need help automating SqlBak with Make?

A person reads every message.

FAQ

SqlBak and Make: common questions

01Is the SqlBak Make integration free?
Yes, SqlBak is a standard app in Make, so its modules are available on the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, remove the cap on active scenarios and allow up to 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Any SqlBak subscription is separate from Make.
02What do you need to connect SqlBak to Make?
You need a SqlBak account and a Make account. Make's documentation for SqlBak lists no specific prerequisite, so the generic steps apply: add a SqlBak module, click Create a connection, optionally give it a name, then either authorize Make on the SqlBak page or paste the key SqlBak provides, and click Save. The connection is stored once and every SqlBak module in your scenarios reuses it. If the window asks for something unexpected, start by checking your SqlBak account settings.
03Does the SqlBak Make integration react in real time?
No, SqlBak has no trigger in Make, so nothing starts a scenario by itself when something changes in SqlBak. You have two ways to begin. The first is a schedule: open the clock on the first module and let Make run the scenario at the interval you choose, every 15 minutes by default, never below 15 minutes on the Free plan. The second is to start from another app's trigger and add SqlBak modules after it, so the SqlBak data is read whenever that other app fires the scenario.
04What if a SqlBak module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SqlBak API with the connection you already set up, which covers what Get Basic AccountInformation, Get Job Settings, List All Jobs and List All Server leave out. Keep in mind that Make describes its SqlBak documentation as limited, since little public information exists about the app, so build the request step by step and test each call with Run once before switching the scenario on.
05Should you use Make or n8n for SqlBak?
It depends on the tool your team already works in. On the Make side, SqlBak offers 5 modules, all actions or searches, plus Make an API Call for the rest, and no trigger, so a schedule or another app has to start each scenario. SqlBak may also have an n8n node, which is worth checking against your needs. Choose on concrete criteria: whether the modules you need exist, how your scenarios will start, and which editor your team is comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations