If you are saying you are embedding the admin creds in your script. This is a very bad risk posture. There a few free tools to convert .ps1 to .exe, yet they are not true .exe, and can be easily reversed back to plain text. So, exposing any creds in the script/exe.
The suggested Schedule Task is the most prudent way to do this and you can just use the script. Set the ST with whatever creds you need, or set it to run with highest creds in the ST UI settings, which is protected via the built-in Windows DPAPI, so not reversible.
You can also put a check for admin in the script using the 'Requires' statement, to ensure that admin level is being used and you can set it to self elevate if it is not. However, the will still prompt someone to enter admin creds.
Then there is also PS JEA implementation you may want to consider.
Just Enough Administration: Windows PowerShell security controls help
protect enterprise data
Leverage PowerShell Just Enough Administration for your Helpdesk
Updated do to the request for clickable stuff.