Automate Squarespace with Make: What really works in the shop

The Make extension is an entry in Squarespace that points to Make, a service that runs processes between apps on its own. Make used to be called Integromat, and such a process is called a scenario there. In the Squarespace extensions directory, Make is listed with the note “Starts at $0.00/month”, in English only and without details on plan or setup. The “Connect to site” button leads to the integration page on make.com; the actual work happens in Make. According to the Make documentation, the connection to the shop runs through an API key. That is a kind of password for programs, which you create in Squarespace and enter in Make.

Make offers 26 modules for Squarespace. Three of them are triggers: they start a process as soon as Make finds a new or changed order, a product or a payment when it checks. The other modules can retrieve orders and mark them as shipped, create, change or delete products, variants and product images, and adjust stock levels.

Make mainly takes over what happens by hand after an order today: transferring it to a spreadsheet or accounting and informing the team.

You may know the routine: the order overview in Squarespace on the left, the spreadsheet on the right. Copy the name, copy the amount, item, VAT, next row. Make can take over exactly these steps. What that ends up costing depends, for a quiet shop, less on the number of orders than on an inconspicuous setting: how often Make asks your shop for news.

An example: an order with three items comes in. At the next check, Make finds it. A ready-made Make template writes each item as its own row in Google Sheets. A further step creates the invoice in accounting, and a third reports the order in Slack or Microsoft Teams. Such invoice flows are described for Wave, QuickBooks and Xero, among others. Make has its own apps for Bexio and Lexware Office; it is worth checking beforehand which steps they offer in detail.

Also possible: taking over stock levels from a supplier’s list, passing orders on to a CRM such as Zoho or ActiveCampaign, or reconciling them with an inventory system such as Katana. We found no ready-made app in Make for Abacus, TWINT or the Swiss Post. That does not rule out a connection.

Most of these processes read orders and pass them on; Make hardly changes the order itself afterwards.

Only the shipping status: Make can mark an order as shipped. Items or address cannot be edited afterwards with the ready-made modules. There is no “Update an Order” module. The existing “Fulfill an Order” module is still enough for a useful process: when the warehouse reports a parcel as sent, Make completes the order in Squarespace.

Make also sets limits for other Squarespace data. There are no ready-made modules for contact forms, contacts, discounts, pages, blog and members. According to the developer documentation, Squarespace explicitly releases form data only to Zapier (“for Zapier integration only”). The article on the Squarespace Contacts API shows how contacts can be connected directly to a CRM.

Make notices a new order only at its next check. You set how often that happens yourself: every 15 minutes at most on the free plan, up to once a minute from the Core plan. Because each check costs one credit, the free plan around the clock covers about one check per hour, Core about one every 15 minutes. The calculation is under “What does Make cost?”.

The reason lies in the type of connection. According to the developer documentation, Squarespace sends instant notifications only to apps with OAuth login. That is a login in which you grant an app access. For API keys the documentation says tersely: “API keys are not supported”. Make connects through such a key and therefore checks at intervals. The Make community confirms this: “This is not instant”.

For accounting and a spreadsheet this is rarely a problem. Whether an order appears in the spreadsheet at 2:03 pm or at 3:00 pm hardly matters day to day. If the team needs to start packing immediately, Zapier reports new orders without delay.

Make is free up to 1,000 credits per month (Free plan). According to the pricing page, the Core plan costs $9 per month for 10,000 credits, probably with annual billing (as of November 2026). The free plan allows two active scenarios.

Credits are Make’s currency, and each step in a process usually costs one. Easy to overlook: the check also costs one credit, even when there is no new order. Make calls such runs “check runs”. A quiet shop therefore pays mainly for asking:

Because a step usually costs one credit, these 280 credits cover about 50 orders a month at five steps per order. Make itself advises running processes only during office hours. When credits run out, the scenarios stop. As soon as credits are available again, the triggers catch up from the last run, according to Make. Unused credits expire at the end of the term.

According to Make’s documentation, you connect Squarespace and Make through an API key that you create in Squarespace and store in Make. The prerequisites are a Squarespace plan with shop features and API access, and a role with access to the developer settings.

The key is created under Settings > Advanced > Developer API Keys. It gets a name, access to the Commerce APIs and a permission level: orders, inventory and products can be read only, or read and written. Squarespace shows the key only once, after which it stays valid as long as the website is active. It is worth storing it safely right away. It is just as sensible to grant only the permissions the process needs: anyone who only writes orders to a spreadsheet gets by with read access. In Make this becomes a connection to Squarespace, followed by triggers, filters and the further steps.

Setup to tick off and copy