Resources · Make integration

SSH Make integrationAutomate SSH with Make.

Yes, Make can log into your server and run a command there. The SSH Make integration counts one module, one brick of a scenario, and a scenario is the chain of steps Make runs for you. Below: the connection fields, a first build, and the questions that follow.

Try the SSH integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SSH Make integration actually cover?

The SSH Make integration is one action module and nothing else. You point Make at a machine you own, you write the command, and Make runs it inside a scenario. What the module returns travels on as a bundle, a single item handed to the next module in the chain.

Three shapes come back over and over. A monitoring app sees a service go down and Make runs the restart command on the right machine. A card lands in Done in your project tool and the deploy script fires on the staging server. Someone in support needs a log, and the command reads it, then the answer goes straight to the channel where the team already talks.

Two things this app will not do. It has no trigger module, so nothing happening on the server can wake Make up: the scenario always starts elsewhere, on a schedule or on another app's trigger. And there is no Make an API Call module for SSH, the generic fallback some apps carry, so this single action is the whole surface.

SSH lives on the other platform too. The SSH n8n integration covers it if your flows run there, and n8n vs Make lays out the criteria if the choice is still open. If you would rather get comfortable with the editor before pointing it at a production server, the Make training walks through the same gestures.

Connect

How do you connect a server to Make?

  1. 01

    Open the connection window

    Log in to Make, drop an SSH module into a scenario, then click Create a connection. A connection is your server access stored in Make once, reused by every SSH module you add later. The window that opens holds every field below.

  2. 02

    Point Make at the machine

    Give the connection a name in Connection name if you juggle several servers, that field is optional. In Host, type the address of the machine you want to reach. The port goes in the field the docs call Post: a number from 1 to 65535, 22 by default.

  3. 03

    Pick how you sign in, then save

    The Auth type dropdown decides the rest: password or key. Fill User name either way, then the password, or upload your key in Private key, which also takes a P12, PFX or PEM certificate. Click Save and the connection is ready.

First scenario

Your first scenario, step by step

GoalWhen the scenario runs on its schedule, SSH executes your command on the server and passes what comes back down the chain.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario, then click the + to add the first module. Search SSH by name and pick Execute a command.

  2. 02

    Link your server

    The module asks for a connection the first time. Click Create a connection, fill the host, the port and the sign-in fields from the section above, then save. Every SSH module you add later reuses it.

  3. 03

    Write the command

    Fill the module fields with the command you want the machine to run. Keep this first one harmless, something that reads rather than changes, because the next step runs it for real.

  4. 04

    Chain the second module

    Click the + on the right of the module to add another Execute a command, then map a piece of data from the first module into the second so both work on the same target.

  5. 05

    Test with Run once

    Click Run once, the editor button that runs the scenario a single time. Each module shows the bundles it received, so you read what the server answered before anything is scheduled.

  6. 06

    Schedule it and switch it on

    Set the clock on the first module. A fresh scenario sits at every 15 minutes, which is also the floor on the Free plan. Then flip the scenario on and leave it alone.

Modules

The one module, and what it is good for

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

SSH1

Execute a command

Action

In Make“Executes a command on a remote device.”

Execute a command runs the command you give it on a remote machine and brings the answer back into the scenario.

When to use it
a support ticket gets closed and the cleanup script on your server has to run right after.
Watch out
the command runs for real the first time you click Run once, so start with one that only reads something.
Need help

Need help automating SSH with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the SSH Make integration free?
Yes. SSH is a standard app, so it works from the Free plan with no extra fee. What the Free plan limits is the running, not the app: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans drop the interval to 1 minute, lift the cap on active scenarios and stretch a run to 40 minutes. Make counts usage in operations, one operation being one module processing one item.
02What do you need before connecting SSH to Make?
A Make account and the access you already use to reach the machine. In practice: the host address, the port the server listens on, a user name, and either a password or a private key file, depending on the method you pick. That key field also accepts a P12, PFX or PEM certificate when you sign with your own. The documentation asks for nothing else on this app, no add-on to install, no setting to prepare beforehand. With those values in front of you, the connection takes one pass.
03Does SSH react in real time in Make?
There is no trigger to react at all: this app ships no trigger module, neither scheduled nor instant. Scheduled means Make looks at the interval you set; instant means the app calls Make through a webhook the second something happens. SSH does neither, so nothing moving on your server can wake a scenario up. The start comes from the Make side, through the schedule on the first module, or from another app's trigger placed in front of SSH.
04What if one module is not enough?
Then you work around it, because SSH has no Make an API Call module, the generic way out that some apps carry. Three routes. Put more logic in the command itself, since the module runs whatever you hand it. Bring a second app into the scenario and leave SSH the server part only. Or look at the plan: a run stops at 5 minutes on Free and at 40 minutes on a paid plan, so a long command belongs on the paid side.
05Make or n8n for SSH?
It depends on where the rest of your automations already live. SSH exists on both platforms, so neither choice leaves you unable to run a command. Make gives you this single module in a visual editor, with the connection saved once and usage counted in operations. If your team already builds on one of the two, keep this scenario next to the others rather than splitting your flows across two tools for one command. The comparison page linked above sets the criteria side by side.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations