Currently, all automation components are offered when creating or editing an automation rule.
However, some components are not relevant for the site and thus are not usable in automation rules. It doesn’t make sense to offer them for use in a rule. Unusable components should not be shown.
This could be as simple as a single checkbox allowing users to filter out unusable components. Or it could be something more complicated that site/app admins can customize. Or it could just be on all the time.
Here are some examples of unusable components:

• All of the Loom Triggers and Actions when Loom is not part of the site. Compass, Guard Premium, Service (JSM), DevOps (GitHub, Azure etc).

• Actions related to Confluence, Google, GitHub, Teams, Slack, Twilio, Okta, Entra, Bitbucket, Salesforce, Datadog, Jenkins, Ansible, New Relic, AWS, Workato, etc.

This is a burden for expert users, and a significant impediment to learning for users that are new to Jira automation.