Have you tried using LinkedIn's REST Api instead of retrieving heavy pages, filling in some form and sending it back?

Your code is prone to be broken whenever LinkedIn changes some elements in their page. Whereas the Api is a contract between LinkedIn and the users.

Check here https://developer.linkedin.com/docs/rest-api and there https://developer.linkedin.com/docs/guide/v2/concepts/methods

Moreover, for the scheduling part, you can use cron.

If you're looking for a 100% Python solution, you can use the excellent Celery project. Check its periodic tasks.

About the code itself

LinkedIn REST Api

Have you tried using LinkedIn's REST Api instead of retrieving heavy pages, filling in some form and sending it back?

Your code is prone to be broken whenever LinkedIn changes some elements in their page. Whereas the Api is a contract between LinkedIn and the users.

Check here https://developer.linkedin.com/docs/rest-api and there https://developer.linkedin.com/docs/guide/v2/concepts/methods

Credentials

So that you don't have to pass your credentials through command line (especially your password, which will be readable in clear through history), you should either

• use a config file (with your Api Key) and read it with ConfigParser (or anything else, depending on the format of your config file (json, python, etc...)
• or set them into your environment variables.

For the scheduling

Using Cron

Moreover, for the scheduling part, you can use cron.

Using Celery

If you're looking for a 100% Python solution, you can use the excellent Celery project. Check its periodic tasks.