The Automation feature designed in Assets is limited and currently there is no option in the HTTP Request Action to add Headers, as outlined in our official documentation at Configuring Assets automation rules

Because of this, it's not possible to use Bearer Token for Authentication in Assets automation rule for Http Request action.

The Automation for Jira that also comes bundled with Jira is a more complete feature for creating automation rules, but it's not directly related with Assets objects, but with the whole instance of Jira, and it does provide a way to add headers and use bearer token with external services, for example: Create and edit masked secret keys for automation rules. However, currently there is no option to update Assets Object Attribute value using Automation for Jira, as seen in this feature request: JIRAAUTOSERVER-464.

Due to this, in certain scenarios where the Customer needs to create an automation rule in Jira Assets to change certain objects to an external service using an API call, this external service may not allow to use basic authentication. This suggestion aims to implement a field where the user can add Headers to the API Call, such as "Authorization: Bearer <TOKEN>".