What is your goal?
A working scenario for Squarespace to Watch Orders (“Pending” status) > (routed to) Get Orders by product > Add Row for Google Sheet that captures ALL new orders, even those using the new native Squarespace payment plan option.
What is the problem & what have you tried?
I am excited to have a working scenario for Squarespace to Watch Orders (“Pending” status) > (routed to) Get Orders by product > Add Row for Google Sheet. Orders were added to the sheet successfully except orders that utilize the new native Squarespace payment plan option. The fulfillment status is the same “Pending” as all other orders. Thoughts to successfully catch these “1 of 2 installments paid” orders to Google Sheet through Make? All other fully paid orders are being added as a new row successfully even though ALL orders are “Pending” status in Squarespace.
Screenshots (scenario flow, module settings, errors)
Hey @anderaly, Welcome to the community! 
I think the gap is before Google Sheets, not in the Add Row module.
Squarespace payment-plan orders have their own payment-plan statuses, and “Pending” fulfillment is not a reliable condition because fulfilling the order doesn’t control the payment-plan schedule.
If your scenario is only using Squarespace > Watch Orders, try adding the row immediately on order creation using the Order ID as a unique key, and remove any filter that assumes the order must behave like a fully paid order before it reaches Google Sheets.
If you also need to catch later installment activity, you’ll probably need to handle order updates as well, because payment-plan activity can show up as changes on the same order over time.
Let us know how it goes!
Regards,
John
@johnai.tech Thank you so much for the help! Even after removing the “Pending” condition on the Watch Orders module, Make is still not able to “see” the payment plan orders. I have attached the current scenario structure (Get Orders was tested before and after the router). Also attached below is choosing what to run - the payment orders are not showing (should include orderid: 1375).
@anderaly
The reason order 1375 isn’t showing in the “Choose where to start” list is that the payment plans orders of Squarespace use another kind of webhook event than the regular orders do. The Watch Orders module used by Make is configured to listen to the order.create event, but Squarespace payment plans use an entirely different event - payment/subscription one, and the native Make module does not recognize it at all.
The fix is to bypass the native Watch Orders module and use a Webhook instead:
-Use the Custom Webhook module as the trigger for your Make workflow, and copy the webhook URL it generated for you.
-In Squarespace settings, navigate to Developer Tools > Webhooks, paste the URL there and subscribe to all kinds of order events, including the payments
-Now, Make will be notified about all order events fired by Squarespace, including the payment plans orders.
-Afterward, put a filter in the workflow to check if it’s indeed the kind of order event you need before pushing it to Google Sheets
That way, you’ll gain access to any kind of order event Squarespace generates.
@Nicholas_A In theory, great solution - problems arise when Squarespace doesn’t support easy “drag and drop” webhook functionality in 7.1 even with Commerce Advanced plan. All require a Webhooks Subscriptions API, which is more complicated than pasting in a webhook url. Without a step-by-step guide for my current low level of developer expertise, it seems Make and Squarespace will not talk appropriately to capture all orders.
This may not be a Google Sheets problem yet. I would first prove where the payment-plan order disappears.
The useful split is:
- the payment-plan order never appears in the first Squarespace watch-order bundle;
- it appears in the first bundle, but gets filtered out by the router / get-order-by-product step;
- it reaches the Google Sheets module, but the row creation is skipped or errors.
Because normal paid orders work and only the native payment-plan orders are missing, I would not start by changing the sheet. I would run one controlled test order and inspect the output bundle immediately after the first Squarespace module.
If the bundle is missing there, Make never got the same event/order shape for payment-plan orders.
If the bundle exists there, the next place to inspect is the router condition or the product/order lookup result.
Safe thing to check publicly: does one payment-plan order appear in the first Squarespace module output bundle at all?
No need to post customer/order details publicly; just the yes/no at that first module is enough to choose the next branch.
Thank you - it’s already been shared in previous post that the payment plan order does not show up in Squarespace Watch Orders in Make. I agree that Make is most likely not seeing the order at all, but there is not a simple Webhook fix, but rather API integration developer work.
That makes sense. If Watch Orders never sees the payment-plan order, I would stop treating this as a Sheets or router issue.
The next split is whether Squarespace exposes the event you need through an API surface that Make can poll/reconcile, or whether you need a small custom middleware step to normalize payment-plan orders into the same row schema as normal orders.
The first spec question I would write down for a developer is: do you need only the initial payment-plan order captured, or every future installment/payment event as separate rows too?
That answer changes the build from a simple order-sync fallback into a subscription/payment-event sync.
