Squarespace automations
E-commerce · 1 integration
Connecting a Squarespace store to the rest of a business stack — order notifications, inventory syncs, customer data handoffs — is one of the most common reasons people reach for an automation platform. The appeal is straightforward: reduce manual work around new orders, form submissions, and fulfillment updates. Which platform you choose matters a lot here, because Squarespace's API has hard ceilings that will dictate what's actually possible at your order volume.
What it costs to automate Squarespace
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Squarespace integrations
Each page compares all five platforms for that pair.
Squarespace triggers & actions by platform
Which capabilities each platform supports for Squarespace.
| Capability | Pipedream | Zapier | Power Automate | Make | n8n |
|---|---|---|---|---|---|
| Triggers | |||||
| App Event Source | ✓ | — | — | — | — |
| Commerce Order | — | — | — | — | ✓ |
| Form Submission | — | — | — | ✓ | — |
| HTTP Webhook | ✓ | — | — | — | — |
| New Commerce Order | — | ✓ | — | — | — |
| New Form Submission | — | ✓ | — | — | — |
| New Order | — | — | — | ✓ | — |
| Schedule | ✓ | — | — | — | — |
| Scheduled flow | — | — | ✓ | — | — |
| Webhook | — | — | — | — | ✓ |
| When a record is created | — | — | ✓ | — | — |
| Actions | |||||
| Send Message | ✓ | — | — | — | ✓ |
| Create a record | — | — | ✓ | — | — |
| Create Record | ✓ | — | — | — | — |
| Custom Code Step | ✓ | — | — | — | — |
| Get rows | — | — | ✓ | — | — |
| HTTP Request | ✓ | — | — | — | — |
| Post Message | — | — | — | ✓ | — |
| Post to Channel | — | — | — | — | ✓ |
| Send a notification | — | — | ✓ | — | — |
| Send an email | — | — | ✓ | — | — |
| Send Channel Message | — | ✓ | — | — | — |
| Send Direct Message | — | ✓ | — | — | — |
| Update Channel Topic | — | — | — | ✓ | — |
Things to know about automating Squarespace
Zapier: Triggers Only
Zapier's native Squarespace connector has exactly one trigger (form submissions) and zero actions — there is no way to write data back into Squarespace through Zapier's native integration. If you need to create orders, update inventory, or push any data into your store, you'll need raw API calls via Zapier's webhook step or switch platforms entirely.
Order Creation Rate Cap
The Create Order endpoint is capped at 100 requests per hour when authenticating with an API Key — a limit that applies per website and is completely separate from the global 300 requests/minute ceiling. Switching to OAuth authentication removes this stricter cap, making it the strongly preferred auth method for any store with real order volume.
Commerce Advanced Plan Required
The Orders, Inventory, and Transactions APIs are only accessible on the Commerce Advanced plan; lower tiers including Business and Commerce Basic cannot use them. API key generation itself requires at least the Core plan, so free and entry-level Squarespace accounts are locked out of automation entirely.
Webhook Fragility at Scale
Squarespace webhooks use best-effort delivery with a 48-hour retry window, but the platform will automatically delete a subscription after repeated failed deliveries. Combined with no guaranteed delivery order and confirmed duplicate events, any workflow consuming Squarespace webhooks must track notification IDs and handle out-of-sequence processing.
n8n Requires Manual HTTP Wiring
There is no native Squarespace node in n8n — every trigger, action, and retry loop must be hand-built using the HTTP Request node against the Commerce API. This is workable for technical users but means common workarounds (e.g., routing through Google Sheets as a middle layer) introduce additional failure points where records can silently drop.
Products V2 Migration Is Mandatory
As of August 30, 2025, Squarespace automatically migrated all sites to Products V2, replacing legacy DOM class names like .ProductItem-* with .product-*. Any custom code or scraping-based integration targeting the old selectors will silently break with no opt-out available.
What breaks at scale
The Create Order endpoint caps at 100 requests per hour per site under API Key auth — that's roughly 1.6 orders per minute before you hit a hard wall and start receiving 429 errors. Because Squarespace doesn't return a Retry-After header, your automation platform (Make, n8n, Pipedream, Power Automate) has no server signal to pace retries against, and queued orders can pile up or drop silently depending on how the tool handles unguided backoff. Switching to OAuth removes this specific cap, but many default integration setups don't prompt you to make that choice upfront.
If your receiving endpoint goes down for any reason — a crashed n8n instance, a misconfigured Pipedream workflow, a Make scenario that errors out repeatedly — Squarespace will retry delivery for up to 48 hours and then permanently delete the webhook subscription without alerting you. The store keeps processing orders, but your automation stops receiving events entirely and there is no automatic re-registration; you only discover the problem when you notice downstream systems (Slack notifications, inventory sync, CRM updates) have gone quiet.
Users report hitting 429 errors after retrieving as few as 1–2 pages of orders (batches of 5–8 requests) within a few minutes — well below the stated 300 req/min global limit. This suggests real-world throttling is more aggressive than documented, and high-volume polling workflows in n8n or Power Automate that paginate through order history on a schedule can exhaust their usable quota before completing a single full sync. Without published rate limit response headers to guide backoff, these workflows stall unpredictably and require manual intervention to resume.
Frequently asked questions
How do I automate Squarespace orders with Zapier, Make, or n8n?
Make (formerly Integromat) offers the most capable native Squarespace module, supporting order, transaction, and member profile triggers. Zapier's native connector only supports form submission triggers with no write-back actions, making it unsuitable for order automation without raw API calls. n8n has no native Squarespace node, so all order automation must be built manually using the HTTP Request node; Pipedream and Power Automate similarly require custom HTTP steps for Squarespace order workflows.
What are the Squarespace API rate limits for automation?
The global rate limit is 300 requests per minute, but the more painful constraint for e-commerce is the Create Order endpoint limit of 100 requests per hour when using API Key authentication — this cap does not apply with OAuth. Squarespace does not return a Retry-After header on 429 responses, so any platform (Zapier, Make, n8n, Pipedream, Power Automate) must implement blind exponential backoff to recover gracefully.
Do Squarespace webhooks work with automation platforms?
Squarespace's Webhook Subscriptions API supports three events — order.create, order.update, and inventory.update — and uses HMAC-SHA256 signatures for verification. Delivery is best-effort with at-least-once guarantees, meaning duplicates are possible and order is not guaranteed; platforms like Make and Pipedream that have built-in deduplication handling are better suited than a hand-rolled n8n HTTP node. You can register up to 25 webhook subscriptions per site, and Squarespace may auto-delete subscriptions after sustained delivery failures.
Which Squarespace plan do I need for API access and automation?
You need at minimum the Core plan to generate an API key at all; the Forms API (used by Zapier) is available from Core upward. However, the Orders, Inventory, and Transactions APIs — the ones needed for meaningful e-commerce automation on any platform including Make, n8n, Pipedream, or Power Automate — require the Commerce Advanced plan specifically.