Generally speaking from a security and reliability standpoint, automation should use a “service account” that is not associated with one specific person. This allows for separate controls/polices/etc. for user accounts and system accounts.
One benefit is, say your organization forces user password changes every 60 days. They may have a different policy for service accounts that never forces them to change (not the best idea). Or maybe at a less frequent interval like once every 6 months or once a year. This keeps people from having to update a bunch of different places each time they change their own password. There are also products that can manage service accounts, their passwords and automatically update the systems using those credentials when the password is changed.
Another scenario is when a person leaves an organization and their accounts are terminated, the automation they created does not start to fail due to it using that person’s credentials which are now disabled/deleted.
Using different credentials also protects the person. With SSO being more and more prevalent, what if somebody else was able to obtain your clear-text credentials (could be in a log file)? Now they can potentially access the HR system, the email system, or other systems where you have trusted access, all as you.