Feature ideas

Expose the organization ID (orgId) natively in the Port Workflows run context to match the functionality of legacy actions and automations. Currently, workflows only expose user details like email and name. Having the field available directly in the context out-of-the-box will simplify workflow configurations.

Current State: Port supports generating pre-filled action execution URLs for self-service actions using JSURL encoding, following the pattern: https://app.port.io/self-serve?action=ACTION_IDENTIFIER&actionInputs=ENCODED_INPUTS This mechanism does not extend to Workflows. Workflows currently have no equivalent shareable or pre-filled execution URL, and no dedicated link is attached to a workflow instance. Problem: Users who have adopted Workflows cannot: Generate bookmarkable or shareable links to trigger a specific workflow with pre-filled inputs. Embed workflow execution links in documentation or external systems. Use workflow URLs within entity properties (e.g., calculation properties) to trigger workflows in context — a capability that exists for actions. Proposed Solution: Introduce a URL scheme for Workflows analogous to the existing action URL pattern, supporting: A stable, shareable URL per workflow (e.g., https://app.port.io/workflows?workflow=WORKFLOW_IDENTIFIER ) Optional pre-filled input parameters via JSURL encoding Support for embedding these URLs in entity properties and calculation properties to trigger workflows in-context

Allow stopping a resync in the middle of a sync.

Enable AI agents to use tools from MCP connectors in automated workflows. A current workaround is to import data into the Port catalog, but this removes real-time access. Adding MCP connector support to agent workflows, with the same RBAC and audit controls, would allow more useful and flexible use cases.

At the moment you cannot run additional filters on calculation property. This makes creating widgets or charts impossible for those properties.

Allow browsing and installing plugins from the public port-experimental/port-plugins registry ( https://github.com/port-experimental/port-plugins ) inside Port.

Trigger a Claude agent with a prompt as part of any workflow.

We would like to see the ability to create custom logs at the node level. This could be be conditional logging depending on node outcome. This would also allow messages that make more sense to the user than generic error messages.

Add support for opening a self-service action form directly from a custom widget/plugin, without navigating to the Self-Service Actions tab

The GitHub Ocean integration should ingest membership data for GitHub Enterprise Teams ( ent:* slugs) in the same way it does for standard organization teams. Today, enterprise teams are discovered and synced as team entities in Port, but their member relationships are not populated. The enrichment flow relies on GraphQL organization.team(slug) , which returns null for enterprise-managed teams ( ent:* ), causing member enrichment to be skipped while the team entity itself is still created. As a result, enterprise teams appear in Port without their members, creating an inconsistency between enterprise-managed teams and standard organization teams. This feature request is to add support for ingesting and maintaining membership relationships for GitHub Enterprise Teams.