Expose response headers in HTTP or SDK

I need to take the session cookie from the response body of my HTTP connection and use that in the request header of my next HTTP action to have access to the API endpoint.

Kyle Tan

said about 7 years ago

There are also situations where we need to get response headers within the SDK :(

Jeremy Farber

said about 7 years ago

This is causing lots of time figuring out errors from the SDK. If we get an error that is in the response header then the only way to figure out what the issue could be is by creating the action is another tool like Postman. Please change this.

Jeremy Farber

said almost 7 years ago

Guys you've done a great job with the SDK and being able to make custom connections, but being unable to see the response headers and use them for errors make the task of troubleshooting an issue almost impossible. PLEASE PLEASE FIX THIS.

AtlasIdentity

said almost 7 years ago

This is a crucial change for us. Without access to the HTTP response headers we cannot paginate through the data exposed by our target 3rd party API. Workato is already exposed a headers object for the HTTP request entity, therefore this appears to be a simple change to also expose this for the pre-existing HTTP response entity. Come on Workato please prioritize this glaring gap in the SDK!

Nick Ciccocioppo

said over 6 years ago

Yes! Absolutely needed!

CJ Wee

said over 6 years ago

Hi all,

You can now access header response in SDK. Documentation on that here: http://docs.workato.com/developing-connectors/sdk/request.html#handling-reaponse

Accessing header response in HTTP action has also been around for some time.

Jeremy Farber

said over 6 years ago

Can we do something with Error as well?

Still can't find your solution?

Send us a ticket, we will try our best to assist you with your problem