I'm not sure if anyone can help me with this issue, but here we go. I am trying to automate my Jotform appointment to create a customer appointment in Square using a Zap. For context, I have a pre-paid service, and I need different appointment times from my non-prepaid appointments. Unfortunately, I can't customize the appointment system to block out my schedule for various types of appointments. Additionally, I can't customize it so that some services require a hold card while others don't.
The issue I keep running into is the valid date/time call data for the start_at field in the Zap. Because the Square integration in Jotform only allows for payment processing, I had to create a Zap so that the appointment appears in my appointment book on Square.
Because the form field data from Jotform to Square doesn't match for appointment times, I had to create a workaround so that the automation follows this flow: Jotform (new submission) --> Google Calendar (Find Event) --> Google Sheets (Create Spreadsheet Row to change the input field for the date to "start_at") --> Formatter (reformat date to YYYY-MM-DDTHH:mm:ssZ+0000 format) --> Square (Create Customer) --> Square (Create appointment).
The tests are fine until I get to the create appointment test trigger for Square, and the input data for the "start_at" field is incorrect. I think the issue is either with the Z value or the format in general. The formatting that it looks like Square uses the API is the reformat I've used above, with I think the Z value being GMT time zone. Based on triggers from other Zaps, that's the format that appears and what seems to be the time zone when we are in DST in the US.
I've also tried inputting the format manually without a Z value, with just Z as the unknown and no value, and with a manual value but no reformatted value in the time zone field, and it still returns an error.
Thank you to anyone who has run into this issue and knows of any solutions.
Hey there 👋
Wow—first off, kudos to you for building such a detailed workflow! That’s some serious Zapier ninja work 💪✨ You’re right that the roadblock here almost always comes down to the start_at format. Square’s API is picky—if it’s even a hair off, it’ll throw that dreaded error.
A few things that usually help:
Exact Format Needed
Square wants YYYY-MM-DDTHH:mm:ssZ (ISO 8601 in UTC). For example:
Square Community
Square Products