Port automations to make the webhook response body payload accessible in subsequent steps. Currently, when a webhook (e.g., from a Logic App) returns data such as a SharePoint link, the response body is visible in the action logs but cannot be referenced in automation payloads. The only available fields are user inputs, trigger context, and run metadata, which means valuable response data from the webhook cannot be used downstream (for example, in notifications or follow-up actions). Enabling access to the webhook response body would remove the need for workarounds and make automations more flexible and powerful.

The automation feature in Port allows users for event driven actions. At the moment, this feature allows users to take only one action at a time such as updating an entity, calling an external API, invoking an action. It would be possible if users can define a series of steps in the invocationMethod such that once an automation is triggered, it will follow the steps and complete the entire workflow. At the moment, if my use case involves making two API calls to an external tool, updating the catalog, automations aren't able to help so I would resolve to using a GitHub action for this complex use-case

Following the support for self service workflows, it would be useful to get a UI for them to be able to track progress and easily edit the flow.

In certain scenarios in bigger organizations it is not unusual to have an approval flow that will involve more than one team.

The review for a request can be done in

* parallel - request denied by any of the teams would stop the workflow

* sequentially - request review progress to the next step only after the previous team has approved

Even a basic implementation on top of the existing could provide a lot of value and further anchor the use of the portal as a coordination tool for processes and teams.