Square Make integrationAutomate Square with Make.
Can a Square sale update the rest of your stack on its own? The Square Make integration gives you 26 modules: 5 triggers, 14 actions and 7 searches around payments, orders and customers. This page connects your account, builds a first scenario with you and explains each module.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Square Make integration let you automate?
The Square Make integration links your Square account to Make, so a payment, an order or a new customer can start an automation without code. In Make, that automation is a scenario: a chain of modules, each one a brick that watches, searches or acts in an app.
A tidy customer base. Watch Customers spots each new profile, then Add a Customer to the Group files it in the right segment, for a shop that separates walk-in buyers from wholesale accounts.
Payments followed up without chasing. Watch Payments picks up new and updated payments; paired with Get a Customer, it gives a bookkeeper the buyer behind each ticket. When you create payments with autocomplete off, Complete a Payment captures them once the goods ship.
Order reports on demand. Search Orders and Get Orders pull a batch of orders into a sheet or a dashboard, which suits a café owner who wants sales in one place. If your tables live elsewhere, the Airtable Make integration works the same way.
What Make does not cover here: several Square modules are marked deprecated by the doc, and the listed modules do not create a refund outside the deprecated one. Make an API Call fills those gaps with the same connection. Many apps also have an n8n node; the n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted.
How do you connect Square to Make?
- 01
Prepare your Square developer side
Make needs a Square developer account and an access token. In the Square Developer Dashboard, open Applications, pick your application and go to its OAuth section, where the Client ID and Client secret sit.
- 02
Add a Square module and create the connection
In your scenario, add any Square module and click Create a connection. A connection is your Square account linked to Make once, then reused by every Square module. The Connection name field is optional but helps when you run several shops.
- 03
Enter your credentials and approve
Paste the credentials copied from Square, or follow the on-screen instructions. For an instant module such as Watch New Events, click Create a webhook first, then Create a connection.
Your first scenario: sort new Square customers into a group
GoalWhen a new customer appears in Square, Make adds that customer to the group you choose.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the + to add the first module. Search for Square and choose Watch Customers.
- 02
Link your Square account
Click Create a connection and finish the steps above. Once the connection exists, Make can read your Square data and list what it finds in the module fields.
- 03
Add the group action
Click the + on the right of Watch Customers, pick Add a Customer to the Group, map the customer from the first module and choose the target group.
- 04
Test with Run once
Create a test customer in Square, then click Run once. Each bundle, one customer here, shows what every module received, so you can check the group was filled.
- 05
Schedule and switch it on
Open the clock on Watch Customers: a new scenario runs every 15 minutes by default, and paid plans go down to 1 minute. Set the schedule, then switch the scenario on.
Square triggers in Make
5 modules start a scenario when something happens in Square. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Square as soon as it happens.
Watch Customers
Scheduled triggerIn Make“Returns new customers since the last check.”
Watch Customers brings every customer profile added in Square since the previous check into your scenario, one bundle per customer, so a new buyer reaches your CRM or mailing tool with nobody retyping details.
Watch New Events
Instant triggerIn Make“Watches for new events(inventory, invoices, transactions, disputes, orders, labors) in square account.”
Watch New Events lets Square tell your scenario the moment something changes: inventory, invoices, transactions, disputes, orders or labor records. It is the only trigger of this app that does not wait for a schedule.
Watch Orders
Scheduled triggerIn Make“Returns create OR updated orders since the last check.”
Watch Orders returns the orders created or updated in Square since the last check, which gives your kitchen screen, your stock sheet or your shipping tool a steady feed of what customers bought.
Watch Payments
Scheduled triggerIn Make“Returns new and updated payments since the last check.”
Watch Payments picks up new payments and changes to existing ones since the previous check, so your accounting sheet or your thank-you email follows every sale taken in Square.
Watch Transactions (Deprecated)
triggerIn the docs onlyWatch Transactions (Deprecated) still appears in the Square doc for scenarios built on the older transaction model, and keeps them readable while you plan a move.
Square actions and searches in Make
Square gives you 21 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Add a Customer to the Group
ActionIn Make“Adds a customer to the customer's group.”
Add a Customer to the Group puts a Square customer into one of your customer groups, so your segments stay accurate without manual sorting in the dashboard.
Complete a Payment
ActionIn Make“By default, payments are set to complete immediately after they are created. If you set autocomplete to false when creating a payment, you can complete (capture) the payment using this endpoint.”
Complete a Payment captures money you only authorized earlier. Square completes payments right after creation by default; this module matters when autocomplete was set to false.
Create a Customer
ActionIn Make“Creates a new customer.”
Create a Customer adds a new profile to your Square directory from data collected elsewhere, a form, a booking or a spreadsheet row, so the counter staff recognize the person on the first visit.
Create an Order
ActionIn Make“Creates an Order”
Create an Order opens an order in Square from an outside source, which lets a web form, a chat or a phone booking tool feed the same order flow as your point of sale.
Get a Customer
ActionIn Make“Gets customer details.”
Get a Customer fetches the full profile of one Square customer from its ID, which turns a bare ID coming from a payment or an order into a full customer profile you can work with.
Get a Payment
ActionIn Make“Returns payment by ID.”
Get a Payment returns one payment from its ID, with the details Square holds on it, so a later module works from the real payment rather than a guess.
Get a Payment (legacy)
ActionIn Make“Retrieves information about a transaction by a payment ID.”
Get a Payment (legacy) reads the transaction behind a payment ID, the older way Square exposed that data, and keeps scenarios built on it working.
Get a Transaction (Deprecated)
ActionIn Make“Gets transaction information.”
Get a Transaction (Deprecated) returns the information of one transaction from the older Square model, which only helps scenarios still built around transactions.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Make an API Call reaches any endpoint of the Square API from your scenario, reusing the same connection, so a need no listed module covers does not force you out of Make.
Update a Customer
ActionIn Make“Updates customers details.”
Update a Customer changes the details of an existing Square profile, so new contact details captured in another tool reach your point of sale as well.
Get Orders
SearchIn Make“Lists orders in batch.”
Get Orders lists Square orders in a batch, one bundle each, which is handy when you need several known orders at once rather than one at a time.
List Customers
SearchIn Make“Lists all customers”
List Customers returns your Square customers as a series of bundles, a quick way to copy the directory into a sheet or check whether someone already exists.
List Payments
SearchIn Make“Lists payments.”
List Payments pulls the payments of your Square account into the scenario, so an accountant or an owner can review takings in the tool they already read.
List Refunds
SearchIn Make“Lists refunds.”
List Refunds brings the refunds recorded in Square into your scenario, which helps track returns and their cost outside the dashboard.
Search Orders
SearchIn Make“Searches for orders.”
Search Orders finds the Square orders that match the criteria you set, so you work on a precise slice instead of the whole history.
Capture Transaction (Deprecated)
ActionIn the docs onlyCapture Transaction (Deprecated) belongs to the older Square transaction model and keeps capture steps of former scenarios in place.
Create a Charge (Deprecated)
ActionIn the docs onlyCreate a Charge (Deprecated) is kept in the Square doc for older scenarios that charged customers through the former transaction model.
Create a Credit Card (Deprecated)
ActionIn the docs onlyCreate a Credit Card (Deprecated) stays in the list for scenarios that stored a card on a customer the old way, so they do not break overnight.
Create a Refund (Deprecated)
ActionIn the docs onlyCreate a Refund (Deprecated) is the only refund action in this app, kept for scenarios written before Square changed its model.
List Transactions (Deprecated)
SearchIn the docs onlyList Transactions (Deprecated) reads transactions from the older Square model, useful only for reports that were built around them.
Search Payments
SearchIn the docs onlySearch Payments, as its name says, looks for payments in Square rather than listing them all, so the scenario handles only the ones you care about.
Need help automating Square with Make?
A person reads every message.
