Hi @denverfix, looks like you’ve found the relevant header
So what’s left here is finding the right cookie seeing your page is sending multiple cookies in the set-cookie header and then extracting its value. You could for example use JMESPath for the job.
Assuming you want to fetch the localization cookie from https://merch.n8n.io/, a possible workflow could look like so:
In addition to JMESPath, I am also using .split() to split up the header value into the relevant parts.
The result would be the actual cookie value. Hope this helps!
I want to generate the cookie when I login to the site.
Hi @denverfix, in that case you’d need to adjust the example so it reflects the requests sent when signing in through your browser.
Does the event generate the cookie all the time?
This depends on the page you are logging into. Assuming there’s no documentation you might need to simply try it out. In most cases the cookie will be good for multiple requests, but depending on the exact page you are using it might require a fresh cookie for every single request.