Feature ideas

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

Give access to properties of the entity being updated in the upsert by allowing .entity notation or similar Would allow counters to be incremented when an event takes place e.g. {{ . entity.properties .counter + 1 }} If title or string property needed to contain string from most recent updated related entity would be able to separate out the current string e.g. {{ . entity.properties.name | split(" ") | .[0] + .event.context.entityIdentifier }}

When performing an entity upsert via automations, API, Terraform, GitHub Actions, etc, any relationship values are overwritten with that specified on the upsert request. This makes maintaining "many" relationships non-trivial, as now the caller must: Fetch the current entity state Extract the relationship which are to be modified Manipulate the relationship arrays Perform the upsert API call Notice the above requires 2 API calls (GET and PATCH) - meaning that, in any scenario where it's possible to have multiple jobs running in parallel (e.g. automations, event-driven workflows), we also now need some form of "transaction locking" in place, to ensure we don't end up with relations being overwritten from a race condition.

Would like the ability to schedule reminder notifications for approvals that haven't been actioned within a specified period. This feature would help ensure that pending requests are addressed in a timely manner, reducing the risk of delays or oversights in the approval process.

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!

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, 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.

Nothing hurts more than working on an automation in Port for 15 minutes and then have the browser accidentally refresh the page so you lose all of your work. ❤️‍🩹 It would be ideal if Port saves the state of my JSON editors in the browsers local storage so that if I exit the browser and come back I can finish my amazing automation.

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