Use Octoparse Auto Login and cookie controls to test and maintain permitted, session-dependent task workflows.
For websites where you are authorized to sign in, Octoparse can save and reuse the Cookies from that session. Auto Login is available from version 8.6.8. The website still decides whether a saved session remains valid, so test every saved or imported Cookie configuration with a small run.
Select Auto Login in the task editor, sign in in the pop-up browser window, then select Set up Auto Login. Octoparse saves the resulting Cookies to the task. It does not add your username, password, or login clicks as workflow steps.
Use Browse Mode to sign in or reach the page state you need. Then select the relevant Go to Web Page action, turn on Use cookie, choose Use cookies from the current page, and select Apply. This saves the current page’s Cookies for that Go to Web Page action.
Export the Cookie string from a browser where you are already signed in, then paste it into the Cookie box for the relevant Go to Web Page action and save the setting. Use this when you cannot sign in inside Octoparse.
Run a small test and confirm that protected content, rather than the login page, is returned. You can update, replace, disable, or delete a saved Cookie setting when the session expires or the page no longer accepts it.
Octoparse lets you keep, update, or clear a task’s Cookies. You can clear Cookies and cache before opening a page, on a schedule, or when the IP changes.Clearing removes the stored session state. It can help if an old page state causes loading problems, but a login-required website may send the task back to its sign-in page. Test the setting on one page before using it in a larger login-required run.In the task editor, Octoparse 10.2 can automatically accept a supported Cookie consent banner. This applies to supported “Accept all” controls, including eligible banners that appear late or inside an iframe or Shadow DOM. It does not handle every popup, subscription wall, login page, CAPTCHA, or Cookie wall.
Open a signed-in page. It should not ask you to sign in or complete another verification step.
Cookie or cache clearing
Open the intended page. It should still show the signed-in content.
From Local to Cloud
Run a small Cloud test. Confirm that the signed-in page and required data are available there.
Cookies can contain sensitive session data. Do not put complete Cookies, credentials, or other secrets in logs, screenshots, or support tickets. Do not use this workflow to access data you are not authorized to view.
