Resources · Make integration

TRIGGERcmd Make integrationAutomate TRIGGERcmd with Make.

What if a new form entry or a sales update could start a command on your own computer? The TRIGGERcmd Make integration gives you 2 action modules for that. This guide shows how to link your account, build a first scenario and pick the right module.

Try the TRIGGERcmd integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TRIGGERcmd Make integration do for you?

The integration lets Make, a no-code automation tool, ask TRIGGERcmd to run a command on your computer. Something happens in another app, Make notices it, and the Trigger Command module starts the command you picked. You build it once as a scenario, which is the automation Make runs for you, and it keeps working without you at the keyboard.

Kick off a local backup when a client file changes. A module from a storage app spots the update, then Trigger Command launches the backup script sitting on your office machine. No one has to remember to click it.

Start a report build after a form comes in. A submission from a form tool is the signal; TRIGGERcmd runs the script that prepares the file on your desktop. The 123FormBuilder Make integration is one way to catch that submission.

Reach the rest of the TRIGGERcmd API. When you need more than running a command, Make an API Call talks to any endpoint of the app with the same account link.

Know the limits before you start. TRIGGERcmd has no trigger module in Make, so another app or the Make clock has to start the scenario. Make's own documentation for this app is also marked as limited, which means few details are published about each module. If something misbehaves, the Make troubleshooting guide covers the usual checks.

Weighing tools? Many apps also have an n8n node, and the n8n vs Make comparison helps you choose.

Connect

How do you connect TRIGGERcmd to Make?

  1. 01

    Add a TRIGGERcmd module

    Inside your scenario, add the Trigger Command module and click Create a connection. A connection is your TRIGGERcmd account linked to Make once, then reused by both modules.

  2. 02

    Name the connection

    This step is optional, but a clear name like "Office PC" helps later when several people or accounts share the same Make team and you need to spot the right link.

  3. 03

    Authorize and save

    Make either opens a TRIGGERcmd page asking you to allow access, or asks for a key that TRIGGERcmd provides. Complete whichever appears, then click Save to finish.

First scenario

Your first scenario with TRIGGERcmd

GoalWhen something happens in another app, Make tells TRIGGERcmd to run a command on your computer.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. That first module is the signal, so pick one from the app where your event happens.

  2. 02

    Set up the starting app

    Search that app by name, choose its module, click Create a connection and fill in its fields. Make lists what it can read once the account is linked.

  3. 03

    Add Trigger Command

    Click the + on the right of the first module, search TRIGGERcmd, pick Trigger Command and link your account. Choose the command to run, mapping data from the previous module if needed.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles, meaning the items each module received. Check that your command actually ran on the computer.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From then on, Make runs the chain for you.

Modules

What each TRIGGERcmd module does

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

TRIGGERcmd1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module sends your own authorized request to the TRIGGERcmd API, reusing the connection you already created, so you can reach an endpoint that the listed module does not cover.

When to use it
you need a TRIGGERcmd feature beyond simply running a command, and the API offers it.
Watch out
Make documents this app only briefly, so test your request with Run once and read the bundle it returns before switching the scenario on.
TRIGGERcmd2

Trigger Command

Action

In Make“Runs a command on your computer”

This is the module you will use most: it asks TRIGGERcmd to run a command on your computer, so a scenario can start a script, a program or a backup the moment the earlier module passes it a bundle.

When to use it
an event in another app, such as a new order or a signed form, should launch something on a machine you own.
Watch out
each run counts as one operation on your Make plan, so filter upstream events you do not care about.
Need help

Need help automating TRIGGERcmd with Make?

A person reads every message.

FAQ

TRIGGERcmd and Make: common questions

01Is the TRIGGERcmd Make integration free?
Yes, you can use it on the Make Free plan, because TRIGGERcmd is a standard app and not an Enterprise one. The Free plan still has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans remove the cap on active scenarios and lower the interval to 1 minute. Usage is counted in operations, one for each module run on one item.
02What do you need to connect TRIGGERcmd to Make?
You need a TRIGGERcmd account and a Make account. Make's documentation lists no special prerequisite for this app and no dedicated setup steps, so the generic flow applies: add a TRIGGERcmd module, click Create a connection, optionally name it, authorize Make on the TRIGGERcmd page or paste the key the app gives you, then click Save. The same connection then serves both modules, so you only go through this once per TRIGGERcmd account.
03Can TRIGGERcmd start a Make scenario in real time?
No, because TRIGGERcmd has no trigger module in Make, only 2 actions. The scenario therefore has to start somewhere else. The usual approach is to place a trigger from another app first, such as a form or a storage tool, then add Trigger Command after it. You can also start the scenario on a schedule set on its first module, every 15 minutes by default on a new scenario, and at least 15 minutes apart on the Free plan.
04What if a TRIGGERcmd module is missing in Make?
Use Make an API Call. This module can reach any endpoint of the TRIGGERcmd API with the connection you already set up, so you are not limited to Trigger Command. Keep in mind that Make marks its TRIGGERcmd documentation as limited, since little public information exists about the app. Before switching the scenario on, test your call with Run once and check the bundle it returns. Each call counts as one operation on your Make plan, like any other module.
05Should you use Make or n8n for TRIGGERcmd?
It depends on the tool your team already uses. On Make, TRIGGERcmd offers 2 modules, Trigger Command and Make an API Call, and it is available from the Free plan. Many apps also have an n8n node, so check whether one exists for TRIGGERcmd before deciding. The choice then comes down to which editor you prefer and where your other automations already live, and the n8n vs Make comparison page lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations