In a Power Platform custom connector, the visibility property for each action determines if and how it is displayed to the user in Power Automate or Power Apps. If actions are missing from the designer, it is highly probable their visibility is set to internal, which hides them from the user interface. To resolve this and make the actions appear, you must change the visibility setting to none. The none setting is the default value and ensures the action is always visible to the maker building the flow.

B. Change the connection name. The connection name is a user-defined label for an authenticated instance and does not influence which actions are available.
C. Change the parameter drop-down type to Static. This setting configures the input experience for a parameter within an action; it does not control the action's visibility.
D. Add an action description value. The description provides helpful text to the user but has no effect on whether the action is displayed in the designer.
E. Set the action visibility option to Internal. Setting the visibility to internal is the cause of the problem, as this property explicitly hides the action from the user. ---

1. Microsoft Learn Documentation: Create a custom connector from scratch.

Reference: In the "Define actions" step of creating a custom connector, the UI provides a Visibility property for each action. The documentation states the options are none, advanced, and internal. Internal visibility hides the operation from the user. To make it visible, it must be set to none or advanced.

Section: Step 3: Define the actions of the connector.

2. Microsoft Learn Documentation: OpenAPI extensions for custom connectors.

Reference: This document details the x-ms-visibility OpenAPI extension, which corresponds to the Visibility property in the UI. It specifies the values: none (default, always visible), advanced (in a secondary menu), and internal (not shown in the UI).

Section: x-ms-visibility.