Resources · Make integration

ProBackup Make integrationAutomate ProBackup with Make.

Want to hear about deletions in ProBackup without checking it by hand? The ProBackup Make integration gives you exactly 1 module, a trigger that watches deleted records. This page shows IT teams how to connect the account, build a first scenario and test it safely.

Try the ProBackup integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ProBackup Make integration do for you?

The ProBackup Make integration links your ProBackup account to Make so a deletion can start an automation. In Make, that automation is called a scenario: a chain of bricks named modules, each one handling a single step. ProBackup brings one of those bricks, a trigger called Watch Deleted Record, and every step after it comes from other apps.

Keep a trace of removals. Watch Deleted Record hands each deleted record to the next module as a bundle, which is simply one item moving through the scenario. Send that bundle to a spreadsheet app and you get a running list of what was removed, without anyone copying it by hand.

Warn the right person. An IT lead rarely wants to open ProBackup just to learn that something vanished. Put a messaging module after the trigger and the team hears about it where it already talks.

Open a follow-up task. A deletion can be normal or a mistake. Sending it to a ticketing or task app gives someone the job of checking which one it was.

Be clear on the limits. Make's documentation for ProBackup is marked as limited, because little public information about the app exists, and it lists no action or search module. The page therefore says nothing about the fields the trigger returns: check them yourself with a test run. If the setup puzzles you, the Make troubleshooting guide and the Make training cover the editor from the ground up.

Also weighing n8n? The same app often has an n8n node, and the n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect ProBackup to Make?

  1. 01

    Add the module and start the connection

    In a scenario, add the Watch Deleted Record module and click Create a connection. A connection is your ProBackup account linked to Make once, then reused by any ProBackup module you add later.

  2. 02

    Give the connection a name

    This step is optional, yet a clear name such as the account or the client it belongs to saves confusion later, especially when several people share the same Make organization and pick connections from a list.

  3. 03

    Authorize Make and save

    Depending on what ProBackup offers, either approve Make on the ProBackup page that opens or paste the key ProBackup gives you. Then click Save and the connection appears in the module.

First scenario

Your first scenario with ProBackup

GoalWhen a record is deleted in ProBackup, Make passes it to a module of another app so the team learns about it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the canvas. That + is where the very first module, the trigger, goes.

  2. 02

    Pick the ProBackup trigger

    Search for ProBackup, choose Watch Deleted Record, then click Create a connection to link your account. Fill in whatever the module asks; Make lists what it can read once connected.

  3. 03

    Add the next module

    Click the + on the right of the trigger and pick the app that should receive the news, a chat tool or a spreadsheet for example. Map the data coming from Watch Deleted Record into its fields.

  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, which is the only reliable way to see what the trigger returns.

  5. 05

    Schedule it and switch it on

    On the trigger, open the clock to set the schedule; a new scenario runs every 15 minutes by default. Then turn the scenario on so it keeps checking without you.

Triggers

What starts a ProBackup scenario?

1 module starts a scenario when something happens in ProBackup. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ProBackup as soon as it happens.

ProBackup1Watch Deleted Record

Watch Deleted Record

triggerIn the docs only

This trigger gives you a scenario that reacts to removals: each record deleted in ProBackup reaches Make as a bundle that the following modules can log, forward or turn into a task. Every ProBackup scenario starts here.

How it fires
scheduled, a type deduced from the module name since the documentation does not state it. Make checks the app on the scenario's schedule, every 15 minutes by default, and never faster than 15 minutes on the Free plan.
When to use it
pick it when a deletion should leave a trace somewhere your team actually looks, such as a shared sheet or a support queue.
Watch out
the documentation describes neither the module nor its output, so run it once and read the bundle before you map anything.
Need help

Need help automating ProBackup with Make?

A person reads every message.

FAQ

ProBackup and Make: common questions

01Is the ProBackup Make integration free?
Yes, on Make's side. ProBackup 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 at most, 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 count usage in operations, one operation being one module run on one bundle. Your ProBackup subscription is a separate matter this page does not cover.
02What do you need to connect ProBackup to Make?
A ProBackup account and a Make account. Make's documentation lists no specific prerequisite for ProBackup and gives no dedicated connection steps, so the generic flow applies: add the Watch Deleted Record module, click Create a connection, optionally name it, authorize Make on the ProBackup page or paste the key ProBackup provides, then click Save. The connection is stored once and reused by every ProBackup module in your scenarios. If something fails at the authorization stage, look at the permissions of the ProBackup account first.
03Does the ProBackup Make integration react in real time?
No. Watch Deleted Record is a scheduled trigger (deduced from its name, the documentation does not say): Make asks ProBackup for new deletions at the interval set on the scenario, which is 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval allowed; paid plans can go down to 1 minute. So a deletion shows up in your scenario at the next check, not the instant it happens. The clock badge on the module in the editor is the visual reminder that it polls rather than listens.
04What if the ProBackup module you need is missing in Make?
It depends on what you need. Make lists a single ProBackup module, Watch Deleted Record, with no action, no search and no Make an API Call module to fill the gap. Make also marks its ProBackup documentation as limited because little public information about the app exists. For anything beyond watching deletions, look for another app that covers the job, or ask the team for help on a custom setup. Before building on the trigger's output, test it with Run once to see which data it really returns.
05Should you use Make or n8n for ProBackup?
It depends on your criteria. On Make, ProBackup offers one scheduled trigger for deleted records, available from the Free plan, and you build the rest of the scenario with other apps in a visual editor. The same app often has an n8n node too, so the useful move is to check which operations each tool exposes for ProBackup and which one your team already uses for its other automations. Pick the one where the modules you need exist, rather than the one with the louder reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations