Resources · Make integration

Squad Make integrationAutomate Squad with Make.

Can Make handle your Squad payments while you work on something else? The Squad Make integration gives you 12 modules: 1 trigger that watches transactions and 11 actions for links, refunds, disputes and balances. This page shows you how to link your account and build a first scenario.

Try the Squad integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Squad Make integration do for you?

The Squad Make integration links your Squad account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. Squad brings 12 of those bricks, so payment work you do by hand in the dashboard can run from a scenario instead.

Checked sales, not guesses. Watch Transactions picks up new transactions, and Verify a Transaction confirms each one with Squad before your order tool or spreadsheet treats it as paid. The data travels between modules as bundles, one bundle per transaction.

Refunds and disputes handled from one place. Initiate a Refund for a Customer sends money back when a support ticket is approved, while Get a Dispute and Resolve a Dispute let a finance lead pull a contested payment into a scenario and close it without switching screens.

Payment requests created on demand. Create a Payment Link builds a link you can drop into an invoice email, and Create a Virtual Account gives a customer a dedicated account to pay into. Get a Balance tells a scenario how much sits in your account before it starts a payout with Initiate a Payment.

Where the list stops, Make an API Call reaches any other endpoint of the Squad API with the same connection. The Squad documentation page in Make lists no official description for these modules, so check each one in the editor before relying on it. If you are weighing tools, read n8n vs Make, and for guided practice see Make training. When a run fails, Make troubleshooting helps you read the error.

Connect

How do you connect Squad to Make?

  1. 01

    Get your Squad API key

    Your Squad account has to be active with KYC completed. Log in, open the dashboard, go to Settings in the main menu, then to the API tab or API Access section, and copy the API key shown on screen.

  2. 02

    Add a Squad module in Make

    In your Make account, add any Squad module to a scenario and click Create a connection. A connection is your Squad account linked to Make once, then reused by every Squad module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Squad into the credentials field, or follow the instructions Make shows on screen, then save. From now on, the Squad modules can read and act on your account without asking for the key again.

First scenario

Your first scenario with Squad

GoalWhen a new transaction shows up in Squad, Make verifies it with Squad so you only act on confirmed payments.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to add the first module. That first module is what starts every run.

  2. 02

    Pick Watch Transactions

    Search for Squad, choose Watch Transactions and click Create a connection with the API key from your Squad settings. Once connected, fill in the fields Make displays for the module.

  3. 03

    Add Verify a Transaction

    Click the + on the right of the trigger, pick Squad again and choose Verify a Transaction. Map the transaction data coming from the first module so Squad knows which payment to confirm.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can see what Squad sent back before anything runs on its own.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, and switch the scenario on. From there, you can add the app that should receive confirmed payments.

Triggers

What starts a Squad scenario

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

Squad1Watch Transactions

Watch Transactions

triggerIn the docs only

Watch Transactions gives your scenario a starting point every time Squad has transactions it has not handed over yet, so nothing has to be exported by hand. Each transaction arrives as its own bundle for the next modules.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default and never faster than that on the Free plan.
When to use it
as the first module of any flow that reacts to money coming in, such as confirming an order or logging a sale in your books.
Watch out
the Make documentation gives no description for this trigger, so run it once and read the bundles before you build on them.
Modules

What Squad can do in Make

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

Squad2

Create a Terminal

ActionIn the docs only

This action sets up a new terminal record in Squad from inside a scenario, which saves you from repeating the same setup in the dashboard each time a point of sale is added.

When to use it
when a new shop or agent is approved in your internal form and needs its own terminal.
Watch out
no official description exists for this module, so check the required fields in Make first.
Squad3

Create a Virtual Account

ActionIn the docs only

Create a Virtual Account gives a customer or a project its own account to pay into, generated as soon as the scenario needs it. Payments then land somewhere easy to match.

When to use it
during onboarding of a new client, so the account details can go straight into the welcome email.
Watch out
run it once per customer, not on every order, or you pile up accounts.
Squad4

Get a Balance

ActionIn the docs only

Get a Balance hands the scenario the balance of your Squad account, so a later module can decide what to do with a real figure rather than a guess.

When to use it
just before Initiate a Payment, with a filter that stops the payout when the balance is too low.
Watch out
the value reflects the moment the module runs, not a live feed, so fetch it again in each run.
Squad5

Get a Dispute

ActionIn the docs only

With Get a Dispute, the details of one contested payment come into your scenario, ready to be posted to a ticket, a chat channel or a sheet your finance team follows.

When to use it
when a customer complaint mentions a charge and you want the dispute data next to the ticket.
Watch out
it reads one dispute at a time, so the scenario needs the dispute identifier from an earlier step.
Squad6

Get an Upload URL

ActionIn the docs only

Get an Upload URL returns an address where a file can be sent to Squad, which is the step that comes before sharing a document with them from a scenario.

When to use it
when you answer a dispute and need to send proof, such as a delivery receipt stored in your drive.
Watch out
the module only provides the address; sending the file is a separate step the documentation does not describe, so test it with Run once.
Squad7

Initiate a Payment

ActionIn the docs only

Initiate a Payment starts a payment from Squad on the scenario's instruction, so payouts approved elsewhere no longer need someone to key them in.

When to use it
once a supplier invoice is marked approved in your accounting app and the amount has been checked.
Watch out
money moves for real; test with Run once on a small case and keep a filter before this module.
Squad8

Initiate a Refund for a Customer

ActionIn the docs only

This module sends a refund back to a customer through Squad, triggered by your own approval process instead of a manual action in the dashboard.

When to use it
when a support agent closes a return request as accepted in your help desk.
Watch out
no module in the list cancels a refund, so make sure the approval step runs before it and only once per request.
Squad9

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Squad API with the connection you already have, which covers what the 11 listed actions leave out.

When to use it
when you need a Squad feature that no other module offers, one that none of the 11 listed actions covers.
Watch out
you write the request yourself, so keep the Squad API reference open while you set it up.
Squad10

Resolve a Dispute

ActionIn the docs only

Resolve a Dispute closes a contested payment in Squad from the scenario, so the decision taken in your ticket tool is applied without a second trip to the dashboard.

When to use it
after your team has reviewed the case and recorded its decision in the help desk.
Watch out
pair it with Get a Dispute first, so the scenario acts on the right case with current details.
Squad11

Verify a Transaction

ActionIn the docs only

Verify a Transaction asks Squad to confirm a given transaction, so the rest of the scenario works with a checked result instead of whatever a customer or a form claimed.

When to use it
before you ship an order or unlock access, right after Watch Transactions or a checkout form.
Watch out
it needs the transaction reference from an earlier module; map it rather than typing it.
Need help

Need help automating Squad with Make?

A person reads every message.

FAQ

Squad and Make: common questions

01Is the Squad Make integration free?
Yes, on the Make side. Squad is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum 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) drop the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one operation being one module run on one bundle. Your Squad subscription is a separate matter, handled on the Squad side.
02What do you need to connect Squad to Make?
An active Squad account with KYC completed, and a valid API key. You find the key in the Squad dashboard under Settings, then the API tab or API Access section. In Make, add a Squad module, click Create a connection, give it a name if you like, and paste the key. The connection is then shared by every Squad module in your scenarios, so you only do this once per account.
03Does the Squad trigger in Make fire instantly?
No. Watch Transactions is a scheduled trigger: Make checks Squad on the scenario's schedule instead of being called by Squad the moment a transaction happens. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. If you need a faster reaction, lower the schedule on a paid plan; the documentation lists no instant trigger for Squad.
04What if a Squad module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Squad API with the connection you already set up, so a feature missing from the 11 actions is still within reach. You write the request yourself, which takes a bit more care than a ready module. Note also that the Make documentation carries a warning that its Squad page is AI-generated from the Squad docs, so confirm important details with Squad before you rely on them.
05Should you use Make or n8n for Squad?
It depends on the tool your team already uses. In Make, Squad comes with 1 trigger, 11 actions and Make an API Call for anything else, all through one connection. The same app often has an n8n node too, so check that the operations you need exist there before choosing. Pick the tool where your other scenarios already live, since keeping payment flows next to the rest of your automations makes them easier to follow and fix.
Same platform

Other docs you might need on this stack.

Browse all integrations