I thought it specifically can't be automated - since the steps involve manual logon to fetch the token

we were curious because they are action you could use in a playbook

between the two actions there's a manual step that requires a login to be able to fetch the token in the second step

so it's "get authorization" first, which gives you a URL to login. You take the URL in your browser, login and get a localhost URL and pass that as a parameter to "Generate token" action

Yes, I know how to generate one. Has anyone tried to automate it, or at least most of the steps.

never mind, dont need to worry about it. It’s going to be fixed by Chronicle in the near future.