Feature ideas

Allow to trigger and approve actions from the MCP server to enhance the integration for both developers and agents

It would be great if Port Self Service Actions allowed to have an input field in table format for users. We need users to input multiple times 4 related inputs which would be better visualized as a table (this is how we manage it in another tool currently). Without a table view, the UX is not good. Use case: Developers need to input network information This information is in a table naturally (DNS | IP | Port | Something else) The information may need to be inputted multiple times in a form They need to make sure the data matches the other data (DNS with IP and such)

Currently, the depends_on functionality in self-service actions only works when the referenced field is part of the userInputs section. Enabling the depends_on for blueprints as a part of Day 2 actions would be beneficial.

For example, if we use a scorecard to represent when an entity meets our organisation standards, and a self-service action to enable teams to address issues where a scorecard has failed. While action triggers can have conditions - which support the "Search & query" syntax. Referencing the result of a specific scorecard is not currently supported. > When using the search a blueprint's entities API route, you can also filter results by relations or scorecards As per https://docs.port.io/search-and-query/#filter-by-relationsscorecards Workaround - it to repeat some of the rules from the scorecard, in the self-service action trigger conditions. But this is not always viable, particularly for more complex scorecard definitions.

Sometimes when an action is going through changes, a platform engineer would want to disable an action for maintenance purposes. It would be great to be able to temporarily disable actions for non-admins.

We'd like to be able to adjust the content of the Approval Message sent to slack for Approval protected actions

For some actions, I would like to be able to display or not some steps. For example, I would like a step for selecting an entity if it exist, or display a step to create it if it is not exists already.

Allow categorizing self service actions for ease of finding appropriate actions for your needs.

In case of very dynamic action forms (where the form changes as result of certain inputs) it would be ideal to be able to make certain inputs required dynamically, as result of a certain field change. An input can be hidden until a certain point, and then when it is visible it might be required. You cannot set it as required, since it if remains invisible it will cause triggering issues.

Right now it is not possible to use JQ when creating conditions for Day-2 or Delete actions. It would be very powerful to have that possibility for advanced searching/filtering of entities