Capture Cookies

Type: capture_cookies

This action will capture the browser cookies currently saved for the web page you are on and return them as a JSON object with key/values.

Tips for using capture_cookies action

• Run this after the steps that set the cookies you want, such as logging in or accepting a cookie pop-up.
• Treat the output like a password. Session cookies are credentials.
• Use it to work out why a page looks different to what you expected; the cookies often explain it.
• Pair it with a screenshot when you're debugging a login, so you can see the page and its cookies together.

Parameters

See universal parameters.

Usage

Capture the cookies of the current page

"actions": [
    {
      "type": "capture_cookies"
    }
]

FAQs

When do I use capture_cookies?

Use it when you need to see or save the session a page is running on after a login, after accepting cookies, or when a page behaves oddly, and you want to investigate why.

What does capture_cookies return?

It returns a JSON object containing the cookie names and values the browser holds for the page, captured at the moment the action runs in your list.

When should I run capture_cookies in my action list?

Run it after anything that sets the cookies you care about, like logging in or dismissing a banner. If you capture first, those cookies won't exist yet.

How do I capture cookies after logging into a site?

Use type for the username and password, click for the submit button, a wait for something on the logged-in page, then capture_cookies.

Can I reuse captured cookies in another request?

Not at the moment. Each browser request starts a fresh session, so cookies captured in one request can't be sent with the next. We're working on it. If this would be useful for what you're building, email support.

What information does capture_cookies return?

Cookie names and values only. Domain, expiry and flags like httpOnly aren't included in the output at the moment.