Skip to main content

REST Web Services POST request - no response payload is being returned

  • Aug 24, 2026 3:19 PM UTC
  • 3 replies
  • 60 views

The REST Web Services POST request successfully creates the event in Google Calendar; however, no response payload is being returned, and the Body output variable remains blank.

3 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+6
  • Automation Anywhere Team
  • Aug 24, 2026 3:21 PM UTC

​@neeraj attri Google’s APIs are… well, picky. Any missed parameters or anything will cause it to fail. Just check, double check, and triple check everything. Make sure your input variables have the expected values.


  • Author
  • Cadet | Tier 2
  • Aug 24, 2026 3:44 PM UTC

I’ve reviewed the configuration multiple times and everything appears to be correct. In fact, when I use the exact same values and configuration in another developer's API task, the response payload is returned successfully. However, in my case, the response remains blank.

The OAuth connection is active, and I also refreshed/re-authorized the connection before executing the API task. Despite the event being created successfully in Google Calendar, the response body is not being returned.


Shreya.Kumar
Pathfinder Community Team
Forum|alt.badge.img+4

​@neeraj attri , can you try hitting the endpoints in an API platform like Bruno/Postman and observing the output? I that doesn’t work, I would highly recommend debugging the workflow in Automation Anywhere, and following the payload as well as response variables. That would give us more information to help you further.