Resources · Make integration

Clover POS Make integrationAutomate Clover POS with Make.

Your customer list and your orders live in Clover, and your other tools never see them. The Clover POS Make integration gives you 13 modules: 10 actions and 3 searches. This guide shows store owners how to link the account and build a first working scenario.

Try the Clover POS integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clover POS Make integration do?

The Clover POS Make integration lets Make read and edit the customers, orders and line items of your Clover merchant account, without code. A scenario, the automation you build in Make as a chain of modules, can create a customer, look up an order or pull a line item, then pass that data to the next app.

A cleaner customer file. When someone joins your loyalty list on your website, Search Customers checks whether Clover already knows them, then Create a Customer or Update a Customer keeps a single record per person at the register.

Order details where your team works. Get an Order and List Line Items fetch what was sold on a ticket so a spreadsheet, an accounting tool or a support inbox gets the same lines as the till. Tools like the Airtable Make integration make a natural destination.

A full export on demand. Get List of Customers in CSV returns every customer as one CSV file, ready to hand to a mailing tool or to archive.

Two limits to know first. The app has no trigger module, so Clover never starts a scenario by itself: you start it from another app or from Make's own schedule. And you need a paid Clover account to connect at all. For anything the listed modules skip, such as the items, payments or shifts the Clover API handles, Make an API Call reaches the rest of the API.

Many apps also have an n8n node. If you hesitate between the two tools, read n8n vs Make, and check Make pricing before you plan how many scenarios you will run.

Connect

How do you connect Clover POS to Make?

  1. 01

    Collect your Merchant ID and token

    Open your Clover POS Developer dashboard and click Account & Setup, then Merchants: copy the ID shown under your merchant's name. Back in Account & Setup, open Ecommerce API tokens, click Create new token, pick API as the Integration Type and copy the Private token.

  2. 02

    Open the connection window

    In your scenario, add any Clover POS module and click Create a connection. A connection is your Clover account linked to Make once; every Clover module in your scenarios reuses it. You can type a Connection name so you recognize it later.

  3. 03

    Fill in the three fields and save

    Pick the Region where your Clover account lives, paste the ID into Merchant ID and the private token into Access Token. Click Save. If Clover asks you to sign in and confirm access, accept, and the connection is ready.

First scenario

Your first scenario with Clover POS

GoalWhen a new signup arrives in another app, Make creates that person as a customer in Clover POS.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Clover has no trigger, so the first module belongs to the app where signups arrive, like your form tool or your spreadsheet.

  2. 02

    Add the Clover module

    Click the + on the right of that first module, search for Clover POS and pick Create a Customer. Choose the connection you set up earlier, or click Create a connection now.

  3. 03

    Map the signup data

    Fill the customer fields by clicking the values from the first module: name, email, whatever your form collects. Each signup is a bundle, one item passed from one module to the next.

  4. 04

    Test with Run once

    Send a test signup, then click Run once. Make runs the scenario one time and shows the bundles each module received. Open Clover and check that the new customer is there.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What each Clover POS module does

Clover POS gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Clover POS1

Create a Customer

Action

In Make“Creates a new customer.”

Adds a new person to the customer list of your Clover merchant account, so the register recognizes them at their next visit.

When to use it
someone signs up for your newsletter or loyalty offer online and you want the cashier to find them by name.
Watch out
its description says nothing about spotting duplicates, so place Search Customers before it when the person might already be in Clover.
Clover POS2

Delete a Customer

Action

In Make“Deletes an existing customer.”

Removes one customer from your Clover account, which keeps your list tidy when a person asks to be forgotten or a test record slipped in.

When to use it
a data deletion request lands in your support inbox and you want Clover cleaned in the same flow.
Watch out
plan as if there is no undo, and point it at a customer returned by Search Customers rather than at a guess.
Clover POS3

Delete a Line Item

Action

In Make“Deletes an existing line item.”

Takes a single line off an order, for example a product added by mistake, while the rest of the ticket stays in place.

When to use it
another system cancels part of a purchase and Clover has to reflect that exact line.
Watch out
pick the exact line to remove from the bundles of List Line Items placed before it, and test on a dummy order with Run once.
Clover POS4

Delete an Order

Action

In Make“Deletes an existing order.”

Erases a whole order from your Clover account, every line included, which is heavier than removing a single line item.

When to use it
test orders or duplicates created by another tool need to disappear from your records.
Watch out
run the scenario with Run once on a known test order first, and read the bundles it received, so you know exactly which order the module removed.
Clover POS5

Get a Customer

Action

In Make“Retrieves an existing customer.”

Fetches the record of one customer you already identified in Clover and hands their details to the modules that follow.

When to use it
an order mentions a customer ID and you need their name or email to send a receipt from another app.
Watch out
it reads one customer you already identified; if all you have is an email or a name, Search Customers is the better choice.
Clover POS6

Get a Line Item

Action

In Make“Retrieves an existing line item.”

Returns the details of one precise line on an order, the product sold on that ticket, so you can reuse it elsewhere without pulling the whole list.

When to use it
another tool stored the reference of one line and needs its content back to fill a report or a return form.
Watch out
to read every line of an order in one go, List Line Items fits better.
Clover POS7

Get an Order

Action

In Make“Retrieves an existing order.”

Brings back one known order from Clover, with its information ready to map into an invoice, a spreadsheet row or a message to your team.

When to use it
a customer writes to support about a purchase and the ticket already holds the order reference.
Watch out
when you do not know which order it is yet, start with Search Orders; this module reads one known order and nothing more.
Clover POS8

Get List of Customers in CSV

Action

In Make“Retrieves all customers in CSV format.”

Exports your entire Clover customer list as a single CSV file, a handy format for a mailing tool, a backup folder or a spreadsheet import.

When to use it
you want a full snapshot of your customers to send to storage or to share with a partner tool, rather than one record at a time.
Watch out
the output is one file, not one bundle per customer, so pick Search Customers when each person needs processing.
Clover POS9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Clover API to your scenario, using the same connection, for whatever the ready-made modules leave out, such as items, payments or shifts.

When to use it
you need a Clover object that no module above handles, like shifts, and you have found in Clover's API reference where it lives.
Watch out
you write the request yourself from Clover's API reference, so test it with Run once before relying on the response.
Clover POS10

Update a Customer

Action

In Make“Updates an existing customer.”

Changes the details of an existing Clover customer, so a new phone number or email entered elsewhere lands at the register too.

When to use it
a client edits their profile in your online shop or CRM and you want both systems to agree.
Watch out
it edits a customer you already identified, so a Search Customers step placed just before is the usual way to find the right one.
Clover POS11

List Line Items

Search

In Make“Retrieves a list of line items.”

Pulls the lines of an order, one bundle per line, so each product sold can travel on its own to a sheet, a stock tool or a report.

When to use it
you want every product of a ticket copied row by row into your bookkeeping file.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which adds operations.
Clover POS12

Search Customers

Search

In Make“Searches for customers or lists them all.”

Finds customers in Clover that match what you look for, or lists them all, and returns each match as a separate bundle.

When to use it
before creating a customer, to check whether the email coming from your form already exists at the register.
Watch out
it may find nobody, so run it once on a known email with Run once and read the bundles before you chain Create a Customer or Update a Customer.
Clover POS13

Search Orders

Search

In Make“Searches for orders or lists them all.”

Looks up orders in your Clover account, or returns all of them, and sends each result down the scenario as its own bundle.

When to use it
you want to copy orders into a sales sheet or spot one that matches a support request.
Watch out
listing everything can produce a lot of bundles, and each module after it spends one operation per bundle.
Need help

Need help automating Clover POS with Make?

A person reads every message.

FAQ

Clover POS and Make: common questions

01Is the Clover POS Make integration free?
Yes on the Make side: Clover POS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. On the Clover side, you do need a paid Clover account to connect.
02What do you need to connect Clover POS to Make?
You need a paid Clover account, access to the Clover POS Developer dashboard and a Make account. From the dashboard you copy two values: your Merchant ID, found under Account & Setup then Merchants, and a Private token, created in Ecommerce API tokens with API as the integration type. In Make, you click Create a connection on any Clover module, choose your region, paste both values and save. If Clover prompts you, confirm access.
03Does Clover POS trigger Make scenarios in real time?
No. The Clover POS app in Make has no trigger module at all, neither scheduled nor instant, so a sale at the register cannot start a scenario by itself. You start the scenario another way: with a trigger from another app, such as a form or a spreadsheet, or with Make's own schedule on the first module, every 15 minutes by default. From there, Search Orders or Search Customers pick up the Clover data you need.
04What can you do if a Clover POS module is missing in Make?
Use Make an API Call. It sends any request to the Clover API with the connection you already set up, which covers what the 13 listed modules do not, such as items, payments, categories, employees or shifts that the Clover app description mentions. You build the request from Clover's API documentation. The Make doc gives no numeric limit for this app, so test each call with Run once and read the response before switching the scenario on.
05Should you use Make or n8n for Clover POS?
It depends on what you need to automate. In Make, Clover POS comes as 13 ready modules for customers, orders and line items, plus Make an API Call for the rest of the API, all reusing one connection. Keep in mind that the Make app has no trigger, so another app or a schedule starts each scenario. Many apps also exist as an n8n node; check whether the Clover actions you need are covered there too, then pick the tool your team already knows and the one that connects to the rest of your stack.
Same platform

Other docs you might need on this stack.

Browse all integrations