Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hey guys, 

I'm building a Zap that uses the Acuity Scheduling API to retrieve available appointment dates. I'm encountering an issue where the month parameter in the API request isn't accepting the dynamically generated "YYYY-MM" format from a "Code by Zapier" step.

I've confirmed that the code correctly outputs the "YYYY-MM" value as a string, but it doesn't appear as an option in the month parameter's mapping dropdown. I've tried refreshing the Zap, reconnecting my Acuity account, and explicitly defining the output type in the code, but the issue persists.

Could this be a bug or limitation in how Zapier handles data types or mapping between the code step and the API request action? Are there any workarounds or suggestions you can provide?

Hi ​@Noob_developer 

For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode with the field mappings.

Also, link to the Acuity API endpoint documentation you used to configure the API request.

Just to advise, when posting a screenshot to the Community, it is essential to obscure any sensitive information within the screenshot for security purposes. Thank you. We're looking forward to troubleshooting your issue further.

Hi ​@Noob_developer 

For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode with the field mappings.

Also, link to the Acuity API endpoint documentation you used to configure the API request.

 

Hi, here are some screenshots, and the link to the Acuity API endpoint documentation below.

 

The screenshots in order:

  1. screenshots 1 and 2 showcase the result of my API request action’s test step.
  1. Shows the configuration of my API Request action, and the month parameter's mapping dropdown. (As you can see, the month parameter is currently set to a static value, but I want to dynamically populate it with the yearMonth output from the Code step (screenshot 3 ).)
  2. Shows the successful execution of my "Code by Zapier" step, which correctly outputs the yearMonth value in the "YYYY-MM" format.

https://developers.acuityscheduling.com/reference/get-availability-dates

 



 

 

 

 

​@Noob_developer 

For the Acuity API request configured in the Zap step, the Query String Parameter “year” is not a supported option from the API endpoint documentation, so make sure to remove that.

Screenshot shows the Acuity API request without a variable mapped to the “month” query string parameter.

Screenshots show the Acuity API request as Zap step 2, but it is unclear what Zap step the Code step is.

The Code step would need to come before the Acuity API Request Zap steps, so you can map the variable from the Code step.

Also, instead of using a Code step, you may want to try using this Zap action: Formatter > Date & Time > Format

NOTE: Zap steps that use the Formatter app count as 0 Tasks in Zap Runs.

Help for Formatter: https://zapier.com/apps/formatter/help

Help link about using system generated timestamps in Zap steps: https://zapier.com/help/create/customize/insert-the-time-your-zap-runs-into-a-field

 

Reply


Terms & Conditions