Feature ideas

Today you can only update one entity using the Upsert entity invocation method, It's true that as a workaround you can send an api call to a custom webhook and update multiple entities using the custom webhook, but it'll be ideal and much clearer to have this ability in the invocation method itself

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.

Currently, the message sender only supports slack. Some organizations use Microsoft teams, which means they cannot create notifications for their teams.

Add a cancel button to self service actions and allow configuration for the cancel button to invoke external communication.

Currently, it's only possible to configure an automation to be triggered on one specific event. For example, when an entity is created or when it gets updated. As developers, building workflow automations, we would like the ability to configure a single automation to be triggered on multiple entity events, allowing us to manage fewer automation resources and avoid code repetition.

We will improve our interface for Automation (to match with one of Actions) to simplify the creation of new automation. Some early preview screenshots are attached!

When an automation is triggered by the deletion of an entity, the "before" event data currently does not include entities related to it unless the relation between the two blueprints is upstream. We need the data to also appear for downstream and indirect relations.

Most of the time, when we create an automation, we'd like to apply it to all existing entities so they will all get aligned based on the automation and then the automation will be triggered for new events. Currently, the entities will get aligned only after all of them will get the respective event which potentially can take a lot of time. Having something similar to Gmail filters' "Also apply filter to X matching conversations" feature would really improve the UX of automation as today we need to manually resync or do a dummy migration in order to trigger the automation alignment.

Right now, Port admins can create automations that can, for example, upsert entities to create a "changelog" type of experience. While this can be an acceptable method for "notifying" entity owners about changes to their entities, a better solution would be in-app notifications in Port to notify the owning team whenever a project or an environment changes

The ability to choose the invocation method of an automation to be "Sending an email" For example - Whenever a scorecard is degraded, send an update email (Just like the Slack use case, but sending the report in email)