Feature ideas

Ability to manage integrations through Terraform The issue right now is that the user needs to create integration manually using UI, then we can import to terraform code. We want to have also creation part in terraform. Terraform is by default tool which should support all crud(create/read/update/delete) actions. In this case create action is not supported. This is problematic when we will have multiple integrations and multiple environments as we will need to do this manually per each integration and environment. (ed

Currently, custom widgets only allow HTTPS links. Any attempt to use a custom URI scheme (deep link) is blocked, and the browser console displays: Requested Enhancement: Support custom URI schemes in custom widgets by allowing administrators to configure or whitelist approved protocols (e.g., cursor://, claude://, claude-cli://, codex://) instead of restricting links to HTTPS only.

Kaban widget: add flow limits" and "express row" for high-priority items the initial phase of the Kanban view would be a basic representation, allowing users to group columns by properties and move cards. FR is to add the "flow limits" and "express row" features for future additions.

Requesting re-run button/capability for workflow runs. During development and testing, we have to create a new event every time we want to test a workflow change. Being able to re-run a previous workflow run would significantly speed up the iteration cycle.

I want to be able to trigger an automation or workflow for any self-service action. Currently you can trigger an automation for a self-service action, but it's tied to a specific action rather than ALL actions.

We'd like a 'Shared with me' section in the sidebar. When a private page is explicitly shared with a user, it automatically appears here for that user. This gives shared pages a predictable location instead of relying on direct links.

Right now the Input node supports only a static list of users. Adding teams, roles, and dynamic policies will enable more advanced human-in-the-loop use cases. For example: requesting approval from the on-call engineer before deployment outside business hours.

Port should support GCP Service Account (JSON key) authentication as an additional authentication method when configuring external MCP Connectors — enabling secure, non-interactive M2M connectivity to Google-hosted MCP servers such as Google Logs Explorer. Users should be able to configure an MCP Connector using a GCP Service Account JSON key, where Port: Accepts client_email and private_key stored as Port Secrets Handles JWT generation and short-lived access token renewal automatically in the background Passes the resulting bearer token to the MCP server on each invocation

the usage records of how the MCP is used: Total Tool API Calls (Daily) Calls per Active Client Unique Tools Used Most Used Tools What tools are accessed with what inputs / outputs - what types of blueprints and properties are being accessed - what skills are discovered through Port (or any other blueprint/catalog as needed). Active MCP Clients (Daily/Weekly) Total MCP Connections