> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/cookie/import-cookie.md).
# Import cookie
Import cookie is the action of loading a string or a file of structured cookie data into the browser to automatically log the account into a successful login state without needing to fill in Username/Password.
🎥 Watch the tutorial video: [Here](https://youtu.be/OLHoUtANkXw).
#### Configuration parameters:
* Cookie file: The absolute path to the `.json` file containing the cookie structure (or directly pass the data variable).
* Structure format: Must be in standard JSON format.
#### Important operational notes:
* Need to Go to URL first: You must allow the browser to access the correct target website before calling this action (For example: Go to `facebook.com` first and then Import cookie Facebook, only then will the cookie match the correct domain).
* Only valid in the current session: All cookie data loaded is only temporarily effective in that working session. As soon as you close the browser Profile, this amount of cookie will automatically disappear and will not overwrite the original data of the Profile.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.gpmautomate.com/automate-en/action-guide/cookie/import-cookie.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
