# Port Documentation > Port is an agentic SDLC platform: one governed layer for humans and AI agents to understand, decide, and act on engineering systems. API base URLs: EU https://api.port.io, US https://api.us.port.io. - [Port Documentation](/index.md) ## Getting started ### overview Set up your Port account, connect your first integration, and build a working software catalog in a few guided onboarding steps. - [Getting started](/getting-started/overview.md): Set up your Port account, connect your first integration, and build a working software catalog in a few guided onboarding steps. ### agentic-sdlc-pillars An overview of the five pillars that make up an agentic SDLC platform in Port - context lake, AI agents, governance, workflows, and human-in-the-loop. - [The pillars of an agentic SDLC platform](/getting-started/agentic-sdlc-pillars.md): An overview of the five pillars that make up an agentic SDLC platform in Port - context lake, AI agents, governance, workflows, and human-in-the-loop. ### build-more-workflows Explore more workflow examples and keep building on top of your context lake. - [Build more workflows](/getting-started/build-more-workflows.md): Explore more workflow examples and keep building on top of your context lake. ### build-your-first-workflow Build your first AI-powered workflow in minutes, using any use-case Port AI suggests for your context lake. - [Build your first workflow](/getting-started/build-your-first-workflow.md): Build your first AI-powered workflow in minutes, using any use-case Port AI suggests for your context lake. ### connect-your-git Connect your Git provider so Port can start populating your context lake with repositories and pull requests. - [Set up your Git provider](/getting-started/connect-your-git.md): Connect your Git provider so Port can start populating your context lake with repositories and pull requests. ### craft-an-initial-prompt Choose a use-case, craft an initial prompt, and let Port AI build the initial structure of your platform. - [Craft a prompt](/getting-started/craft-an-initial-prompt.md): Choose a use-case, craft an initial prompt, and let Port AI build the initial structure of your platform. ### docs-ai-assistant Use Port's AI assistant to ask documentation questions, generate resource definitions, debug JSON/YAML, and get help with blueprints and actions. - [Docs AI assistant](/getting-started/docs-ai-assistant.md): Use Port's AI assistant to ask documentation questions, generate resource definitions, debug JSON/YAML, and get help with blueprints and actions. ### invite-users Invite colleagues to your Port platform to collaborate on workflows and catalog management. - [Invite your team](/getting-started/invite-users.md): Invite colleagues to your Port platform to collaborate on workflows and catalog management. ### set-up-your-context-lake Connect additional tools and populate your context lake with services, users, and ownership data. - [Set up your context lake](/getting-started/set-up-your-context-lake.md): Connect additional tools and populate your context lake with services, users, and ownership data. ### view-dashboards Explore the dashboard Port auto-created for your use-case, now populated with real data from your tools. - [View your dashboards](/getting-started/view-dashboards.md): Explore the dashboard Port auto-created for your use-case, now populated with real data from your tools. ## context-lake ### business-context #### organization-hierarchy Model your organization hierarchy with team blueprints. Create views showing groups, teams, and services at each tier level. - [Visualize organization hierarchy](/context-lake/business-context/organization-hierarchy.md): Model your organization hierarchy with team blueprints. Create views showing groups, teams, and services at each tier level. #### overview Add business context to your Port catalog so agents and workflows can prioritize by cost, criticality, ownership, SLAs, and risk. - [Business context](/context-lake/business-context/overview.md): Add business context to your Port catalog so agents and workflows can prioritize by cost, criticality, ownership, SLAs, and risk. #### ownership Assign users and teams as owners of catalog entities. Sync ownership from integrations, configure the ownership property and $team meta-property, and visualize who owns what in your portal. - [Manage ownership in Port](/context-lake/business-context/ownership.md): Assign users and teams as owners of catalog entities. Sync ownership from integrations, configure the ownership property and $team meta-property, and visualize who owns what in your portal. ### consuming-the-lake #### govern-data-access ##### examples Examples of catalog RBAC configurations including making entities immutable, property-level permissions, and team ownership-based access control. - [Examples](/context-lake/consuming-the-lake/govern-data-access/examples.md): Examples of catalog RBAC configurations including making entities immutable, property-level permissions, and team ownership-based access control. ##### overview Set Port catalog RBAC so you control who reads, creates, updates, or deletes entities and properties by role, team, or policy. - [Govern data access](/context-lake/consuming-the-lake/govern-data-access/overview.md): Set Port catalog RBAC so you control who reads, creates, updates, or deletes entities and properties by role, team, or policy. #### other-consumption-methods ##### overview Use the Port n8n node and related methods so external automation can query your Context Lake without direct access to every tool. - [Other consumption methods](/context-lake/consuming-the-lake/other-consumption-methods/overview.md): Use the Port n8n node and related methods so external automation can query your Context Lake without direct access to every tool. ##### port-n8n-node Install and configure Port's custom n8n node to integrate Port AI agents and API into your n8n automation workflows. - [Port n8n node](/context-lake/consuming-the-lake/other-consumption-methods/port-n8n-node.md): Install and configure Port's custom n8n node to integrate Port AI agents and API into your n8n automation workflows. #### overview See how you consume Port's Context Lake: query entities, use Port MCP, apply catalog RBAC, and trigger external automation. - [Consumption methods](/context-lake/consuming-the-lake/overview.md): See how you consume Port's Context Lake: query entities, use Port MCP, apply catalog RBAC, and trigger external automation. #### port-mcp-server The Port MCP server does not use Port AI capabilities. You can install and use it without enabling Port AI features or accepting the Port AI Terms. - [Port MCP server](/context-lake/consuming-the-lake/port-mcp-server.md): The Port MCP server does not use Port AI capabilities. You can install and use it without enabling Port AI features or accepting the Port AI Terms. #### search-and-query ##### advanced Advanced search options including attach_title_to_relation and exclude_calculated_properties query parameters for customizing search results. - [Advanced](/context-lake/consuming-the-lake/search-and-query/advanced.md): Advanced search options including attach_title_to_relation and exclude_calculated_properties query parameters for customizing search results. ##### examples Search and query examples for catalog pages, dashboard widgets, automations, and dynamic action permissions with practical JSON rules. - [Examples](/context-lake/consuming-the-lake/search-and-query/examples.md): Search and query examples for catalog pages, dashboard widgets, automations, and dynamic action permissions with practical JSON rules. ##### operators - [Comparison operators](/context-lake/consuming-the-lake/search-and-query/operators/comparison-operators.md): Comparison operators for search rules including equals, contains, greater/less than, between, isEmpty, and property existence checks. - [Relation operators](/context-lake/consuming-the-lake/search-and-query/operators/relation-operators.md): Relation operators for searching entities by relationships including relatedTo, containsAny, and direction/depth controls for traversing relations. ##### overview Apply Port's search and query syntax to filter entities in pages, dashboards, scorecards, RBAC, actions, and API search endpoints. - [API access & search](/context-lake/consuming-the-lake/search-and-query/overview.md): Apply Port's search and query syntax to filter entities in pages, dashboards, scorecards, RBAC, actions, and API search endpoints. ##### structure-and-syntax Search query structure with combinators (and/or), rules, property operators, and meta-properties like $blueprint and $identifier. - [Structure & syntax](/context-lake/consuming-the-lake/search-and-query/structure-and-syntax.md): Search query structure with combinators (and/or), rules, property operators, and meta-properties like $blueprint and $identifier. ### data-model #### configure-data-model Learn how Port's data model uses blueprints, properties, and relations so you can define and manage your catalog schema. - [Data model](/context-lake/data-model/configure-data-model.md): Learn how Port's data model uses blueprints, properties, and relations so you can define and manage your catalog schema. #### define-your-ontology Learn how blueprint descriptions, relation titles, property types, and enum values turn a schema into a semantic knowledge graph that AI agents can reason over and act on. - [Define your ontology](/context-lake/data-model/define-your-ontology.md): Learn how blueprint descriptions, relation titles, property types, and enum values turn a schema into a semantic knowledge graph that AI agents can reason over and act on. #### iac ##### pulumi-managed-blueprint Comprehensive blueprint with properties, relations and mirror properties - [Pulumi-Managed Blueprint Example](/context-lake/data-model/iac/pulumi-managed-blueprint.md): Comprehensive blueprint with properties, relations and mirror properties ##### terraform-managed-blueprint Comprehensive blueprint with properties, relations and mirror properties - [Terraform-Managed Blueprint Example](/context-lake/data-model/iac/terraform-managed-blueprint.md): Comprehensive blueprint with properties, relations and mirror properties #### setup-blueprint ##### default-blueprints Reference for default Port blueprints including service, workload, environment, user, and team. Describes each blueprint's purpose and properties. - [Default blueprints](/context-lake/data-model/setup-blueprint/default-blueprints.md): Reference for default Port blueprints including service, workload, environment, user, and team. Describes each blueprint's purpose and properties. ##### overview Create Port blueprints to model your assets, then add properties and relations using Port AI, the UI, API, Terraform, or Pulumi. - [Set up blueprints](/context-lake/data-model/setup-blueprint/overview.md): Create Port blueprints to model your assets, then add properties and relations using Port AI, the UI, API, Terraform, or Pulumi. ##### properties - [Aggregation Property](/context-lake/data-model/setup-blueprint/properties/aggregation-property.md): Learn how to use aggregation properties to calculate metrics based on relations in your catalog, such as counting entities or averaging values. - [Array](/context-lake/data-model/setup-blueprint/properties/array.md): Array is a data type used to save lists of data - [Boolean](/context-lake/data-model/setup-blueprint/properties/boolean.md): Boolean is a primitive data type that has one of two possible values - true and false - [➕ Calculation Property](/context-lake/data-model/setup-blueprint/properties/calculation-property.md): Calculation property allows you to construct new data from existing properties of an entity - [Examples](/context-lake/data-model/setup-blueprint/properties/calculation-property/examples.md): Examples of calculation properties including math operations, string concatenation, conditional logic, and date formatting in Port blueprints. - [Datetime](/context-lake/data-model/setup-blueprint/properties/datetime.md): Datetime is a data type used to reference a date and time - [Email](/context-lake/data-model/setup-blueprint/properties/email.md): Email is a data type used to save Email addresses - [Embedded URL](/context-lake/data-model/setup-blueprint/properties/embedded-url.md): Learn how to use embedded URL properties to display external webpages like dashboards, diagrams, and architecture views within entity pages. - [Authentication](/context-lake/data-model/setup-blueprint/properties/embedded-url/authentication.md): Learn how to configure SSO authentication for embedded URL properties to display protected webpages within Port entity pages. - [Enum](/context-lake/data-model/setup-blueprint/properties/enum.md): Enum is a data type used to define a named set of constant values. - [Labeled URL](/context-lake/data-model/setup-blueprint/properties/labeled-url-object.md): Labeled URL is an object type used to store URLs with custom display labels - [Markdown](/context-lake/data-model/setup-blueprint/properties/markdown.md): Learn how to use the Markdown property type to display formatted Markdown content within entity pages in Port. - [Meta-Properties](/context-lake/data-model/setup-blueprint/properties/meta-properties.md): Reference for meta-properties that exist on every entity by default, including identifier, title, team, timestamps, and created/updated by fields. - [Mirror Property](/context-lake/data-model/setup-blueprint/properties/mirror-property.md): Mirror Property allows you to map data from related entities to your entity - [Number](/context-lake/data-model/setup-blueprint/properties/number.md): Number is a primitive data type used to save numeric data - [Object](/context-lake/data-model/setup-blueprint/properties/object.md): Object is a data type used to save object definitions in JSON - [Properties](/context-lake/data-model/setup-blueprint/properties/overview.md): Configure Port blueprint properties from the Data model page or catalog so you can create, edit, and hide the fields your entities store. - [Owning Teams](/context-lake/data-model/setup-blueprint/properties/owning-teams.md): Owning Teams defines which team owns a blueprint's entities. It can be added once per blueprint, creates a relation to the Team blueprint, and sets the blueprint's ownership. - [Proto](/context-lake/data-model/setup-blueprint/properties/proto.md): Proto is a data type used to save proto definitions in Port - [String](/context-lake/data-model/setup-blueprint/properties/string.md): Configure string properties on Port blueprints, including enum values, formats, and validation rules. String is a primitive data type used to save text data. - [Swagger UI](/context-lake/data-model/setup-blueprint/properties/swagger.md): Learn how to use the Swagger UI property to display OpenAPI and AsyncAPI specification files within entity pages in Port. - [Team](/context-lake/data-model/setup-blueprint/properties/team.md): Team is a data type used to reference teams that exist in Port - [Timer](/context-lake/data-model/setup-blueprint/properties/timer.md): Timer is a data type used to define an expiration date/lifespan of a specific entity - [URL](/context-lake/data-model/setup-blueprint/properties/url.md): URL is a data type used to save links to websites - [User](/context-lake/data-model/setup-blueprint/properties/user.md): User is a data type used to reference users that exist in Port - [Yaml](/context-lake/data-model/setup-blueprint/properties/yaml.md): Yaml is a data type used to save object definitions in YAML ##### relate-blueprints Learn how to create relations between blueprints to define logical connections between assets in your software catalog. - [Relate Blueprints](/context-lake/data-model/setup-blueprint/relate-blueprints.md): Learn how to create relations between blueprints to define logical connections between assets in your software catalog. ### extend-the-context-lake You can extend the Context Lake beyond native integrations by connecting external MCP servers and publishing skills. - [Extend the context lake](/context-lake/extend-the-context-lake.md): You can extend the Context Lake beyond native integrations by connecting external MCP servers and publishing skills. ### ingestion #### catalog-auto-discovery Learn how to use AI-powered auto discovery to identify and create missing entities in your catalog based on related data from multiple sources. - [Auto discovery](/context-lake/ingestion/catalog-auto-discovery.md): Learn how to use AI-powered auto discovery to identify and create missing entities in your catalog based on related data from multiple sources. #### configure-mapping ##### common-jq-use-cases Common JQ patterns for integration mappings, self-service action backends, and filters. - [Common jq use-cases](/context-lake/ingestion/configure-mapping/common-jq-use-cases.md): Common JQ patterns for integration mappings, self-service action backends, and filters. ##### configuration-methods Configure an integration's mapping using either the visual form editor or the code-based YAML editor. - [Configuration methods](/context-lake/ingestion/configure-mapping/configuration-methods.md): Configure an integration's mapping using either the visual form editor or the code-based YAML editor. ##### entity-cleanup When you remove a resource type from your integration mapping or decommission an integration, the associated entities in Port are not automatically deleted. This documentation explains how to properly clean up stale entities to keep your software catalog accurate and up to date. - [Clean up stale entities](/context-lake/ingestion/configure-mapping/entity-cleanup.md): When you remove a resource type from your integration mapping or decommission an integration, the associated entities in Port are not automatically deleted. This documentation explains how to properly clean up stale entities to keep your software catalog accurate and up to date. ##### overview Edit Port integration mapping with JQ to select source data, map properties and relations, and tune sync in YAML or forms. - [Configure mapping](/context-lake/ingestion/configure-mapping/overview.md): Edit Port integration mapping with JQ to select source data, map properties and relations, and tune sync in YAML or forms. #### ingest-data-into-port ##### api - [Advanced](/context-lake/ingestion/ingest-data-into-port/api/advanced.md): Advanced API query parameters including delete_dependents for cascading deletes and create_missing_related_entities for automatic entity creation. - [CI/CD](/context-lake/ingestion/ingest-data-into-port/api/ci-cd.md): Overview of CI/CD integrations for keeping your software catalog up to date with build versions, job statuses, and other CI/CD data. - [Azure Pipelines](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/azure-pipelines.md): Learn how to create, update, and query Port entities directly from Azure Pipelines using Port's API. - [Examples](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/azure-pipelines/examples.md): Examples of creating and updating Port entities from Azure Pipelines, including CI job tracking and Docker image reporting. - [CircleCI workflows](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/circleci-workflow.md): Learn how to create, update, and query Port entities directly from CircleCI workflows using Port's API. - [Examples](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/circleci-workflow/examples.md): Examples of creating and updating Port entities from CircleCI workflows, including CI job tracking and Docker image reporting. - [Codefresh Workflow Template](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/codefresh-workflow-template.md): Learn how to use Port's Codefresh workflow template to create, update, and query entities directly from Codefresh pipelines. - [Examples](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/codefresh-workflow-template/examples.md): Basic create/update example - [GitHub Workflow](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/github-workflow.md): Learn how to use Port's GitHub action to create, update, and query entities directly from GitHub workflows. - [Examples](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/github-workflow/examples.md): Examples of using Port's GitHub action to create entities, import dependencies, and report CI job status from GitHub workflows. - [Gitlab CI Pipelines](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/gitlab-pipelines.md): Learn how to create, update, and query Port entities directly from GitLab CI pipeline jobs using Port's API. - [Examples](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/gitlab-pipelines/examples.md): Examples of creating and updating Port entities from GitLab CI pipelines, including CI job tracking and Docker image reporting. - [Jenkins Deployment](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/jenkins-deployment.md): Learn how to create, update, and query Port entities directly from Jenkins pipelines using Port's API. - [Examples](/context-lake/ingestion/ingest-data-into-port/api/ci-cd/jenkins-deployment/examples.md): Examples of creating and updating Port entities from Jenkins pipelines, including CI job tracking and Docker image reporting. - [Ingest via API](/context-lake/ingestion/ingest-data-into-port/api/ingest-via-api-overview.md): Authenticate with Port's REST API to ingest entities and update your catalog from scripts, CI pipelines, or custom systems. ##### custom-integration - [Configuration](/context-lake/ingestion/ingest-data-into-port/custom-integration/ocean-custom-integration/configuration.md): Prerequisites, resource mapping, and advanced configuration for the Ocean custom integration - [Hosted by Port](/context-lake/ingestion/ingest-data-into-port/custom-integration/ocean-custom-integration/installation-types/hosted-by-port.md): Install the Ocean custom integration hosted by Port - [Build your integration](/context-lake/ingestion/ingest-data-into-port/custom-integration/ocean-custom-integration/installation-types/self-hosted/build-your-integration.md): Interactive guide to configure and install your integration - [Custom authentication](/context-lake/ingestion/ingest-data-into-port/custom-integration/ocean-custom-integration/installation-types/self-hosted/custom-authentication.md): Configure OAuth2, JWT, and other dynamic token-based authentication flows - [Setup](/context-lake/ingestion/ingest-data-into-port/custom-integration/ocean-custom-integration/installation-types/self-hosted/setup.md): Install the Ocean custom integration in your own infrastructure - [Overview](/context-lake/ingestion/ingest-data-into-port/custom-integration/ocean-custom-integration/overview.md): Connect any REST API to Port with Ocean custom integration so you can map endpoints to blueprints and ingest with config only. - [Standalone Ocean integration](/context-lake/ingestion/ingest-data-into-port/custom-integration/ocean-custom-integration/standalone.md): If the pre-built Ocean custom integration doesn't meet your needs, you can build a standalone Ocean integration from scratch using the Ocean framework. - [Create a custom integration](/context-lake/ingestion/ingest-data-into-port/custom-integration/overview.md): Build a custom Port integration when no native option exists. Define blueprints, then ingest via Ocean, webhooks, the API, or IaC. ##### native-integrations - [Available integrations](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations.md): Browse all available Port native integrations. Each card links to the integration's documentation. - [Claude AI metrics](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/ai-usage-metrics/claude.md): Ingest Claude AI (Enterprise) and Claude Platform usage, analytics, and skill adoption into Port to track AI tool adoption across your organization. - [Cursor metrics](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/ai-usage-metrics/cursor.md): Learn how to ingest Cursor team, model, and skill usage into Port to track AI adoption and cost patterns across your engineering organization using the Ocean custom integration framework. - [GitHub Copilot metrics](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/ai-usage-metrics/github-copilot.md): Ingest GitHub Copilot usage and metrics into Port to track AI coding tool adoption across your engineering organization. - [OpenAI metrics](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/ai-usage-metrics/openai.md): Learn how to ingest OpenAI usage metrics, costs, and model information into Port using the Ocean custom integration framework. - [APM & alerting](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting.md): Overview of APM and alerting integrations for syncing monitoring data from tools like Datadog, Prometheus, and Azure Monitor to Port. - [Azure Monitor](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting/azure-monitor.md): Learn how to ingest Azure Monitor alerts, activity logs, and metrics into Port using the Ocean custom integration framework. - [Datadog](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting/datadog.md): Sync Datadog monitors, services, SLOs, and host data into Port's software catalog, and use it across scorecards, dashboards, and automations. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting/datadog/examples.md): Mapping examples for Datadog resources including monitors, services, SLOs, and dashboards using the Datadog integration. - [Dynatrace](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting/dynatrace.md): Sync Dynatrace monitoring data, problems, and services into Port's software catalog. - [New Relic](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting/newrelic.md): Sync New Relic monitoring data, alerts, and services into Port's software catalog. - [Prometheus](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting/prometheus.md): Learn how to ingest Prometheus alerts, rules, and scrape targets into Port using the Ocean custom integration framework. - [Sentry](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/apm-alerting/sentry.md): Sync Sentry projects, issues, and error tracking data into Port's software catalog. - [Argo CD](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/argocd.md): Sync Argo CD applications, deployments, and clusters into Port's software catalog. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/argocd/example.md): Mapping examples for ArgoCD resources including clusters, projects, applications, and deployment history. - [n8n](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/automation-platforms/n8n.md): Learn how to ingest n8n users, projects, and workflows into Port using the Ocean custom integration framework. - [Zapier](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/automation-platforms/zapier.md): Learn how to ingest Zapier apps and zaps into Port using the Ocean custom integration framework. - [Jenkins](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cicd/jenkins.md): Sync Jenkins jobs, builds, and pipelines into Port's software catalog. - [Octopus Deploy Integration](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cicd/octopus-deploy.md): Sync Octopus Deploy projects, releases, and deployments into Port's software catalog. - [Ingest additional resources](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cicd/octopus-deploy/mapping-extra-resources.md): Learn how to map additional Octopus Deploy resources like runbooks, tasks, teams, environments, and workers into Port. - [Cloud cost](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-cost.md): Overview of cloud cost integrations for syncing cost and usage data from tools like Kubecost and OpenCost to Port. - [Kubecost](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-cost/kubecost.md): Sync Kubecost cost allocation and Kubernetes spend data into Port's software catalog. - [Advanced configuration for Kubecost objects](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-cost/kubecost/advanced.md): Advanced configuration options for Kubecost integration including allocation queries, filters, and cloud cost aggregation parameters. - [OpenCost](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-cost/opencost.md): Sync OpenCost Kubernetes cost and resource spend data into Port's software catalog. - [Cloud providers](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers.md): Overview of cloud provider integrations for syncing AWS, Azure, and GCP resources to your Port software catalog. - [Installation](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/installation.md): Install the Port AWS integration using Port-hosted or self-hosted deployment. Covers single account and multi-account setups via ECS, EC2, EKS (IRSA), or one-off Docker runs. - [AWS v3](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/Overview.md): Learn how to sync AWS resources like EC2, S3, Lambda, EKS, and more to Port using the AWS v3 integration with flexible deployment options. - [AWS resource and property reference](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference.md): Reference guide for AWS resource types, actions, and properties supported by the AWS v3 integration including EC2, S3, ECS, Lambda, and more. - [Amazon DynamoDB](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-dynamodb.md): Reference for Amazon DynamoDB resources including tables with supported actions, permissions, and mapping configurations. - [Amazon Elastic Compute Cloud (EC2)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-elastic-compute-cloud.md): Reference for Amazon EC2 resources including instances and volumes with supported actions, permissions, and mapping configurations. - [Amazon Elastic Container Registry (ECR)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-elastic-container-registry.md): Reference for Amazon ECR repository resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon Elastic Container Service (ECS)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-elastic-container-service.md): Reference for Amazon ECS resources including clusters, services, and task definitions with supported actions and mapping configurations. - [Amazon Elastic Kubernetes Service (EKS)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-elastic-kubernetes-service.md): Reference for Amazon EKS cluster resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon ElastiCache](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-elasticache.md): Reference for Amazon ElastiCache resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon Managed Streaming for Apache Kafka (MSK)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-managed-streaming-for-apache-kafka.md): Reference for Amazon MSK cluster resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon MemoryDB](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-memorydb.md): Reference for Amazon MemoryDB user resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon Relational Database Service (RDS)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-relational-database-service.md): Reference for Amazon RDS DB instance resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon Simple Email Service (SES)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-simple-email-service.md): Reference for Amazon SES resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon Simple Queue Service (SQS)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-simple-queue-service.md): Reference for Amazon SQS resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [Amazon Simple Storage Service (S3)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/amazon-simple-storage-service.md): Reference for Amazon S3 bucket resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [AWS Account](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/aws-account.md): Reference for AWS Account information resources for resyncing account data without AWS Organizations permissions. - [AWS CodeBuild](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/aws-codebuild.md): Reference for AWS CodeBuild resources including projects and build runs with supported actions, permissions, and mapping configurations. - [AWS CodeDeploy](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/aws-codedeploy.md): Reference for AWS CodeDeploy resources including applications, deployment groups, deployments, and deployment targets with supported actions and mapping configurations. - [AWS CodePipeline](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/aws-codepipeline.md): Reference for AWS CodePipeline resources including pipelines, stages, actions, and executions with supported actions, permissions, and mapping configurations. - [AWS Lambda](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/aws-lambda.md): Reference for AWS Lambda resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [AWS Organizations](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws-v3/resource-and-property-reference/aws-organizations.md): Reference for AWS Organizations account resources including supported actions, permissions, and mapping configurations for the AWS v3 integration. - [AWS on-premise](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws.md): Sync AWS resources into Port's software catalog using the self-hosted AWS integration. - [AWS exporter](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/aws-exporter.md): Deprecated AWS exporter documentation - learn about the legacy serverless application for syncing AWS resources to Port. - [Event-based updates](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/aws-exporter/event-based-updates.md): Learn how to configure real-time event-based updates for the deprecated AWS exporter using EventBridge and CloudTrail. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/aws-exporter/examples.md): Examples of mapping AWS resources like ECS clusters, S3 buckets, Lambda functions, and more using the deprecated AWS exporter. - [Connect ECR repository to a service](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/aws-exporter/examples/connect-ecr-repo-to-service-using-tags.md): Learn how to connect AWS ECR repositories to existing services in Port using resource tags for the deprecated AWS exporter. - [Installation](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/aws-exporter/installation.md): Installation guide for the deprecated AWS exporter using Terraform or manual SAM deployment methods. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/examples.md): Base mapping examples for AWS resources including accounts and generic cloud resources using the AWS Ocean integration. - [Mapping extra resources](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/examples/mapping_extra_resources.md): Learn how to map additional AWS resources to Port including ECS, Lambda, SQS, DynamoDB, and other Cloud Control API supported resources. - [Live events setup](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/live-events.md): Learn how to set up real-time event processing for AWS resources using EventBridge and CloudTrail to keep your Port catalog updated. - [Multi account support](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/aws/multi_account.md): Learn how to configure the AWS Ocean integration to ingest resources from multiple AWS accounts using cross-account IAM roles. - [Azure](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/azure.md): Sync Azure cloud resources into Port's software catalog. - [Azure Resource Graph (Beta)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/azure/azure-resource-graph.md): Learn how to sync Azure resources to Port using the Azure Resource Graph integration for high-volume, multi-subscription data ingestion. - [Resource Templates](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/azure/resource_templates.md): Base mapping templates for Azure resources including subscriptions, resource groups, and generic cloud resources using the Azure integration. - [Advanced Templates](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/azure/resource_templates/advanced.md): Advanced mapping templates for Azure resources including storage accounts, AKS clusters, virtual machines, and Service Bus resources. - [Mapping Extra Resources](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/azure/resource_templates/mapping_extra_resources.md): Learn how to map additional Azure resources to Port that are not covered in the standard templates by using the Azure REST API reference. - [GCP](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/gcp.md): Sync Google Cloud (GCP) resources into Port's software catalog. - [Cloud Function Sync protocol](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/gcp/cloud-function-sync.md): Sync resources from any HTTP endpoint using the GCP Cloud Function Sync protocol - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/gcp/examples.md): Base mapping examples for GCP resources including projects and generic cloud resources using the GCP integration. - [Map Extra Resources](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/cloud-providers/gcp/examples/mapping_extra_resources.md): Learn how to map additional GCP resources to Port including compute instances, BigQuery datasets, and other Asset Inventory supported resources. - [Code quality & security](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security.md): Overview of code quality and security integrations for syncing data from tools like SonarQube, Snyk, Wiz, Mend.io, and Checkmarx to Port. - [Aikido](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/aikido.md): Sync Aikido security findings and vulnerabilities into Port's software catalog. - [ArmorCode](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/armorcode.md): Sync ArmorCode security findings and ASPM data into Port's software catalog. - [BrowserStack](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/browserstack.md): Learn how to ingest BrowserStack Automate test data including plans, projects, and builds into Port using the Ocean custom integration. - [Checkmarx One](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/checkmarx.md): Sync Checkmarx One scan results and security findings into Port's software catalog. - [Resource mapping examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/checkmarx/examples.md): Mapping examples for Checkmarx resources including projects, scans, SAST, SCA, KICS, and API security findings with blueprints and configurations. - [Mend.io](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/mend.md): Sync Mend.io projects and SCA security findings into Port's software catalog. - [Snyk](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/snyk.md): Sync Snyk vulnerabilities, projects, and security findings into Port's software catalog. - [SonarQube](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/sonarqube.md): Sync SonarQube code quality metrics, issues, and projects into Port's software catalog. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/sonarqube/examples.md): Mapping examples for SonarQube resources including projects and analysis results with blueprints and configurations. - [Wiz](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/wiz.md): Sync Wiz cloud security issues and findings into Port's software catalog. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/code-quality-security/wiz/examples.md): Mapping examples for Wiz resources including projects, cloud resources, issues, and control findings with blueprints and configurations. - [Kafka](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/event-processing/kafka.md): Sync Kafka clusters, topics, and brokers into Port's software catalog. - [LaunchDarkly](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/feature-management/launchdarkly.md): LaunchDarkly integration in Port - [Git](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git.md): Overview of Git provider integrations for syncing repositories, pull requests, and other data from GitHub, GitLab, Bitbucket, and Azure DevOps. - [Azure DevOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/azure-devops.md): Sync Azure DevOps repositories, pull requests, and pipelines into Port's software catalog. - [Advanced](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/azure-devops/advanced.md): Advanced Azure DevOps integration configuration including createMissingRelatedEntities, deleteDependentEntities, and custom settings. - [Capabilities](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/azure-devops/capabilities.md): Azure DevOps integration capabilities including file content enrichment for READMEs, CODEOWNERS, and documentation in entity properties. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/azure-devops/examples.md): Azure DevOps integration examples for repositories, pull requests, pipelines, teams, and members with blueprint definitions and mapping configurations. - [GitOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/azure-devops/gitops.md): Manage Port entities as code using port.yml files in Azure DevOps repositories. Define entities declaratively and sync via push events. - [Mapping Extensions](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/azure-devops/mapping_extensions.md): Extend Azure DevOps mapping with additional data sources beyond JQ. Includes file content enrichment and custom resource extraction. - [Bitbucket app (deprecated)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-app.md): Deprecated Bitbucket Cloud app integration - use the newer Bitbucket Cloud integration instead for syncing repositories and pull requests. - [Advanced](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-app/advanced.md): Advanced Bitbucket App configuration including createMissingRelatedEntities and deleteDependentEntities flags. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-app/examples.md): Bitbucket App integration examples for repositories, file contents, and pull requests with blueprint definitions and mapping configurations. - [GitOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-app/gitops.md): Manage Port entities as code using port.yml files with Bitbucket App. Define entities declaratively and sync via push events. - [Bitbucket Cloud](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-cloud.md): Sync Bitbucket Cloud repositories, pull requests, and projects into Port's software catalog. - [Advanced](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-cloud/advanced.md): Advanced Bitbucket Cloud configuration including createMissingRelatedEntities and deleteDependentEntities flags. - [Capabilities](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-cloud/capabilities.md): Bitbucket Cloud integration capabilities including repository, pull request, and file ingestion with automatic blueprint creation. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-cloud/examples.md): Bitbucket Cloud integration examples for repositories, pull requests, projects, and files with blueprint definitions and mapping configurations. - [GitOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-cloud/gitops.md): Manage Port entities as code using port.yml files in Bitbucket Cloud repositories. Define entities declaratively and sync automatically. - [Bitbucket (self-hosted)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-server.md): Sync Bitbucket (self-hosted) repositories, pull requests, and projects into Port's software catalog. - [GitOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/bitbucket/bitbucket-server/gitops.md): Manage Port entities as code using port.yml files in Bitbucket Server repositories. Define entities declaratively and sync via webhooks. - [GitHub (Ocean)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/github-ocean.md): Sync GitHub repositories, pull requests, workflows, and deployments into Port's software catalog using the GitHub Ocean integration. - [Capabilities](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/github-ocean/capabilities.md): Advanced capabilities of the GitHub Ocean integration including parallel processing, file content ingestion, and custom query filtering. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/github-ocean/examples.md): Mapping examples for GitHub Ocean resources including repositories, pull requests, issues, deployments, releases, and team members. - [GitOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/github-ocean/gitops.md): Manage Port entities as code using port.yml files in GitHub repositories. Define entities declaratively and sync via push events. - [Key changes](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/github-ocean/migration/key-changes.md): Overview of key changes between legacy GitHub app and GitHub Ocean including multi-org support, authentication, and mapping syntax updates. - [Migration steps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/github-ocean/migration/migration-steps.md): Step-by-step guide for migrating from the legacy GitHub app to GitHub Ocean, including entity ownership transfer and mapping updates. - [GitLab v2](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab-v2.md): Sync GitLab projects, merge requests, and pipelines into Port's software catalog using the v2 integration. - [Advanced](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab-v2/advanced.md): Advanced GitLab v2 configuration including createMissingRelatedEntities, deleteDependentEntities, and custom integration flags. - [Capabilities](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab-v2/capabilities.md): GitLab v2 integration capabilities including file content enrichment for READMEs, CODEOWNERS, and documentation in entity properties. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab-v2/examples.md): Mapping examples for GitLab v2 resources including groups, projects, issues, merge requests, pipelines, and releases with blueprints and configurations. - [GitOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab-v2/gitops.md): Manage Port entities as code using port.yml files in GitLab v2 repositories. Define entities declaratively and sync via push events. - [Mapping extensions](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab-v2/mapping_extensions.md): Extend GitLab v2 mapping with additional data sources beyond JQ. Includes file content enrichment and external API lookups. - [Migration guide to the v2 integration](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab-v2/migration.md): Migrate from GitLab v1 to v2 integration. Replace group tokens with service account authentication and update mapping configurations. - [GitLab](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab.md): Sync GitLab projects, merge requests, and pipelines into Port's software catalog. - [Advanced](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab/advanced.md): Advanced configuration options for the GitLab integration including delete dependents and entity creation flags. - [Capabilities](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab/capabilities.md): Advanced capabilities of the GitLab integration including file ingestion, folder mapping, and live events configuration. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab/examples.md): Mapping examples for GitLab resources including projects, merge requests, pipelines, issues, and groups with blueprints and configurations. - [GitOps](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab/gitops.md): Manage Port entities as code using port.yml files in GitLab repositories. Define entities declaratively and sync via push events. - [Mapping Extensions](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitlab/mapping_extensions.md): Extend GitLab mapping with additional data sources beyond JQ. Includes file content enrichment and custom resource extraction. - [GitOps using Port CRDs](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/gitops-using-port-crd.md): Learn how to use GitOps with Port's Kubernetes CRDs to export custom entities from your K8s clusters to the catalog. - [Working with monorepos](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/git/working-with-monorepos.md): Learn how to configure Git integrations to create separate entities for each microservice in a monorepo. - [Microsoft Entra ID](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/identity-providers/azure-ad.md): Learn how to ingest Microsoft Entra ID (Azure AD) users, groups, applications, and service principals into Port. - [Okta](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/identity-providers/okta.md): Sync Okta users, groups, and applications into Port's software catalog. - [Incident management](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management.md): Overview of incident management integrations for syncing data from tools like PagerDuty, OpsGenie, and Incident.io to Port. - [FireHydrant](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/firehydrant.md): Sync FireHydrant incidents, services, and on-call data into Port's software catalog. - [Incident.io](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/incident-io.md): Learn how to ingest Incident.io incidents, alerts, schedules, and teams into Port using the Ocean custom integration framework. - [Jira Service Management (JSM)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/jira-service-management.md): Learn how to ingest Jira Service Management service desks, customer requests, and organizations into Port using the Ocean custom integration. - [Opsgenie](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/opsgenie.md): Sync Opsgenie alerts, incidents, services, and on-call schedules into Port's software catalog. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/opsgenie/examples.md): Mapping examples for OpsGenie resources including users, teams, services, alerts, and incidents with blueprints and configurations. - [PagerDuty](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/pagerduty.md): Sync PagerDuty services, incidents, and on-call schedules into Port's software catalog. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/pagerduty/examples.md): Mapping examples for PagerDuty resources including users, teams, services, incidents, and schedules with blueprints and configurations. - [Rootly](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/rootly.md): Learn how to ingest Rootly incidents, services, teams, and on-call data into Port using the Ocean custom integration framework. - [ServiceNow](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/servicenow.md): Sync ServiceNow incidents, services, and CMDB data into Port's software catalog. - [Statuspage](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/statuspage.md): Sync Statuspage pages, components, and incidents into Port's software catalog. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/incident-management/statuspage/examples.md): Mapping examples for Statuspage resources including status pages, components, incidents, and maintenance windows with blueprints and configurations. - [Komodor](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/komodor.md): Sync Komodor Kubernetes services, deployments, and health data into Port's software catalog. - [Kubernetes](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes.md): Sync Kubernetes workloads, namespaces, and resources into Port's software catalog. - [Advanced](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/advanced.md): Advanced configuration options for the Kubernetes exporter including resync intervals, state keys, and delete behavior parameters. - [Basic example](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/basic-example.md): Basic Example - [Custom CRDs](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/custom-crds.md): Learn how to export and map custom Kubernetes CRDs like ArgoCD resources to Port using the K8s exporter. - [Port Entity CRD](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/port-crd.md): Learn how to use Port's Kubernetes Custom Resource Definitions to define and sync entities from K8s cluster manifests to your catalog. - [Templates](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates.md): Pre-built configuration templates for common Kubernetes exporter use cases and third-party tools like ArgoCD and Istio. - [FluxCD](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates/fluxcd.md): FluxCD quickstart - [Kubernetes (advanced)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates/full-kubernetes-exporter.md): Advanced Kubernetes installation - [Istio](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates/istio.md): Istio quickstart - [Knative](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates/knative.md): Knative quickstart - [Kyverno](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates/kyverno.md): Kyverno quickstart - [Red Hat Openshift](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates/openshift.md): Openshift quickstart - [Trivy Operator](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/kubernetes-stack/kubernetes/templates/trivy.md): Trivy quickstart - [Amplication](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/other/amplication.md): Sync Amplication services and generated resources into Port's software catalog. - [Backstage](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/other/backstage.md): Ingest Backstage entities into your context lake so that agents, workflows, and your team members can access and act on them. - [Slack](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/other/slack.md): Learn how to ingest Slack users, channels, and user groups into Port using the Ocean custom integration framework. - [Project management](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/project-management.md): Overview of project management integrations for syncing data from tools like Jira, Linear, and other project tracking systems to Port. - [Jira Server (self-hosted)](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/project-management/jira-server.md): Sync Jira Server (self-hosted) projects and issues into Port's software catalog. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/project-management/jira-server/examples.md): Mapping examples for Jira Server resources including projects, users, and issues with default blueprints and configurations. - [Jira](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/project-management/jira.md): Sync Jira projects, issues, and teams into Port's software catalog. - [Capabilities](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/project-management/jira/capabilities.md): Advanced capabilities of the Jira integration including JQL filtering, field selection, live events, and sprints ingestion. - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/project-management/jira/examples.md): Mapping examples for Jira Cloud resources including issues, epics, sprints, boards, teams, and components with blueprints and configurations. - [Linear](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/project-management/linear.md): Sync Linear teams, issues, labels, and documents into Port's software catalog. - [Terraform Cloud & Terraform Enterprise](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/terraform-cloud.md): Terraform integration in Port - [Examples](/context-lake/ingestion/ingest-data-into-port/native-integrations/available-integrations/terraform-cloud/examples.md): Mapping examples for Terraform Cloud resources including organizations, workspaces, runs, and state versions with blueprints and configurations. - [Install a native integration](/context-lake/ingestion/ingest-data-into-port/native-integrations/overview.md): Install Port native integrations to sync GitHub, Kubernetes, Jira, and more into your catalog with hosted or self-hosted options. - [Full resync](/context-lake/ingestion/ingest-data-into-port/native-integrations/sync-mechanisms/full-resync.md): How Port full resync fetches, maps, and ingests integration data, including reconciliation and monitoring sync status. - [Incremental sync](/context-lake/ingestion/ingest-data-into-port/native-integrations/sync-mechanisms/incremental-sync.md): How Port incremental sync fetches only created or updated records between full resyncs. - [Live events](/context-lake/ingestion/ingest-data-into-port/native-integrations/sync-mechanisms/live-events.md): How Port live events process webhook and watch API changes in real time, including scalable self-hosted infrastructure with Redis Streams and ocean-gateway. ##### other - [Integrate assets using GitOps](/context-lake/ingestion/ingest-data-into-port/other/gitops.md): Overview of GitOps integration options for managing Port entities using your Git repositories as the source of truth, including how to build a custom GitOps integration using Port's API. - [IaC](/context-lake/ingestion/ingest-data-into-port/other/iac.md): Overview of Infrastructure-as-Code methods for ingesting data and defining your software catalog alongside IaC configurations using Terraform or Pulumi. - [Pulumi](/context-lake/ingestion/ingest-data-into-port/other/iac/pulumi.md): Learn how to use Port's Pulumi provider to manage blueprints and entities as infrastructure-as-code in Python, TypeScript, JavaScript, or Go. - [Terraform](/context-lake/ingestion/ingest-data-into-port/other/iac/terraform.md): Learn how to use Port's Terraform provider to manage blueprints, entities, and other Port resources as infrastructure-as-code. - [Manual entity management](/context-lake/ingestion/ingest-data-into-port/other/manual-entity-management.md): Not every catalog entity has a single clean source of truth. Manual entity management helps you fill gaps, correct edge cases, and enrich data that automation cannot reliably provide. - [Migrate Blueprint Data](/context-lake/ingestion/ingest-data-into-port/other/migrate-data.md): Learn how to migrate entity data between blueprints when evolving your software catalog structure, including property transformations and relation updates. - [Other ingestion methods](/context-lake/ingestion/ingest-data-into-port/other/other-ingestion-methods-overview.md): Explore Port's other ingestion options: IaC, GitOps, S3 buckets, Port MCP, and manual updates when continuous sync is not ideal. - [Port MCP](/context-lake/ingestion/ingest-data-into-port/other/port-mcp.md): You can ingest entities into your catalog using Port MCP tools. This is useful when an agent or an IDE workflow needs to create or update entities as part of a multi-step SDLC automation. - [S3 Bucket](/context-lake/ingestion/ingest-data-into-port/other/s3-integrations.md): Learn how to ingest data from external sources into Port using Airbyte or Fivetran with S3 as an intermediate storage layer. ##### webhook - [Examples](/context-lake/ingestion/ingest-data-into-port/webhook/examples.md): Examples of using Port's webhook integration to ingest resources from various tools like Jira, OpsGenie, SonarQube, and Sentry. - [Codecov](/context-lake/ingestion/ingest-data-into-port/webhook/examples/codecov.md): Ingest CodeCov coverage into your catalog - [Falco Sidekick](/context-lake/ingestion/ingest-data-into-port/webhook/examples/falco.md): Ingest Falco alerts into your catalog - [Grafana](/context-lake/ingestion/ingest-data-into-port/webhook/examples/grafana.md): Ingest Grafana alerts into your catalog - [JFrog](/context-lake/ingestion/ingest-data-into-port/webhook/examples/jfrog.md): Ingest JFrog artifacts, Docker tags and builds into your catalog - [Prometheus](/context-lake/ingestion/ingest-data-into-port/webhook/examples/prometheus.md): Ingest Prometheus alerts into your catalog - [Split](/context-lake/ingestion/ingest-data-into-port/webhook/examples/split.md): Ingest Split IO Impressions into your catalog - [StackHawk](/context-lake/ingestion/ingest-data-into-port/webhook/examples/stackhawk.md): Ingest StackHawk application vulnerabilities into Port - [Ingest via Webhooks](/context-lake/ingestion/ingest-data-into-port/webhook/ingest-via-webhooks-overview.md): Use Port's generic webhook to ingest events from any service, map payloads with JQ, and create, update, or delete entities. #### integrations-vs-mcp Port gives you two ways to connect external tools: integrations and MCP connectors. They solve different problems and are designed to complement each other — in many cases, you can benefit from both connected for the same tool. - [Integrations vs. MCP connectors](/context-lake/ingestion/integrations-vs-mcp.md): Port gives you two ways to connect external tools: integrations and MCP connectors. They solve different problems and are designed to complement each other — in many cases, you can benefit from both connected for the same tool. #### overview Choose how you ingest into Port's Context Lake: native integrations, MCP connectors, APIs, webhooks, or custom integrations. - [Overview](/context-lake/ingestion/overview.md): Choose how you ingest into Port's Context Lake: native integrations, MCP connectors, APIs, webhooks, or custom integrations. ### overview See how Port's context lake unifies data from your engineering tools into one queryable layer that humans and AI agents can use. - [Context Lake](/context-lake/overview.md): See how Port's context lake unifies data from your engineering tools into one queryable layer that humans and AI agents can use. ## Workflows ### overview Build Port workflows for humans, automations, and AI agents. Trigger runs from forms, catalog events, schedules, or Port MCP. - [Workflows & tools](/workflows/overview.md): Build Port workflows for humans, automations, and AI agents. Trigger runs from forms, catalog events, schedules, or Port MCP. ### build-workflows #### action-nodes ##### ai Invoke Port AI or AI agents directly from workflows to perform intelligent operations and automated decision-making. - [AI](/workflows/build-workflows/action-nodes/ai.md): Invoke Port AI or AI agents directly from workflows to perform intelligent operations and automated decision-making. ##### configuration-and-outputs Learn common action node configuration fields, outputs, and how to chain action nodes together in workflows. - [Configuration and outputs](/workflows/build-workflows/action-nodes/configuration-and-outputs.md): Learn common action node configuration fields, outputs, and how to chain action nodes together in workflows. ##### integration-actions - [Azure DevOps Pipelines](/workflows/build-workflows/action-nodes/integration-actions/azure-devops.md): Trigger Azure DevOps pipelines from Port workflows using your installed Azure DevOps integration. - [Claude managed agents integration action](/workflows/build-workflows/action-nodes/integration-actions/claude-managed-agents.md): The Claude managed agents integration action allows workflows to create new agents or trigger agent sessions directly using your installed Claude Managed Agents integration. - [Cursor cloud agents](/workflows/build-workflows/action-nodes/integration-actions/cursor-cloud-agents.md): The Cursor cloud agents integration action allows workflows to launch new Cursor cloud agents or send follow-up prompts to existing ones directly using your installed Cursor Cloud Agents integration. - [GitHub integration action](/workflows/build-workflows/action-nodes/integration-actions/github.md): Trigger GitHub Actions workflows directly from Port workflows using your installed GitHub integration. - [GitLab integration actions](/workflows/build-workflows/action-nodes/integration-actions/gitlab.md): Trigger GitLab CI/CD pipelines and create merge requests from Port workflows using your installed GitLab integration. - [Linear issue actions](/workflows/build-workflows/action-nodes/integration-actions/linear.md): Create and manage Linear issues, comments, documents, and reactions from Port workflows. - [Overview](/workflows/build-workflows/action-nodes/integration-actions/overview.md): Trigger operations in connected platforms like GitHub directly from workflows using Port's existing integrations. ##### kafka Publish messages to Port's dedicated Kafka topic from workflows to process events with your own consumers. - [Kafka](/workflows/build-workflows/action-nodes/kafka.md): Publish messages to Port's dedicated Kafka topic from workflows to process events with your own consumers. ##### port-execution-agent Execute workflow webhook actions inside your private network without exposing public endpoints using the Port execution agent. - [Port execution agent](/workflows/build-workflows/action-nodes/port-execution-agent.md): Execute workflow webhook actions inside your private network without exposing public endpoints using the Port execution agent. ##### upsert-entity Create or update entities in Port's software catalog from workflows using the upsert entity action node. - [Upsert entity](/workflows/build-workflows/action-nodes/upsert-entity.md): Create or update entities in Port's software catalog from workflows using the upsert entity action node. ##### webhook Send HTTP requests to external endpoints from workflows, supporting synchronous and asynchronous operations with custom headers and payloads. - [Webhook](/workflows/build-workflows/action-nodes/webhook.md): Send HTTP requests to external endpoints from workflows, supporting synchronous and asynchronous operations with custom headers and payloads. #### data-flow Pass data between workflow nodes using outputs and variables, reference trigger inputs, and use JQ expressions for data transformation. - [Data flow](/workflows/build-workflows/data-flow.md): Pass data between workflow nodes using outputs and variables, reference trigger inputs, and use JQ expressions for data transformation. #### event-trigger Configure workflows to run automatically when entities are created, updated, or deleted in your software catalog. - [Event trigger](/workflows/build-workflows/event-trigger.md): Configure workflows to run automatically when entities are created, updated, or deleted in your software catalog. #### flow-nodes ##### condition Add branching logic to workflows using condition nodes that evaluate JQ expressions and route execution to different paths. - [Condition nodes](/workflows/build-workflows/flow-nodes/condition.md): Add branching logic to workflows using condition nodes that evaluate JQ expressions and route execution to different paths. ##### input Add human-in-the-loop steps to workflows using input nodes for approvals, manual gates, and decision points that require user responses. - [Input nodes](/workflows/build-workflows/flow-nodes/input.md): Add human-in-the-loop steps to workflows using input nodes for approvals, manual gates, and decision points that require user responses. #### iac Manage Port workflows as code with the Terraform or Pulumi providers, defining workflow nodes and connections. - [Manage workflows with IaC](/workflows/build-workflows/iac.md): Manage Port workflows as code with the Terraform or Pulumi providers, defining workflow nodes and connections. #### quickstart Create your first workflow in Port using the visual editor, JSON editor, or AI-assisted builder to send a webhook notification. - [Quickstart](/workflows/build-workflows/quickstart.md): Create your first workflow in Port using the visual editor, JSON editor, or AI-assisted builder to send a webhook notification. #### reusable-workflows Share logic across workflows by triggering child workflows from parent workflows, enabling reusable approval flows and shared provisioning sequences. - [Reusable workflows](/workflows/build-workflows/reusable-workflows.md): Share logic across workflows by triggering child workflows from parent workflows, enabling reusable approval flows and shared provisioning sequences. #### schedule-trigger Configure workflows to run automatically on a recurring cron schedule. - [Schedule trigger](/workflows/build-workflows/schedule-trigger.md): Configure workflows to run automatically on a recurring cron schedule. #### self-service-trigger ##### advanced-input-configurations Configure advanced user input features including visibility controls, input dependencies, and dynamic default values using JQ expressions. - [Advanced input configurations](/workflows/build-workflows/self-service-trigger/advanced-input-configurations.md): Configure advanced user input features including visibility controls, input dependencies, and dynamic default values using JQ expressions. ##### configuration Configure self-service trigger nodes with user inputs, permissions, and UI contexts to create on-demand workflow executions. - [Configuration](/workflows/build-workflows/self-service-trigger/configuration.md): Configure self-service trigger nodes with user inputs, permissions, and UI contexts to create on-demand workflow executions. ##### contexts Surface self-service triggers in additional UI locations like entity creation flows and action menus using the contexts configuration. - [Contexts](/workflows/build-workflows/self-service-trigger/contexts.md): Surface self-service triggers in additional UI locations like entity creation flows and action menus using the contexts configuration. ##### send-link-to-workflow Generate shareable URLs with pre-filled workflow inputs using JSURL encoding. Useful for bookmarks, documentation, and programmatic links. - [Share a pre-filled workflow URL](/workflows/build-workflows/self-service-trigger/send-link-to-workflow.md): Generate shareable URLs with pre-filled workflow inputs using JSURL encoding. Useful for bookmarks, documentation, and programmatic links. ##### user-inputs - [Array](/workflows/build-workflows/self-service-trigger/user-inputs/array.md): Configure array inputs for workflow forms to accept lists of values like tags, services to deploy, or email recipients. - [Datetime](/workflows/build-workflows/self-service-trigger/user-inputs/datetime.md): Configure datetime inputs for workflow forms to accept date and time values for scheduling, expiration, or maintenance windows. - [Email](/workflows/build-workflows/self-service-trigger/user-inputs/email.md): Configure email inputs for workflow forms to accept and validate email addresses for contacts or notifications. - [Entity](/workflows/build-workflows/self-service-trigger/user-inputs/entity.md): Configure entity inputs for workflow forms to let users select entities from your software catalog like services or environments. - [Number](/workflows/build-workflows/self-service-trigger/user-inputs/number.md): Configure number inputs for workflow forms to accept numeric values like replica counts, port numbers, or resource limits. - [Object](/workflows/build-workflows/self-service-trigger/user-inputs/object.md): Configure object inputs for workflow forms to accept JSON objects for configuration data, metadata, or key-value pairs. - [Structure and fields](/workflows/build-workflows/self-service-trigger/user-inputs/structure-and-fields.md): Define user inputs for self-service workflows including input structure, common fields, and required vs optional configurations. - [Team](/workflows/build-workflows/self-service-trigger/user-inputs/team.md): Configure team inputs for workflow forms to let users select Port teams for ownership assignment or notifications. - [Text](/workflows/build-workflows/self-service-trigger/user-inputs/text.md): Configure text inputs for workflow forms to accept string values like service names, version tags, or commit SHAs. - [Toggle](/workflows/build-workflows/self-service-trigger/user-inputs/toggle.md): Configure toggle inputs for workflow forms to accept boolean true/false values for feature flags or operation modes. - [URL](/workflows/build-workflows/self-service-trigger/user-inputs/url.md): Configure URL inputs for workflow forms to accept and validate URL strings for repository links, API endpoints, or documentation. - [User](/workflows/build-workflows/self-service-trigger/user-inputs/user.md): Configure user inputs for workflow forms to let users select Port users for ownership, reviewers, or on-call assignment. - [YAML](/workflows/build-workflows/self-service-trigger/user-inputs/yaml.md): Configure YAML inputs for workflow forms to accept YAML-formatted content like Kubernetes manifests or configuration files. #### setup-checklist Resolve a saved workflow's missing integrations and secrets from the workflow editor. - [Setup checklist](/workflows/build-workflows/setup-checklist.md): Resolve a saved workflow's missing integrations and secrets from the workflow editor. #### test-workflows Test your workflow directly from the builder by running the entire workflow or individual nodes with mock data before publishing. - [Test workflows](/workflows/build-workflows/test-workflows.md): Test your workflow directly from the builder by running the entire workflow or individual nodes with mock data before publishing. ### actions-and-automations #### create-self-service-experiences Create self-service actions that let developers trigger workflows from Port, such as scaffolding services, provisioning resources, and running day-2 operations, with forms, guardrails, and approvals. - [Self-service actions](/workflows/actions-and-automations/create-self-service-experiences.md): Create self-service actions that let developers trigger workflows from Port, such as scaffolding services, provisioning resources, and running day-2 operations, with forms, guardrails, and approvals. ##### send-link-to-action Generate shareable URLs with pre-filled action inputs using JSURL encoding. Useful for bookmarks, documentation, and programmatic links. - [Share a pre-filled action URL](/workflows/actions-and-automations/create-self-service-experiences/send-link-to-action.md): Generate shareable URLs with pre-filled action inputs using JSURL encoding. Useful for bookmarks, documentation, and programmatic links. ##### set-self-service-actions-rbac Control who can execute self-service actions using role-based permissions. Configure manual approval workflows and ownership-based restrictions. - [Set actions RBAC](/workflows/actions-and-automations/create-self-service-experiences/set-self-service-actions-rbac.md): Control who can execute self-service actions using role-based permissions. Configure manual approval workflows and ownership-based restrictions. - [Dynamic permissions](/workflows/actions-and-automations/create-self-service-experiences/set-self-service-actions-rbac/dynamic-permissions.md): Control action execution and approval using runtime data from your catalog. Define queries and JQ conditions for ownership, manager approval, and on-call rules. - [Examples](/workflows/actions-and-automations/create-self-service-experiences/set-self-service-actions-rbac/dynamic-permissions/examples.md): Dynamic permissions examples including blocking duplicate entities, requiring manager approval, and enforcing ownership-based execution rules. ##### setup-the-backend Configure self-service action backends to execute logic when triggered. Supports GitHub, GitLab, Azure DevOps, Jenkins, webhooks, and more. - [Set up backend](/workflows/actions-and-automations/create-self-service-experiences/setup-the-backend.md): Configure self-service action backends to execute logic when triggered. Supports GitHub, GitLab, Azure DevOps, Jenkins, webhooks, and more. ##### setup-ui-for-action Configure self-service action frontend including title, icon, operation type (create, day-2, delete), and user form inputs. - [Set up frontend](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action.md): Configure self-service action frontend including title, icon, operation type (create, day-2, delete), and user form inputs. - [Advanced input configurations](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/advanced-form-configurations.md): Advanced input settings allow you to create more customizable experiences for users who perform self-service actions. This is done by creating adaptive inputs that change according to data about the entity, the user, and other inputs. - [User Inputs](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs.md): Define user inputs for self-service actions with various types, validation rules, default values, and conditional visibility using jqQuery. - [Array](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/array.md): Array is an input for lists of data - [Datetime](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/datetime.md): Datetime is an input used to reference a date and time - [Email](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/email.md): Email is an input used to save Email addresses - [Entity](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/entity.md): Entity is an input used to reference existing entities from the software catalog when triggering actions - [Number](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/number.md): Number is a basic input for numeric data - [Object](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/object.md): Object is a basic input for JSON data - [Secret](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/secret.md): A secret input encrypts its value before sending it to your backend and never stores or logs it. Choose Port-managed encryption or your own public key. - [Team](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/team.md): Team is an input used to reference teams that exist in Port - [Text](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/text.md): Text is a basic input for textual information - [Toggle (Boolean)](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/toggle.md): Toggle is a basic input that has one of two possible values - true and false - [URL](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/url.md): URL is an input used to save links to websites - [User](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/user.md): User is an input used to reference users that exist in Port - [Yaml](/workflows/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/yaml.md): Yaml is an input used to save object definitions in YAML #### define-automations Create Port automations that trigger actions automatically based on catalog events like entity creation, updates, timers, or external webhooks. Configure triggers, conditions, and backend handlers. - [Define automations](/workflows/actions-and-automations/define-automations.md): Create Port automations that trigger actions automatically based on catalog events like entity creation, updates, timers, or external webhooks. Configure triggers, conditions, and backend handlers. ##### examples Automation examples including Slack/Teams notifications on entity changes, TTL enforcement, PagerDuty incident creation, and scorecard-based alerts. - [Examples](/workflows/actions-and-automations/define-automations/examples.md): Automation examples including Slack/Teams notifications on entity changes, TTL enforcement, PagerDuty incident creation, and scorecard-based alerts. ##### migrate-from-changelog-destination Step-by-step guide for migrating from the legacy changelogDestination feature to Port Automations. - [Migrate from changelog destination](/workflows/actions-and-automations/define-automations/migrate-from-changelog-destination.md): Step-by-step guide for migrating from the legacy changelogDestination feature to Port Automations. ##### setup-action Configure automation backends including webhook, GitHub, GitLab, and Kafka. Define JSON payloads with jq expressions and access trigger event data. - [Set up backend](/workflows/actions-and-automations/define-automations/setup-action.md): Configure automation backends including webhook, GitHub, GitLab, and Kafka. Define JSON payloads with jq expressions and access trigger event data. ##### setup-trigger Configure automation triggers for entity events (create, update, delete, timer expiration) or action run status changes. Supports JQ conditions for filtering. - [Set up trigger](/workflows/actions-and-automations/define-automations/setup-trigger.md): Configure automation triggers for entity events (create, update, delete, timer expiration) or action run status changes. Supports JQ conditions for filtering. #### overview Understand Port's legacy actions and automations so you can run self-service and event-based logic, or move new work to workflows. - [Overview](/workflows/actions-and-automations/overview.md): Understand Port's legacy actions and automations so you can run self-service and event-based logic, or move new work to workflows. #### reflect-action-progress Once a self-service action or automation has been executed, an actionRun object will be created in Port. - [Interact with action runs](/workflows/actions-and-automations/reflect-action-progress.md): Once a self-service action or automation has been executed, an actionRun object will be created in Port. #### setup-backend Configure backends for self-service actions including GitHub workflows, GitLab pipelines, Azure DevOps, Jenkins, webhooks, and Kafka topics. - [Backend types](/workflows/actions-and-automations/setup-backend.md): Configure backends for self-service actions including GitHub workflows, GitLab pipelines, Azure DevOps, Jenkins, webhooks, and Kafka topics. ##### azure-pipeline The Azure backend can trigger Azure pipelines for both self-service actions and automations, using incoming webhook triggers. - [Azure pipeline](/workflows/actions-and-automations/setup-backend/azure-pipeline.md): The Azure backend can trigger Azure pipelines for both self-service actions and automations, using incoming webhook triggers. - [Trigger pipelines in non-default branch](/workflows/actions-and-automations/setup-backend/azure-pipeline/trigger-non-default-branch.md): Configure Port self-service actions to trigger Azure DevOps pipelines from non-default branches using refName parameter. - [Azure DevOps troubleshooting](/workflows/actions-and-automations/setup-backend/azure-pipeline/troubleshooting.md): Common questions and solutions for Azure DevOps integration and pipelines in Port. ##### create-update-entity In some cases, we don't want to run complex logic via a workflow or pipeline, but rather want our backend to simply create or update an entity in our software catalog. - [Create/update entity](/workflows/actions-and-automations/setup-backend/create-update-entity.md): In some cases, we don't want to run complex logic via a workflow or pipeline, but rather want our backend to simply create or update an entity in our software catalog. ##### github-ocean The GitHub Ocean backend allows you to trigger GitHub workflows for your self-service actions and automations, using the GitHub Ocean integration. - [GitHub workflow via Ocean](/workflows/actions-and-automations/setup-backend/github-ocean.md): The GitHub Ocean backend allows you to trigger GitHub workflows for your self-service actions and automations, using the GitHub Ocean integration. ##### github-workflow The GitHub backend allows you to trigger GitHub workflows for your self-service actions and automations, using Port's GitHub application. - [GitHub workflow](/workflows/actions-and-automations/setup-backend/github-workflow.md): The GitHub backend allows you to trigger GitHub workflows for your self-service actions and automations, using Port's GitHub application. - [Auto discovery](/workflows/actions-and-automations/setup-backend/github-workflow/auto-discovery.md): Automatically discover and import GitHub workflow actions into Port as self-service actions using the auto discovery tool. ##### gitlab-pipeline The GitLab backend allows you to trigger GitLab pipelines for your self-service actions and automations. - [GitLab pipeline](/workflows/actions-and-automations/setup-backend/gitlab-pipeline.md): The GitLab backend allows you to trigger GitLab pipelines for your self-service actions and automations. - [GitLab SaaS](/workflows/actions-and-automations/setup-backend/gitlab-pipeline/saas.md): Trigger GitLab SaaS pipelines from Port self-service actions using webhook URLs with trigger tokens. - [Self-hosted GitLab](/workflows/actions-and-automations/setup-backend/gitlab-pipeline/self-hosted.md): Trigger self-hosted GitLab pipelines from Port using the execution agent with Kafka messaging and GitLab trigger tokens. ##### jenkins-pipeline The Jenkins backend allows you to trigger Jenkins pipelines for your self-service actions and automations, using webhooks. - [Jenkins pipeline](/workflows/actions-and-automations/setup-backend/jenkins-pipeline.md): The Jenkins backend allows you to trigger Jenkins pipelines for your self-service actions and automations, using webhooks. ##### kafka Port manages a Kafka topic per customer that publishes the execution run requests. - [Kafka topic](/workflows/actions-and-automations/setup-backend/kafka.md): Port manages a Kafka topic per customer that publishes the execution run requests. ##### security Port IP addresses for firewall allow lists. Covers webhook outbound IPs and Ocean integration source IPs for EU and US regions. - [Security](/workflows/actions-and-automations/setup-backend/security.md): Port IP addresses for firewall allow lists. Covers webhook outbound IPs and Ocean integration source IPs for EU and US regions. ##### send-slack-message The Send Slack message backend type allows you to send a message to a Slack channel, using a webhook URL. - [Send Slack message](/workflows/actions-and-automations/setup-backend/send-slack-message.md): The Send Slack message backend type allows you to send a message to a Slack channel, using a webhook URL. ##### webhook The webhook backend allows you to trigger your own custom webhooks, for both self-service actions and automations. - [Webhook](/workflows/actions-and-automations/setup-backend/webhook.md): The webhook backend allows you to trigger your own custom webhooks, for both self-service actions and automations. - [Circle CI Actions](/workflows/actions-and-automations/setup-backend/webhook/circle-ci.md): Port's Circle CI integration allows you to trigger new pipelines in Circle CI directly from Port. - [Triggering Cloud Build using webhooks](/workflows/actions-and-automations/setup-backend/webhook/cloudbuild-pipeline.md): This page will guide you through the process of triggering your Cloud Build pipelines from Port, using Webhook Actions. - [Software templates](/workflows/actions-and-automations/setup-backend/webhook/examples/software-templates.md): Use Cookiecutter with Port webhooks to scaffold new service repositories from software templates via self-service actions. - [Terraform: No-Code resource provisioning](/workflows/actions-and-automations/setup-backend/webhook/examples/terraform-no-code-resource-provisioning.md): Expose Terraform-based cloud resource provisioning as no-code self-service actions. Example covers S3 bucket lifecycle operations. - [Debug webhooks locally](/workflows/actions-and-automations/setup-backend/webhook/local-debugging-webhook.md): Debug webhook self-service actions locally using smee.io to receive Port webhook payloads on your development machine. - [Port execution agent](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent.md): Port execution agent securely forwards action invocations to private endpoints via Kafka without exposing public URLs. Requires dedicated Kafka topic from Port support. - [Control the payload](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/control-the-payload.md): Port offers two ways to control the payload sent to your backend: - [Argo workflow](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/examples/trigger-an-argo-workflow.md): This example helps internal developer teams to trigger an Argo Workflow using Port's self service actions. We will create a blueprint for argoWorkflow that will be connected to a backend action. We will then add some configuration files (invocations.json) to control the payload and trigger your Argo Workflows directly from Port using the sync execution method. - [CircleCI pipline](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/examples/trigger-circleCI-pipeline.md): This example helps internal developer teams to trigger CircleCI pipelines using Port's self service actions. In particular, you will create a blueprint for circleCI Project that will be connected to a backend action. You will then add some configuration files (invocations.json) to control the payload and trigger your CircleCI pipeline directly from Port using the sync execution method. - [OpsGenie incident](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/examples/trigger-opsgenie-incident.md): This example helps internal developer teams to trigger Opsgenie incidents using Port's self service actions. In particular, you will create a blueprint for opsgenieIncident that will be connected to a backend action. You will then add some configuration files (invocations.json) to control the payload and trigger your Opsgenie incident directly from Port using the sync execution method. - [Terraform Cloud run](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/examples/trigger-terraform-cloud-run.md): This example helps internal developer teams to trigger an Terraform Cloud run using Port's self service actions. We will create a blueprint for Terraform Cloud Workspace that will be connected to a backend action. We will then add some configuration files (invocations.json) to control the payload and trigger your Terraform Cloud run directly from Port using the sync execution method. - [Windmill job](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/examples/trigger-windmill-job.md): This example helps internal developer teams to trigger Windmill job using Port's self service actions. In particular, you will create a blueprint for windmillJob that will be connected to a backend action. You will then add some configuration files (invocations.json) to control the payload and trigger your Windmill job directly from Port using async/sync execution method. - [ArgoCD](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/installation-methods/argocd.md): Install the Port execution agent in Kubernetes using ArgoCD with Helm capabilities. Includes manifest examples and configuration steps. - [Docker](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/installation-methods/docker.md): Run the Port execution agent as a Docker container with Kafka streaming to forward action invocations to private endpoints. - [Helm](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/installation-methods/helm.md): Install the Port execution agent in Kubernetes using Helm. Configure Kafka credentials and optional GitLab pipeline triggers. - [Usage](/workflows/actions-and-automations/setup-backend/webhook/port-execution-agent/usage.md): Configure actions to use the Port execution agent by setting type to WEBHOOK and agent to true. Supports Kafka and HTTP polling streamers. - [Validate webhook signatures](/workflows/actions-and-automations/setup-backend/webhook/signature-verification.md): Verify webhook signatures using x-port-timestamp and x-port-signature headers to ensure requests are from Port and not tampered with. - [Terraform cloud actions](/workflows/actions-and-automations/setup-backend/webhook/terraform-cloud.md): Port's Terraform Cloud integration allows you to trigger Terraform Cloud runs directly from Port. ### concepts Learn the core building blocks of workflows including nodes (triggers, actions, conditions), edges, and how multiple triggers work together. - [Concepts and structure](/workflows/concepts.md): Learn the core building blocks of workflows including nodes (triggers, actions, conditions), edges, and how multiple triggers work together. ### expose-as-tool Make any workflow invokable by AI agents through the Port MCP server. Learn how to configure tool names, write descriptions agents can use, and control who can invoke the workflow. - [Expose workflows as tools](/workflows/expose-as-tool.md): Make any workflow invokable by AI agents through the Port MCP server. Learn how to configure tool names, write descriptions agents can use, and control who can invoke the workflow. ### hide-actions-and-automations Hide Port's legacy actions and automations across the UI, so your users see and build workflows only. - [Hide actions & automations](/workflows/hide-actions-and-automations.md): Hide Port's legacy actions and automations across the UI, so your users see and build workflows only. ### manage-workflows Create a workflow and set who can build it and who can run it, through Port AI, the UI, and the API. - [Manage a workflow](/workflows/manage-workflows.md): Create a workflow and set who can build it and who can run it, through Port AI, the UI, and the API. ### permissions Control who can see and execute workflows using team-based, role-based, or dynamic permission rules on self-service triggers. - [Workflow execute permissions](/workflows/permissions.md): Control who can see and execute workflows using team-based, role-based, or dynamic permission rules on self-service triggers. ### track-workflow-execution #### track-and-manage-runs Monitor workflow executions, view run status and logs, cancel running workflows, and interact with workflow runs through the API. - [Track & manage runs](/workflows/track-workflow-execution/track-and-manage-runs.md): Monitor workflow executions, view run status and logs, cancel running workflows, and interact with workflow runs through the API. #### workflow-run-page View and debug individual workflow executions with visual status indicators showing node success, failure, and data flow through the graph. - [Workflow run page](/workflows/track-workflow-execution/workflow-run-page.md): View and debug individual workflow executions with visual status indicators showing node success, failure, and data flow through the graph. ### use-cases-and-examples Real-world workflow examples for common use cases including scaffolding microservices, deployments, automated catalog updates, and agent-triggered rollbacks. - [Use-cases & examples](/workflows/use-cases-and-examples.md): Real-world workflow examples for common use cases including scaffolding microservices, deployments, automated catalog updates, and agent-triggered rollbacks. ### workflow-catalog Workflows are represented as entities in the _workflow system blueprint, enabling team ownership and catalog-level access control. - [Workflow catalog and ownership](/workflows/workflow-catalog.md): Workflows are represented as entities in the _workflow system blueprint, enabling team ownership and catalog-level access control. ## port-ai ### ai-invocations Track, debug, and collect feedback on every Port AI interaction using AI invocation records. - [AI invocations](/port-ai/ai-invocations.md): Track, debug, and collect feedback on every Port AI interaction using AI invocation records. ### api-interaction Port AI can be accessed programmatically through Port's API, enabling integration into custom applications and workflows. - [Port AI API interaction](/port-ai/api-interaction.md): Port AI can be accessed programmatically through Port's API, enabling integration into custom applications and workflows. ### context-engineering Context engineering is the practice of constructing an optimal information environment that provides the right amount of directions, tools, and knowledge for AI systems to successfully solve problems. - [Context engineering](/port-ai/context-engineering.md): Context engineering is the practice of constructing an optimal information environment that provides the right amount of directions, tools, and knowledge for AI systems to successfully solve problems. ### limits-and-quotas Rate limits, monthly quotas, error handling, and technical limitations for Port AI across all interfaces. - [Limits and quotas](/port-ai/limits-and-quotas.md): Rate limits, monthly quotas, error handling, and technical limitations for Port AI across all interfaces. ### llm-providers-management #### overview Manage and configure LLM providers that power Port AI, including Port's managed infrastructure and bring-your-own-LLM options. - [LLM provider management](/port-ai/llm-providers-management/overview.md): Manage and configure LLM providers that power Port AI, including Port's managed infrastructure and bring-your-own-LLM options. #### providers ##### anthropic-compatible Configure any Anthropic Messages API-compatible endpoint as an LLM provider in Port, including custom gateways and proxies. - [Anthropic compatible setup](/port-ai/llm-providers-management/providers/anthropic-compatible.md): Configure any Anthropic Messages API-compatible endpoint as an LLM provider in Port, including custom gateways and proxies. ##### anthropic Configure Anthropic as an LLM provider in Port to use Claude models directly through Anthropic's API. - [Anthropic setup](/port-ai/llm-providers-management/providers/anthropic.md): Configure Anthropic as an LLM provider in Port to use Claude models directly through Anthropic's API. ##### aws-bedrock Configure AWS Bedrock as an LLM provider in Port using IAM-based authentication to access Claude and other models. - [AWS Bedrock setup](/port-ai/llm-providers-management/providers/aws-bedrock.md): Configure AWS Bedrock as an LLM provider in Port using IAM-based authentication to access Claude and other models. ##### azure-anthropic Configure Azure Anthropic as an LLM provider in Port to use Claude models hosted in your Azure deployment. - [Azure Anthropic setup](/port-ai/llm-providers-management/providers/azure-anthropic.md): Configure Azure Anthropic as an LLM provider in Port to use Claude models hosted in your Azure deployment. ##### azure-openai Configure Azure OpenAI as an LLM provider in Port by storing your Azure credentials and registering your OpenAI deployment. - [Azure OpenAI setup](/port-ai/llm-providers-management/providers/azure-openai.md): Configure Azure OpenAI as an LLM provider in Port by storing your Azure credentials and registering your OpenAI deployment. ##### openai-compatible Configure any OpenAI-compatible endpoint as an LLM provider in Port, including LiteLLM proxies and custom gateways. - [OpenAI compatible setup](/port-ai/llm-providers-management/providers/openai-compatible.md): Configure any OpenAI-compatible endpoint as an LLM provider in Port, including LiteLLM proxies and custom gateways. ##### openai Configure OpenAI as an LLM provider in Port by storing your API key and registering your OpenAI account. - [OpenAI setup](/port-ai/llm-providers-management/providers/openai.md): Configure OpenAI as an LLM provider in Port by storing your API key and registering your OpenAI account. ##### overview Step-by-step setup guides for each LLM provider supported by Port, including OpenAI, Anthropic, Azure, AWS Bedrock, and Vertex AI. - [Provider guides overview](/port-ai/llm-providers-management/providers/overview.md): Step-by-step setup guides for each LLM provider supported by Port, including OpenAI, Anthropic, Azure, AWS Bedrock, and Vertex AI. ##### vertex-anthropic Configure Vertex Anthropic as an LLM provider in Port to use Claude models hosted on Google Vertex AI. - [Vertex Anthropic setup](/port-ai/llm-providers-management/providers/vertex-anthropic.md): Configure Vertex Anthropic as an LLM provider in Port to use Claude models hosted on Google Vertex AI. ##### vertex-gemini Configure Vertex Gemini as an LLM provider in Port using service account or Express Mode authentication. - [Vertex Gemini setup](/port-ai/llm-providers-management/providers/vertex-gemini.md): Configure Vertex Gemini as an LLM provider in Port using service account or Express Mode authentication. #### selecting-llm-provider Learn how to select specific LLM providers and models for Port AI requests, including default provider configuration and validation. - [Selecting LLM provider](/port-ai/llm-providers-management/selecting-llm-provider.md): Learn how to select specific LLM providers and models for Port AI requests, including default provider configuration and validation. #### setup-and-configuration Technical guide for setting up LLM providers in Port, including permissions, secrets management, validation, and troubleshooting. - [Setup & configuration](/port-ai/llm-providers-management/setup-and-configuration.md): Technical guide for setting up LLM providers in Port, including permissions, secrets management, validation, and troubleshooting. ### overview Use Port AI to query your software catalog in natural language, get contextual answers, and run actions through MCP tools. - [Port AI](/port-ai/overview.md): Use Port AI to query your software catalog in natural language, get contextual answers, and run actions through MCP tools. ### port-ai-assistant Use the Port AI Assistant for instant AI chat with ask, plan, and build modes, per-tool approval settings, and no configuration required. - [Port AI Assistant](/port-ai/port-ai-assistant.md): Use the Port AI Assistant for instant AI chat with ask, plan, and build modes, per-tool approval settings, and no configuration required. ### port-ai-plugin Install Port's Agent Skills and plugin to bring Port's context and MCP tools into your coding agent. - [Port AI plugin](/port-ai/port-ai-plugin.md): Install Port's Agent Skills and plugin to bring Port's context and MCP tools into your coding agent. ### security-and-data-controls Learn about Port AI's security practices, data privacy, RBAC enforcement, and controls for responsible AI usage. - [AI security and data controls](/port-ai/security-and-data-controls.md): Learn about Port AI's security practices, data privacy, RBAC enforcement, and controls for responsible AI usage. ### tools-and-approvals Control which tools Port AI can use, how they are approved, and which MCP connectors are attached to an API request. - [Tools and approvals](/port-ai/tools-and-approvals.md): Control which tools Port AI can use, how they are approved, and which MCP connectors are attached to an API request. ## agent-management ### AGENTS This is a hidden guide for AI agents to understand how to maintain and update the AI interfaces documentation in Port Docs. - [AGENTS.md - AI Documentation Maintenance Guide](/agent-management/AGENTS.md): This is a hidden guide for AI agents to understand how to maintain and update the AI interfaces documentation in Port Docs. ### ai-gateway What AI gateways do in the agentic SDLC, where they stop, and how Port governs agents, keys, and tools running through them. - [AI Gateway](/agent-management/ai-gateway.md): What AI gateways do in the agentic SDLC, where they stop, and how Port governs agents, keys, and tools running through them. ### ai-registry #### agent-registry Maintain a centralized agent registry in your Context Lake for AI agents deployed across cloud platforms such as AWS Bedrock and Azure AI Foundry. - [Agent registry](/agent-management/ai-registry/agent-registry.md): Maintain a centralized agent registry in your Context Lake for AI agents deployed across cloud platforms such as AWS Bedrock and Azure AI Foundry. #### managing-ai-primitives Short map of Port AI building blocks in the AI registry: skills, agents, MCP, context, and controls. - [Managing AI primitives](/agent-management/ai-registry/managing-ai-primitives.md): Short map of Port AI building blocks in the AI registry: skills, agents, MCP, context, and controls. #### mcp-connectors Set up MCP connectors as a Port gateway: approve servers, choose exposed tools, and let agents call them under RBAC and audit. - [MCP connectors](/agent-management/ai-registry/mcp-connectors.md): Set up MCP connectors as a Port gateway: approve servers, choose exposed tools, and let agents call them under RBAC and audit. ##### github-mcp-connector Set up the GitHub MCP connector to give Port AI access to GitHub repositories, issues, and pull requests through OAuth authentication. - [GitHub MCP connector](/agent-management/ai-registry/mcp-connectors/github-mcp-connector.md): Set up the GitHub MCP connector to give Port AI access to GitHub repositories, issues, and pull requests through OAuth authentication. ##### use-in-workflows Connect an MCP connector with organization-level OAuth so it can be called from an automated workflow AI node, and verify it end to end. - [Use in workflows](/agent-management/ai-registry/mcp-connectors/use-in-workflows.md): Connect an MCP connector with organization-level OAuth so it can be called from an automated workflow AI node, and verify it end to end. #### mcp-registry The MCP registry is an organizational catalog of MCP servers your teams are allowed to use. Platform teams define which servers are approved, developers discover what is available, and new servers enter through a governed request flow instead of ad hoc installs. - [MCP registry](/agent-management/ai-registry/mcp-registry.md): The MCP registry is an organizational catalog of MCP servers your teams are allowed to use. Platform teams define which servers are approved, developers discover what is available, and new servers enter through a governed request flow instead of ad hoc installs. #### prompts Prebuilt prompts for the Port MCP server that help AI agents query and act on your Port catalog. - [Prompts](/agent-management/ai-registry/prompts.md): Prebuilt prompts for the Port MCP server that help AI agents query and act on your Port catalog. #### skills ##### enrich-port-ai-with-skills Skills give Port AI domain-specific instructions at runtime. Instead of repeating the same prompts or hoping the model infers your process, you package expert workflows as skills that Port AI loads when a task matches. - [Enrich Port AI with skills](/agent-management/ai-registry/skills/enrich-port-ai-with-skills.md): Skills give Port AI domain-specific instructions at runtime. Instead of repeating the same prompts or hoping the model infers your process, you package expert workflows as skills that Port AI loads when a task matches. ##### overview Package Port AI skills with reusable instructions so agents load the right steps when they handle specialized tasks in your org. - [Skills](/agent-management/ai-registry/skills/overview.md): Package Port AI skills with reusable instructions so agents load the right steps when they handle specialized tasks in your org. ##### skills-registry A skills registry is a central library of reusable skills that platform teams publish and developers consume across the organization. Instead of each squad maintaining its own prompts and instructions, approved skills live in Port and sync to developer machines or load at runtime through Port AI. - [Skills registry](/agent-management/ai-registry/skills/skills-registry.md): A skills registry is a central library of reusable skills that platform teams publish and developers consume across the organization. Instead of each squad maintaining its own prompts and instructions, approved skills live in Port and sync to developer machines or load at runtime through Port AI. ##### skills-usage-analytics Analyze how teams adopt and use skills across Cursor and Claude by ingesting skill usage metrics into Port. - [Skills usage analytics](/agent-management/ai-registry/skills/skills-usage-analytics.md): Analyze how teams adopt and use skills across Cursor and Claude by ingesting skill usage metrics into Port. ### custom-agents #### build-an-ai-agent Build an AI agent in Port to assist your developers with finding information and completing tasks. - [Build agents](/agent-management/custom-agents/build-an-ai-agent.md): Build an AI agent in Port to assist your developers with finding information and completing tasks. #### interact-with-ai-agents Learn how to invoke and interact with Port AI agents programmatically through API calls, automations, and workflow integrations. - [Interact with agents](/agent-management/custom-agents/interact-with-ai-agents.md): Learn how to invoke and interact with Port AI agents programmatically through API calls, automations, and workflow integrations. #### overview Build Port custom agents for domain tasks that automate incidents, deployments, and monitoring as machine-to-machine operations. - [Port custom agents](/agent-management/custom-agents/overview.md): Build Port custom agents for domain tasks that automate incidents, deployments, and monitoring as machine-to-machine operations. ### external-agents #### claude-managed-agents Manage Claude agents and trigger sessions directly from Port workflows. - [Claude managed agents](/agent-management/external-agents/claude-managed-agents.md): Manage Claude agents and trigger sessions directly from Port workflows. #### cursor-cloud-agents Manage Cursor cloud agents and trigger runs directly from Port workflows. - [Cursor cloud agents](/agent-management/external-agents/cursor-cloud-agents.md): Manage Cursor cloud agents and trigger runs directly from Port workflows. #### overview Surface external AI agents in Context Lake, track ownership in a registry, and start sessions from Port workflows you already run. - [External agents](/agent-management/external-agents/overview.md): Surface external AI agents in Context Lake, track ownership in a registry, and start sessions from Port workflows you already run. ### overview Govern AI agents, skills, and MCP access in Port so you can discover what exists, control permissions, and operate agents safely. - [Agent management](/agent-management/overview.md): Govern AI agents, skills, and MCP access in Port so you can discover what exists, control permissions, and operate agents safely. ### port-mcp-server #### available-tools Reference for all tools exposed by the Port MCP Server, organized by developer and builder roles with detailed capabilities. - [Available tools](/agent-management/port-mcp-server/available-tools.md): Reference for all tools exposed by the Port MCP Server, organized by developer and builder roles with detailed capabilities. #### installation Install and configure the Port MCP server so AI agents and LLMs can interact with your Port developer portal using natural language. Covers OAuth and client-credentials authentication for local and CI use. - [Installation](/agent-management/port-mcp-server/installation.md): Install and configure the Port MCP server so AI agents and LLMs can interact with your Port developer portal using natural language. Covers OAuth and client-credentials authentication for local and CI use. #### overview Learn how the Port MCP server lets Claude, Cursor, and Copilot query your catalog and run governed actions from your IDE. - [Port MCP server](/agent-management/port-mcp-server/overview.md): Learn how the Port MCP server lets Claude, Cursor, and Copilot query your catalog and run governed actions from your IDE. #### token-based-authentication Connect to the Port MCP server from CI/CD pipelines and headless agents using OAuth client credentials, without interactive user consent. - [Machine authentication for the Port MCP server](/agent-management/port-mcp-server/token-based-authentication.md): Connect to the Port MCP server from CI/CD pipelines and headless agents using OAuth client credentials, without interactive user consent. ## interface-builder ### global-search Search across entities, actions, blueprints, and tech docs using Cmd+K. Configure which blueprints appear in global search results. - [Global search](/interface-builder/global-search.md): Search across entities, actions, blueprints, and tech docs using Cmd+K. Configure which blueprints appear in global search results. ### notifications #### slack-app Use Port's Slack app to interact with your developer portal and AI features directly from Slack, including notifications and catalog queries. - [Slack Application](/interface-builder/notifications/slack-app.md): Use Port's Slack app to interact with your developer portal and AI features directly from Slack, including notifications and catalog queries. ### overview Design Port catalog pages and dashboards where teams view live context and launch governed workflows from the same surface. - [Interface builder](/interface-builder/overview.md): Design Port catalog pages and dashboards where teams view live context and launch governed workflows from the same surface. ### port-interface #### customization Customize your portal with organization branding, logos, announcement banners, and accessibility settings like high contrast mode. - [Customization & accessibility](/interface-builder/port-interface/customization.md): Customize your portal with organization branding, logos, announcement banners, and accessibility settings like high contrast mode. #### dashboards ##### custom-widgets Add custom widgets including iframes for external content, markdown for formatted text, and action buttons to trigger self-service workflows. - [Custom widgets](/interface-builder/port-interface/dashboards/custom-widgets.md): Add custom widgets including iframes for external content, markdown for formatted text, and action buttons to trigger self-service workflows. ##### data-widgets Build data visualizations with number charts, pie charts, line charts, tables, and entity widgets. Supports aggregations, filtering, and conditional formatting. - [Data widgets](/interface-builder/port-interface/dashboards/data-widgets.md): Build data visualizations with number charts, pie charts, line charts, tables, and entity widgets. Supports aggregations, filtering, and conditional formatting. ##### overview Choose Port dashboard widgets for charts, tables, actions, and personal views to show catalog data on home and entity pages. - [Overview](/interface-builder/port-interface/dashboards/overview.md): Choose Port dashboard widgets for charts, tables, actions, and personal views to show catalog data on home and entity pages. ##### personal-widgets Add personal widgets to your home page showing your assigned entities, recently viewed items, and recently used actions. - [Personal widgets](/interface-builder/port-interface/dashboards/personal-widgets.md): Add personal widgets to your home page showing your assigned entities, recently viewed items, and recently used actions. #### page ##### catalog-page Customize Port catalog pages with table views, filters, grouping, sorting, and widgets. Configure initial filters, hide properties, save views, and control page visibility by team or role. - [Catalog page](/interface-builder/port-interface/page/catalog-page.md): Customize Port catalog pages with table views, filters, grouping, sorting, and widgets. Configure initial filters, hide properties, save views, and control page visibility by team or role. ##### dashboard-page Create dashboard pages with customizable widgets to display aggregated entity data, charts, and visualizations in your software catalog. - [Dashboard page](/interface-builder/port-interface/page/dashboard-page.md): Create dashboard pages with customizable widgets to display aggregated entity data, charts, and visualizations in your software catalog. ##### entity-page Customize entity pages with Overview, Related entities, Runs, and Audit log tabs. Add widgets and configure property visibility. - [Entity page](/interface-builder/port-interface/page/entity-page.md): Customize entity pages with Overview, Related entities, Runs, and Audit log tabs. Add widgets and configure property visibility. ##### folders Organize your software catalog by grouping pages into folders. Supports nesting up to 3 levels and drag-and-drop reordering. - [Folders](/interface-builder/port-interface/page/folders.md): Organize your software catalog by grouping pages into folders. Supports nesting up to 3 levels and drag-and-drop reordering. ##### page-permissions Control who can view or edit catalog and dashboard pages using role-based permissions for users and teams. - [Page permissions](/interface-builder/port-interface/page/page-permissions.md): Control who can view or edit catalog and dashboard pages using role-based permissions for users and teams. ##### private-pages Create personal catalog and dashboard pages in a dedicated Private sidebar section. Configure who can create private pages, change visibility between organization and private, and manage permissions on your own pages. - [Private pages](/interface-builder/port-interface/page/private-pages.md): Create personal catalog and dashboard pages in a dedicated Private sidebar section. Configure who can create private pages, change visibility between organization and private, and manage permissions on your own pages. #### plugins A plugin is a self-contained web UI, built from HTML, JavaScript, or a framework such as React, that you develop locally and upload to Port. Plugins power custom widgets that render inside dashboards and entity pages using the same catalog data and permissions as the rest of the platform. - [Plugins](/interface-builder/port-interface/plugins.md): A plugin is a self-contained web UI, built from HTML, JavaScript, or a framework such as React, that you develop locally and upload to Port. Plugins power custom widgets that render inside dashboards and entity pages using the same catalog data and permissions as the rest of the platform. ## governance ### governance-across-pillars #### overview Port's access controls live in each pillar, not one screen. See how catalog, workflow, AI agent, and interface permissions fit together. - [Governance across pillars](/governance/governance-across-pillars/overview.md): Port's access controls live in each pillar, not one screen. See how catalog, workflow, AI agent, and interface permissions fit together. #### scope-building-permissions-across-teams-and-users Scope who can build, run, and approve workflows and scorecards using team-based and dynamic RBAC, the same model that governs your catalog. - [Scope building permissions across teams and users](/governance/governance-across-pillars/scope-building-permissions-across-teams-and-users.md): Scope who can build, run, and approve workflows and scorecards using team-based and dynamic RBAC, the same model that governs your catalog. ### overview Scope what humans and agents can see and do in Port with scorecards, pillar permissions, and audit trails on every action. - [Governance layer](/governance/overview.md): Scope what humans and agents can see and do in Port with scorecards, pillar permissions, and audit trails on every action. ### standards-and-compliance #### concepts-and-structure Understand scorecard concepts including levels, rules, conditions, and filters. Learn how scorecards are structured and how entities are evaluated against defined standards. - [Concepts and structure](/governance/standards-and-compliance/concepts-and-structure.md): Understand scorecard concepts including levels, rules, conditions, and filters. Learn how scorecards are structured and how entities are evaluated against defined standards. #### examples ##### automation-use-cases Automate responses to scorecard rule changes including Slack/Teams notifications and GitHub issue creation. Includes automation configurations and GitHub workflow examples. - [Automation use-cases](/governance/standards-and-compliance/examples/automation-use-cases.md): Automate responses to scorecard rule changes including Slack/Teams notifications and GitHub issue creation. Includes automation configurations and GitHub workflow examples. ##### extend-data-model Extend scorecard blueprints with custom properties like SLA tracking and due dates. Build automated workflows for compliance monitoring, reminders, and exception handling. - [Extend the default scorecards](/governance/standards-and-compliance/examples/extend-data-model.md): Extend scorecard blueprints with custom properties like SLA tracking and due dates. Build automated workflows for compliance monitoring, reminders, and exception handling. ##### scorecard-use-cases Practical scorecard examples including ownership scorecards, relation existence checks, DORA metrics tracking, and agent dispatch guardrails. Ready-to-use JSON configurations you can implement immediately. - [Scorecard use-cases](/governance/standards-and-compliance/examples/scorecard-use-cases.md): Practical scorecard examples including ownership scorecards, relation existence checks, DORA metrics tracking, and agent dispatch guardrails. Ready-to-use JSON configurations you can implement immediately. #### manage-scorecard-groups Define engineering standards once and apply them across multiple blueprints with scorecard groups. Create, edit, and delete groups using the API or Terraform. - [Manage scorecard groups](/governance/standards-and-compliance/manage-scorecard-groups.md): Define engineering standards once and apply them across multiple blueprints with scorecard groups. Create, edit, and delete groups using the API or Terraform. #### manage-scorecards Create, edit, and delete Port scorecards using the UI, API, or Terraform. Includes step-by-step instructions and code examples for managing scorecards programmatically. - [Manage scorecards](/governance/standards-and-compliance/manage-scorecards.md): Create, edit, and delete Port scorecards using the UI, API, or Terraform. Includes step-by-step instructions and code examples for managing scorecards programmatically. #### manage-using-3rd-party-apps Integrate Port scorecards with Jira, GitHub, and Slack for automated issue tracking and notifications. Overview of available third-party app integrations. - [Manage using 3rd-party apps](/governance/standards-and-compliance/manage-using-3rd-party-apps.md): Integrate Port scorecards with Jira, GitHub, and Slack for automated issue tracking and notifications. Overview of available third-party app integrations. ##### github Automatically create and close GitHub issues for violated scorecard rules using the Port message sender. Sync scorecard compliance with GitHub issue tracking. - [Open/close GitHub issues](/governance/standards-and-compliance/manage-using-3rd-party-apps/github.md): Automatically create and close GitHub issues for violated scorecard rules using the Port message sender. Sync scorecard compliance with GitHub issue tracking. ##### jira Automatically create and close Jira issues for violated scorecard rules using the Port message sender. Sync scorecard compliance with Jira task tracking. - [Open/close JIRA issues](/governance/standards-and-compliance/manage-using-3rd-party-apps/jira.md): Automatically create and close Jira issues for violated scorecard rules using the Port message sender. Sync scorecard compliance with Jira task tracking. ##### slack Send Slack reports and reminders for scorecard compliance using the Port message sender GitHub action. Includes examples of scorecard reports and reminders. - [Send Slack messages](/governance/standards-and-compliance/manage-using-3rd-party-apps/slack.md): Send Slack reports and reminders for scorecard compliance using the Port message sender GitHub action. Includes examples of scorecard reports and reminders. #### overview Create scorecard rules and maturity levels that continuously measure services, teams, and resources against engineering standards. - [Standards and compliance](/governance/standards-and-compliance/overview.md): Create scorecard rules and maturity levels that continuously measure services, teams, and resources against engineering standards. ## platform-administration ### audit-log View a complete record of changes in your Port organization. Track entity, blueprint, action, automation, integration, and AI agent-triggered run modifications with filtering and export. - [Audit log](/platform-administration/audit-log.md): View a complete record of changes in your Port organization. Track entity, blueprint, action, automation, integration, and AI agent-triggered run modifications with filtering and export. ### multi-org-management #### manage-port-across-environments Learn how to manage Port resources across multiple environments using IaC (Terraform) or Git-based resource definitions for consistent deployments. - [Manage Port across environments](/platform-administration/multi-org-management/manage-port-across-environments.md): Learn how to manage Port resources across multiple environments using IaC (Terraform) or Git-based resource definitions for consistent deployments. #### multi-org-sso This page covers how to configure SSO when your Port company has multiple organizations, such as separate environments for development and production. It addresses common questions about IdP application registration, team synchronization, and RBAC across organizations. - [Multi-org SSO setup](/platform-administration/multi-org-management/multi-org-sso.md): This page covers how to configure SSO when your Port company has multiple organizations, such as separate environments for development and production. It addresses common questions about IdP application registration, team synchronization, and RBAC across organizations. #### multi-organization Manage multiple Port organizations with cross-organization access. Create organizations, switch between them, and share users. - [Multiple organization membership](/platform-administration/multi-org-management/multi-organization.md): Manage multiple Port organizations with cross-organization access. Create organizations, switch between them, and share users. ### plan-management Learn about Port's plan types. - [Plan management](/platform-administration/plan-management.md): Learn about Port's plan types. ### secrets-management #### port-secrets Manage Port API credentials (client ID, client secret) and organization secrets. Use secrets in integrations and automations with the {{ .secrets.SECRET_NAME }} template syntax. - [Credentials & secrets](/platform-administration/secrets-management/port-secrets.md): Manage Port API credentials (client ID, client secret) and organization secrets. Use secrets in integrations and automations with the {{ .secrets.SECRET_NAME }} template syntax. ### security Port security practices including SOC2 Type II, ISO 27001, GDPR compliance, data encryption, access controls, and infrastructure security. - [Security & compliance](/platform-administration/security.md): Port security practices including SOC2 Type II, ISO 27001, GDPR compliance, data encryption, access controls, and infrastructure security. ### sso-authentication #### SCIM SCIM provisioning is not self-serve. To enable it for your organization, contact Port support. - [SCIM](/platform-administration/sso-authentication/SCIM.md): SCIM provisioning is not self-serve. To enable it for your organization, contact Port support. #### self-serve-sso Set up SSO in Port, connect your identity provider, verify domains, and configure group filters and session settings as an admin. - [Manage your SSO connection](/platform-administration/sso-authentication/self-serve-sso.md): Set up SSO in Port, connect your identity provider, verify domains, and configure group filters and session settings as an admin. #### sso-providers Port offers several SSO integrations, allowing you to easily assign permissions and roles using your users and teams. - [SSO providers](/platform-administration/sso-authentication/sso-providers.md): Port offers several SSO integrations, allowing you to easily assign permissions and roles using your users and teams. ##### ldap Integrate any LDAP system with Port SSO - [LDAP](/platform-administration/sso-authentication/sso-providers/ldap.md): Integrate any LDAP system with Port SSO ##### oidc Integrate any SSO with Port using OIDC application - [OIDC](/platform-administration/sso-authentication/sso-providers/oidc.md): Integrate any SSO with Port using OIDC application - [Entra ID (AzureAD)](/platform-administration/sso-authentication/sso-providers/oidc/azure-ad.md): Integrate AzureAD with Port using OIDC - [Okta](/platform-administration/sso-authentication/sso-providers/oidc/okta.md): Integrate Okta with Port - [Onelogin](/platform-administration/sso-authentication/sso-providers/oidc/onelogin.md): Integrate Onelogin with Port ##### saml Integrate any SSO with Port using SAML application - [SAML](/platform-administration/sso-authentication/sso-providers/saml.md): Integrate any SSO with Port using SAML application - [Entra ID (AzureAD)](/platform-administration/sso-authentication/sso-providers/saml/azure-ad.md): Integrate Entra ID (AzureAD) with Port using SAML - [Google Workspace](/platform-administration/sso-authentication/sso-providers/saml/google-workspace.md): Integrate Google Workspace with Port using SAML - [JumpCloud](/platform-administration/sso-authentication/sso-providers/saml/jumpcloud.md): Integrate JumpCloud with Port using SAML - [Okta](/platform-administration/sso-authentication/sso-providers/saml/okta.md): Integrate Okta with Port using SAML ### usage-dashboard Track portal usage metrics including user activity, entity counts, action execution, integration usage, and AI interactions. Updated daily. - [Portal usage dashboard](/platform-administration/usage-dashboard.md): Track portal usage metrics including user activity, entity counts, action execution, integration usage, and AI interactions. Updated daily. ### users-and-teams #### manage-users-teams Manage users, teams, roles, and permissions in Port. Invite users, assign roles, create teams, and configure granular access controls. - [Manage users & teams](/platform-administration/users-and-teams/manage-users-teams.md): Manage users, teams, roles, and permissions in Port. Invite users, assign roles, create teams, and configure granular access controls. #### user-membership-reference A complete reference for how users are added to organizations in Port — SSO, SCIM, invitations, member statuses, and edge cases. - [User membership reference](/platform-administration/users-and-teams/user-membership-reference.md): A complete reference for how users are added to organizations in Port — SSO, SCIM, invitations, member statuses, and edge cases. #### view-as-different-user Test permissions by viewing the portal as a different user. Validate dynamic filters, role-based access, and page visibility without switching accounts. - [View as a different user](/platform-administration/users-and-teams/view-as-different-user.md): Test permissions by viewing the portal as a different user. Validate dynamic filters, role-based access, and page visibility without switching accounts. ## Guides Step-by-step tutorials and walkthroughs for specific Port use cases. These guides show you how to implement common scenarios with Port. For API reference and concept documentation, see the reference sections in /context-lake/ and /api-reference/. - [Guides](/guides.md): Step-by-step tutorials and walkthroughs for specific Port use cases. These guides show you how to implement common scenarios with Port. For API reference and concept documentation, see the reference sections in /context-lake/ and /api-reference/. ### All guides #### add-tags-to-aws-resources Enable agents and developers to add tags to AWS S3 buckets and ECR repositories through governed Port workflows. - [Add tags to AWS resources](/guides/all/add-tags-to-aws-resources.md): Enable agents and developers to add tags to AWS S3 buckets and ECR repositories through governed Port workflows. #### ai-powered-github-workflow-documentation Enable agents and developers to automatically generate and maintain human-readable documentation for GitHub Actions workflows using Port's AI agents and automation system. - [Auto-generate GitHub workflow documentation](/guides/all/ai-powered-github-workflow-documentation.md): Enable agents and developers to automatically generate and maintain human-readable documentation for GitHub Actions workflows using Port's AI agents and automation system. #### ai-powered-incident-management Enable agents and developers to implement an AI-powered incident management lifecycle in Port, from triage and orchestration to incident updates, RCA, and postmortems. - [AI-powered incident management](/guides/all/ai-powered-incident-management.md): Enable agents and developers to implement an AI-powered incident management lifecycle in Port, from triage and orchestration to incident updates, RCA, and postmortems. #### apply-labels-to-github-pr-based-on-sonar-scans Enable agents and developers to automatically label your GitHub pull request based on SonarQube scan reports through Port's agentic SDLC platform. - [Auto-label your GitHub PRs with Sonar Scans](/guides/all/apply-labels-to-github-pr-based-on-sonar-scans.md): Enable agents and developers to automatically label your GitHub pull request based on SonarQube scan reports through Port's agentic SDLC platform. #### approval-workflow-for-gitlab-deployment Enable agents and developers to govern GitLab deployments with Port workflows and ServiceNow approvals. - [Approval workflows for service deployment](/guides/all/approval-workflow-for-gitlab-deployment.md): Enable agents and developers to govern GitLab deployments with Port workflows and ServiceNow approvals. #### assign-pr-reviewers-with-claude Enable agents and developers to automatically assess pull request risk, assign reviewers, comment, and auto-approve low-risk changes using a Claude managed agent triggered from a Port workflow. - [Assign PR reviewers with a Claude managed agent](/guides/all/assign-pr-reviewers-with-claude.md): Enable agents and developers to automatically assess pull request risk, assign reviewers, comment, and auto-approve low-risk changes using a Claude managed agent triggered from a Port workflow. #### auto-assign-bugs-to-owners Enable agents and developers to automatically assign Jira bugs to owning teams and services with Port automations and AI. - [Auto-assign bugs to owners with AI](/guides/all/auto-assign-bugs-to-owners.md): Enable agents and developers to automatically assign Jira bugs to owning teams and services with Port automations and AI. #### auto-enhance-pr-descriptions-with-ai Enable agents and developers to automatically enhance PR descriptions with AI-generated, template-compliant content using a Port workflow, an AI agent, and coding assistants. - [Auto-enhance PR descriptions with AI](/guides/all/auto-enhance-pr-descriptions-with-ai.md): Enable agents and developers to automatically enhance PR descriptions with AI-generated, template-compliant content using a Port workflow, an AI agent, and coding assistants. #### auto-remediate-insecure-cloud-resources-with-ai Enable agents and developers to automatically detect and remediate insecure cloud resources using Port workflows and Claude Code to generate infrastructure-as-code patches. - [Auto-remediate insecure cloud resources with AI](/guides/all/auto-remediate-insecure-cloud-resources-with-ai.md): Enable agents and developers to automatically detect and remediate insecure cloud resources using Port workflows and Claude Code to generate infrastructure-as-code patches. #### automate-slack-alert-for-overdue-prs Enable agents and developers to keep pull request reviews moving with automated Slack alerts for overdue pull requests. - [Automate Slack Alert for Overdue PRs](/guides/all/automate-slack-alert-for-overdue-prs.md): Enable agents and developers to keep pull request reviews moving with automated Slack alerts for overdue pull requests. #### automate-user-role-update Enable agents and developers to maintain governed Port access by assigning the Admin role when users join an administrators team. - [Automate admin role assignment](/guides/all/automate-user-role-update.md): Enable agents and developers to maintain governed Port access by assigning the Admin role when users join an administrators team. #### automatically-approve-action-using-automation Enable agents and developers to govern routine requests with automated approvals for Port self-service actions. - [Automate self-service action approvals](/guides/all/automatically-approve-action-using-automation.md): Enable agents and developers to govern routine requests with automated approvals for Port self-service actions. #### automatically-resolve-tickets Enable agents and developers to resolve Jira tickets with coding agents through governed Port workflows or an n8n workflow enriched by Port context. - [Automatically resolve tickets with Port](/guides/all/automatically-resolve-tickets.md): Enable agents and developers to resolve Jira tickets with coding agents through governed Port workflows or an n8n workflow enriched by Port context. #### automatically-set-relations-between-entities-with-automation Enable agents and developers to link service entities to owning teams through Port automations without custom integration code. - [Automatically set relations between entities with automation](/guides/all/automatically-set-relations-between-entities-with-automation.md): Enable agents and developers to link service entities to owning teams through Port automations without custom integration code. #### azure-resource-tagging-initiative Enable agents and developers to track and enforce Azure resource tagging compliance using Port scorecards, dashboards, and self-service actions. - [Track Azure resource tagging compliance](/guides/all/azure-resource-tagging-initiative.md): Enable agents and developers to track and enforce Azure resource tagging compliance using Port scorecards, dashboards, and self-service actions. #### build-ai-agent-registry Enable agents and developers to build a centralized AI Agent Registry in Port to discover, govern, and manage AI agents deployed across AWS Bedrock and Azure AI Foundry. - [Build an AI Agent Registry](/guides/all/build-ai-agent-registry.md): Enable agents and developers to build a centralized AI Agent Registry in Port to discover, govern, and manage AI agents deployed across AWS Bedrock and Azure AI Foundry. #### build-github-dashboards-in-port Enable agents and developers to build GitHub dashboards in Port for dependency security, identity and access, repository activity, and engineering metrics. - [Build GitHub dashboards in Port](/guides/all/build-github-dashboards-in-port.md): Enable agents and developers to build GitHub dashboards in Port for dependency security, identity and access, repository activity, and engineering metrics. #### build-port-with-mcp Use the Port MCP server with your assistant to create blueprints, actions, automations, and scorecards from described outcomes. - [Build and configure Port using the MCP server](/guides/all/build-port-with-mcp.md): Use the Port MCP server with your assistant to create blueprints, actions, automations, and scorecards from described outcomes. #### build-port-workflows-with-mcp Use AI and Port's MCP server to build Port workflows through natural language conversations, designing multi-step node graphs without hand-writing workflow JSON. - [Build workflows with AI](/guides/all/build-port-workflows-with-mcp.md): Use AI and Port's MCP server to build Port workflows through natural language conversations, designing multi-step node graphs without hand-writing workflow JSON. #### calculate-blast-radius-with-ai Enable agents and developers to calculate deployment blast radius and production risk using AI, service dependencies, and Port self-service actions. - [Calculate blast radius with AI](/guides/all/calculate-blast-radius-with-ai.md): Enable agents and developers to calculate deployment blast radius and production risk using AI, service dependencies, and Port self-service actions. #### centralize-ai-coding-rules-with-port Centralize AI coding rules in Port and use a workflow to sync them to AGENTS.md for GitHub Copilot. - [Centralize AI coding rules with Port](/guides/all/centralize-ai-coding-rules-with-port.md): Centralize AI coding rules in Port and use a workflow to sync them to AGENTS.md for GitHub Copilot. #### connect-github-codeowners-with-service-team-and-user Enable agents and developers to connect GitHub CODEOWNERS with Port repositories, teams, and users for governed ownership context. - [Connect GitHub CODEOWNERS with Repository, Team & User](/guides/all/connect-github-codeowners-with-service-team-and-user.md): Enable agents and developers to connect GitHub CODEOWNERS with Port repositories, teams, and users for governed ownership context. #### connect-github-pr-with-jira-issue Enable agents and developers to trace delivery work by connecting GitHub pull requests to Jira issues in Port. - [Connect GitHub Pull Request with Jira Issue](/guides/all/connect-github-pr-with-jira-issue.md): Enable agents and developers to trace delivery work by connecting GitHub pull requests to Jira issues in Port. #### copy-pipeline-template-to-target-repo Enable agents and developers to copy pipeline template from one repository to another using Port Actions. - [Copy Pipeline Template to Target Repo](/guides/all/copy-pipeline-template-to-target-repo.md): Enable agents and developers to copy pipeline template from one repository to another using Port Actions. #### create-an-ec2-instance Enable agents and developers to create an EC2 instance in Port using GitHub Actions or GitLab CI. - [Create an AWS EC2 instance](/guides/all/create-an-ec2-instance.md): Enable agents and developers to create an EC2 instance in Port using GitHub Actions or GitLab CI. #### create-cloud-resource-using-iac Enable agents and developers to create cloud resources using Infrastructure as Code (IaC) in Port for efficient and automated deployments. - [Create cloud resources using IaC](/guides/all/create-cloud-resource-using-iac.md): Enable agents and developers to create cloud resources using Infrastructure as Code (IaC) in Port for efficient and automated deployments. #### create-engineering-intelligence-pulse Enable agents and developers to run a weekly Engineering Intelligence assessment that ranks the engineering improvements worth making, records each one with its evidence, and publishes a brief to Slack through Port's agentic SDLC platform. - [Create the Engineering Intelligence Pulse](/guides/all/create-engineering-intelligence-pulse.md): Enable agents and developers to run a weekly Engineering Intelligence assessment that ranks the engineering improvements worth making, records each one with its evidence, and publishes a brief to Slack through Port's agentic SDLC platform. #### create-github-copilot-ai-usage-dashboard-custom-plugin Enable agents and developers to track GitHub Copilot adoption, acceptance rates, and AI-generated insights with a Port custom plugin. - [Measure GitHub Copilot adoption and usage with plugins](/guides/all/create-github-copilot-ai-usage-dashboard-custom-plugin.md): Enable agents and developers to track GitHub Copilot adoption, acceptance rates, and AI-generated insights with a Port custom plugin. #### create-incident-io-incident Enable agents and developers to initiate incident.io response through governed Port self-service actions. - [Create an incident.io Incident](/guides/all/create-incident-io-incident.md): Enable agents and developers to initiate incident.io response through governed Port self-service actions. #### create-jira-issue-from-datadog-alert Enable agents and developers to create Jira issues from Datadog and other alerts through governed Port workflows and Jira webhooks. - [Create a Jira issue from a monitoring alert](/guides/all/create-jira-issue-from-datadog-alert.md): Enable agents and developers to create Jira issues from Datadog and other alerts through governed Port workflows and Jira webhooks. #### create-jira-issue-gitlab Enable agents and developers to create Jira issues through a governed Port self-service action backed by GitLab CI. - [Create a Jira issue using GitLab CI](/guides/all/create-jira-issue-gitlab.md): Enable agents and developers to create Jira issues through a governed Port self-service action backed by GitLab CI. #### create-new-aws-account-gitlab Enable agents and developers to provision AWS accounts through a governed Port workflow that validates the request with AI and provisions it with GitLab CI/CD and Terraform. - [Automate AWS account creation with GitLab](/guides/all/create-new-aws-account-gitlab.md): Enable agents and developers to provision AWS accounts through a governed Port workflow that validates the request with AI and provisions it with GitLab CI/CD and Terraform. #### create-organizational-hierarchy-views Enable agents and developers to model and visualize hierarchy tiers in your organization through Port's agentic SDLC platform. - [Create organizational hierarchy views](/guides/all/create-organizational-hierarchy-views.md): Enable agents and developers to model and visualize hierarchy tiers in your organization through Port's agentic SDLC platform. #### create-roi-dashboard Enable agents and developers to create a dashboard that tracks the ROI of actions in Port. - [Create an actions ROI dashboard](/guides/all/create-roi-dashboard.md): Enable agents and developers to create a dashboard that tracks the ROI of actions in Port. #### create-slack-channel-for-reported-incident-with-port-workflows Learn how to automatically create a Slack channel and GitHub issue when a PagerDuty incident is reported, using Port Workflows for real-time team communication and incident documentation. - [Auto-create Slack channel & GitHub issue for PagerDuty incidents](/guides/all/create-slack-channel-for-reported-incident-with-port-workflows.md): Learn how to automatically create a Slack channel and GitHub issue when a PagerDuty incident is reported, using Port Workflows for real-time team communication and incident documentation. #### create-slack-channel-for-reported-incident Enable agents and developers to coordinate PagerDuty response by creating a Slack channel and GitHub issue automatically through Port. - [Auto-create Slack channel & GitHub issue for PagerDuty incidents](/guides/all/create-slack-channel-for-reported-incident.md): Enable agents and developers to coordinate PagerDuty response by creating a Slack channel and GitHub issue automatically through Port. #### create-survey-intelligence Enable agents and developers to deploy the Survey Intelligence plugins (Survey Builder, Survey Forms, and Survey Analytics) to run engineering surveys and turn responses into insights through Port's agentic SDLC platform. - [Create Survey Intelligence](/guides/all/create-survey-intelligence.md): Enable agents and developers to deploy the Survey Intelligence plugins (Survey Builder, Survey Forms, and Survey Analytics) to run engineering surveys and turn responses into insights through Port's agentic SDLC platform. #### deploy-azure-resource-with-terraform Enable agents and developers to deploy Azure storage accounts with Terraform from Port using GitHub Actions, Azure DevOps, or Jenkins. - [Deploy Azure resource with Terraform](/guides/all/deploy-azure-resource-with-terraform.md): Enable agents and developers to deploy Azure storage accounts with Terraform from Port using GitHub Actions, Azure DevOps, or Jenkins. #### deploy-s3-bucket-crossplane Enable agents and developers to provision S3 buckets through governed Port workflows backed by Crossplane. - [Deploy S3 Bucket using Crossplane](/guides/all/deploy-s3-bucket-crossplane.md): Enable agents and developers to provision S3 buckets through governed Port workflows backed by Crossplane. #### enforce-ai-coding-security-standards Enable agents and developers to enforce AI coding security standards by checking for comprehensive Cursor security rules and GitHub Copilot instructions using Port scorecards and GitHub integration. - [Enforce AI coding security standards](/guides/all/enforce-ai-coding-security-standards.md): Enable agents and developers to enforce AI coding security standards by checking for comprehensive Cursor security rules and GitHub Copilot instructions using Port scorecards and GitHub integration. #### enrich-tasks-with-ai Enable agents and developers to enrich tasks with AI-powered context using Port workflows, providing developers with automated insights, related issues, and potential collaborators. - [Enrich tasks with AI-powered context](/guides/all/enrich-tasks-with-ai.md): Enable agents and developers to enrich tasks with AI-powered context using Port workflows, providing developers with automated insights, related issues, and potential collaborators. #### ensure-production-readiness Enable agents and developers to ensure production readiness in Port, optimizing your deployments for reliability and performance. - [Ensure production readiness](/guides/all/ensure-production-readiness.md): Enable agents and developers to ensure production readiness in Port, optimizing your deployments for reliability and performance. #### find-internal-documentation-with-ai Enable agents and developers to find internal documentation with AI through Port's agentic SDLC platform. - [Find internal documentation with AI](/guides/all/find-internal-documentation-with-ai.md): Enable agents and developers to find internal documentation with AI through Port's agentic SDLC platform. #### generate-zendesk-ticket-summaries-with-ai Summarize Zendesk tickets using workflows that fetches ticket comments and side conversations, then uses Port AI to produce a structured summary. - [Summarize Zendesk tickets with AI](/guides/all/generate-zendesk-ticket-summaries-with-ai.md): Summarize Zendesk tickets using workflows that fetches ticket comments and side conversations, then uses Port AI to produce a structured summary. #### heal-unhealthy-k8s-pods Build a single Port workflow that detects unhealthy Kubernetes workloads, diagnoses them with Port AI, and applies targeted fixes automatically. - [Auto-heal unhealthy Kubernetes pods with Port workflows](/guides/all/heal-unhealthy-k8s-pods.md): Build a single Port workflow that detects unhealthy Kubernetes workloads, diagnoses them with Port AI, and applies targeted fixes automatically. #### iam-permissions-guide Enable agents and developers to request time-bound AWS IAM permissions through governed Port workflows and automated revocation. - [IAM permission management](/guides/all/iam-permissions-guide.md): Enable agents and developers to request time-bound AWS IAM permissions through governed Port workflows and automated revocation. #### implement-rbac-for-ai-agents-with-n8n-and-port Enable agents and developers to enforce role-based tool access for AI agents using Port and n8n. - [RBAC for AI agents with n8n and Port](/guides/all/implement-rbac-for-ai-agents-with-n8n-and-port.md): Enable agents and developers to enforce role-based tool access for AI agents using Port and n8n. #### incident-blueprint Enable agents and developers to implement the incident blueprint pattern for self-healing incident workflows through Port's agentic SDLC platform. - [Implement the incident blueprint pattern](/guides/all/incident-blueprint.md): Enable agents and developers to implement the incident blueprint pattern for self-healing incident workflows through Port's agentic SDLC platform. #### ingest-claude-code-security-reviews Enable agents and developers to ingest Claude Code security review findings and visualize them in Port dashboards. - [Ingest Claude Code security reviews](/guides/all/ingest-claude-code-security-reviews.md): Enable agents and developers to ingest Claude Code security review findings and visualize them in Port dashboards. #### ingest-cloud-resources-using-apm-integrations Enable agents and developers to ingest cloud resources monitored by Datadog, Dynatrace, or New Relic into Port. - [Ingest cloud resources using APM integrations](/guides/all/ingest-cloud-resources-using-apm-integrations.md): Enable agents and developers to ingest cloud resources monitored by Datadog, Dynatrace, or New Relic into Port. #### ingest-data-via-airbyte-and-s3 Enable agents and developers to ingest HiBob or Okta data into Port using Airbyte, Amazon S3, and a custom webhook integration. - [Ingest data via Airbyte and S3](/guides/all/ingest-data-via-airbyte-and-s3.md): Enable agents and developers to ingest HiBob or Okta data into Port using Airbyte, Amazon S3, and a custom webhook integration. #### ingest-dotnet-framework-versions Enable agents and developers to ingest .NET framework versions from .csproj files and track them across your repositories using Port. - [Ingest .NET framework versions from repositories](/guides/all/ingest-dotnet-framework-versions.md): Enable agents and developers to ingest .NET framework versions from .csproj files and track them across your repositories using Port. #### ingest-gitlab-vulnerabilities-into-your-context-lake Enable agents and developers to centralize GitLab SAST, DAST, dependency, and container findings by team and service in Port's context lake. - [Ingest GitLab security vulnerabilities into your context lake](/guides/all/ingest-gitlab-vulnerabilities-into-your-context-lake.md): Enable agents and developers to centralize GitLab SAST, DAST, dependency, and container findings by team and service in Port's context lake. #### ingest-linearb-metrics-into-your-context-lake Enable agents and developers to consolidate LinearB engineering metrics into Port's Engineering Intelligence platform, leveraging Port's native analytics alongside imported data for a unified view of engineering performance. - [Ingest LinearB metrics into your context lake](/guides/all/ingest-linearb-metrics-into-your-context-lake.md): Enable agents and developers to consolidate LinearB engineering metrics into Port's Engineering Intelligence platform, leveraging Port's native analytics alongside imported data for a unified view of engineering performance. #### ingest-prompts-skills-from-github-using-gitops Enable agents and developers to ingest AI prompts and skills from GitHub using GitOps by mapping repo files to Port blueprints. - [Ingest prompts and skills from GitHub using GitOps](/guides/all/ingest-prompts-skills-from-github-using-gitops.md): Enable agents and developers to ingest AI prompts and skills from GitHub using GitOps by mapping repo files to Port blueprints. #### ingest-repository-files-into-your-context-lake Enable agents and developers to parse package manifests, API specifications, SBOMs, SARIF files, and security scan results from repositories into Port. - [Ingest repository files into your context lake](/guides/all/ingest-repository-files-into-your-context-lake.md): Enable agents and developers to parse package manifests, API specifications, SBOMs, SARIF files, and security scan results from repositories into Port. #### ingest-slack-data-via-airbyte-s3-and-webhook Enable agents and developers to ingest Slack channels, users, and memberships into Port using Airbyte or Fivetran, S3, and a webhook integration. - [Ingest Slack data into Port](/guides/all/ingest-slack-data-via-airbyte-s3-and-webhook.md): Enable agents and developers to ingest Slack channels, users, and memberships into Port using Airbyte or Fivetran, S3, and a webhook integration. #### ingest-swarmia-metrics-into-your-context-lake Enable agents and developers to consolidate Swarmia DORA and pull request metrics into Port's Engineering Intelligence platform, leveraging Port's native analytics alongside imported data for a unified view of engineering performance. - [Ingest Swarmia metrics into your context lake](/guides/all/ingest-swarmia-metrics-into-your-context-lake.md): Enable agents and developers to consolidate Swarmia DORA and pull request metrics into Port's Engineering Intelligence platform, leveraging Port's native analytics alongside imported data for a unified view of engineering performance. #### ingest-vulnerability-alerts-from-orca-security-using-a-custom-webhook-integration Enable agents and developers to investigate Orca Security vulnerabilities by ingesting historical and real-time alerts into Port. - [Ingest vulnerability alerts from Orca Security](/guides/all/ingest-vulnerability-alerts-from-orca-security-using-a-custom-webhook-integration.md): Enable agents and developers to investigate Orca Security vulnerabilities by ingesting historical and real-time alerts into Port. #### interact-with-pagerduty-incidents Learn how to create, trigger, reassign, and resolve PagerDuty incidents from Port using a single native workflow, and keep your catalog in sync. - [Interact with PagerDuty incidents](/guides/all/interact-with-pagerduty-incidents.md): Learn how to create, trigger, reassign, and resolve PagerDuty incidents from Port using a single native workflow, and keep your catalog in sync. #### interact-with-servicenow Enable agents and developers to create, update, trigger, and delete ServiceNow records and incidents using Port workflows. - [Interact with ServiceNow records & incidents](/guides/all/interact-with-servicenow.md): Enable agents and developers to create, update, trigger, and delete ServiceNow records and incidents using Port workflows. #### keep-azure-catalog-upto-date-with-incremental-syncing Enable agents and developers to keep your Azure catalog up to date by syncing only changed resources into Port using GitHub Actions or a local script. - [Keep your Azure catalog up to date with incremental syncing](/guides/all/keep-azure-catalog-upto-date-with-incremental-syncing.md): Enable agents and developers to keep your Azure catalog up to date by syncing only changed resources into Port using GitHub Actions or a local script. #### let-developers-enrich-services-using-gitops Enable agents and developers to enrich service context through Git-managed repository metadata ingested into Port. - [Enrich services using GitOps](/guides/all/let-developers-enrich-services-using-gitops.md): Enable agents and developers to enrich service context through Git-managed repository metadata ingested into Port. #### lock-and-unlock-services-in-port Enable agents and developers to govern deployments with Port service locks and automated GitHub workflow checks. - [Lock and unlock services](/guides/all/lock-and-unlock-services-in-port.md): Enable agents and developers to govern deployments with Port service locks and automated GitHub workflow checks. #### manage-ai-instructions Centralize AI instructions in Port and use a workflow to automatically sync AGENTS.md to GitHub repositories when instructions change. - [Manage AI instructions with Port](/guides/all/manage-ai-instructions.md): Centralize AI instructions in Port and use a workflow to automatically sync AGENTS.md to GitHub repositories when instructions change. #### manage-and-surface-technical-docs Enable agents and developers to manage and surface technical documentation in Port by ingesting markdown from a Git source, displaying it on service or repository pages, and adding the TechDocs plugin. - [Manage and surface technical documentation in Port](/guides/all/manage-and-surface-technical-docs.md): Enable agents and developers to manage and surface technical documentation in Port by ingesting markdown from a Git source, displaying it on service or repository pages, and adding the TechDocs plugin. #### manage-and-visualize-cloud-resources Enable agents and developers to manage and visualize AWS, Azure, and GCP cloud resources in Port using integrations, self-service actions, and dashboards. - [Manage and visualize cloud resources](/guides/all/manage-and-visualize-cloud-resources.md): Enable agents and developers to manage and visualize AWS, Azure, and GCP cloud resources in Port using integrations, self-service actions, and dashboards. #### manage-and-visualize-jira-issues Enable agents and developers to monitor and manage Jira issues using dashboards, labels, and self-service actions in Port. - [Manage and visualize your Jira issues](/guides/all/manage-and-visualize-jira-issues.md): Enable agents and developers to monitor and manage Jira issues using dashboards, labels, and self-service actions in Port. #### manage-and-visualize-pagerduty-incidents Enable agents and developers to manage your PagerDuty incidents with self-service actions and monitor them using dashboards in Port. - [Manage and visualize your PagerDuty incidents](/guides/all/manage-and-visualize-pagerduty-incidents.md): Enable agents and developers to manage your PagerDuty incidents with self-service actions and monitor them using dashboards in Port. #### manage-and-visualize-your-launchdarkly-feature-flags Enable agents and developers to manage and visualize your LaunchDarkly feature flags using dashboards and self-service actions in Port. - [Manage and visualize your LaunchDarkly feature flags](/guides/all/manage-and-visualize-your-launchdarkly-feature-flags.md): Enable agents and developers to manage and visualize your LaunchDarkly feature flags using dashboards and self-service actions in Port. #### manage-argocd-applications Enable agents and developers to sync, restart, and self-heal Argo CD applications from Port using governed workflows, Port AI diagnosis, and GitHub Actions backends. - [Manage Argo CD applications](/guides/all/manage-argocd-applications.md): Enable agents and developers to sync, restart, and self-heal Argo CD applications from Port using governed workflows, Port AI diagnosis, and GitHub Actions backends. #### manage-clusters Enable agents and developers to provision and manage Kubernetes clusters through governed Port workflows backed by Crossplane and Argo CD. - [Create and manage Kubernetes clusters](/guides/all/manage-clusters.md): Enable agents and developers to provision and manage Kubernetes clusters through governed Port workflows backed by Crossplane and Argo CD. #### manage-developer-environments Enable agents and developers to create, extend, and tear down developer environments through governed Port workflows backed by GitHub Actions. - [Manage developer environments](/guides/all/manage-developer-environments.md): Enable agents and developers to create, extend, and tear down developer environments through governed Port workflows backed by GitHub Actions. #### manage-firehydrant-incidents Enable agents and developers to manage FireHydrant incidents through governed Port actions while keeping incident context synchronized. - [Manage FireHydrant incidents](/guides/all/manage-firehydrant-incidents.md): Enable agents and developers to manage FireHydrant incidents through governed Port actions while keeping incident context synchronized. #### manage-humanitec-applications Enable agents and developers to ingest Humanitec resources into Port and manage Humanitec applications with self-service actions. - [Manage Humanitec applications](/guides/all/manage-humanitec-applications.md): Enable agents and developers to ingest Humanitec resources into Port and manage Humanitec applications with self-service actions. #### manage-incident-lifecycle Enable agents and developers to create governed self-service actions to acknowledge, escalate, and resolve PagerDuty incidents from Port. - [Manage incident lifecycle](/guides/all/manage-incident-lifecycle.md): Enable agents and developers to create governed self-service actions to acknowledge, escalate, and resolve PagerDuty incidents from Port. #### manage-kubernetes-namespaces Enable agents and developers to create and manage Kubernetes namespaces through Port with automated workflows, approval processes, and chained self-service actions. - [Manage Kubernetes namespaces](/guides/all/manage-kubernetes-namespaces.md): Enable agents and developers to create and manage Kubernetes namespaces through Port with automated workflows, approval processes, and chained self-service actions. #### manage-mcp-registry Enable agents and developers to build a governed MCP server registry in Port using workflows, MCP connectors, a dashboard, and an AI assistant, so teams can request, review, and discover approved MCP servers. - [Manage MCP server registry](/guides/all/manage-mcp-registry.md): Enable agents and developers to build a governed MCP server registry in Port using workflows, MCP connectors, a dashboard, and an AI assistant, so teams can request, review, and discover approved MCP servers. #### manage-pagerduty-on-call-schedules Enable agents and developers to manage and track PagerDuty on-call schedules across teams and services with dashboards and Port workflows through Port's agentic SDLC platform. - [Manage PagerDuty on-call schedules](/guides/all/manage-pagerduty-on-call-schedules.md): Enable agents and developers to manage and track PagerDuty on-call schedules across teams and services with dashboards and Port workflows through Port's agentic SDLC platform. #### manage-pull-requests Enable agents and developers to manage GitHub pull requests from Port using a workflow that dispatches a GitHub Actions pipeline to close, merge, or approve PRs. - [Manage GitHub pull requests](/guides/all/manage-pull-requests.md): Enable agents and developers to manage GitHub pull requests from Port using a workflow that dispatches a GitHub Actions pipeline to close, merge, or approve PRs. #### manage-your-eks-clusters Enable agents and developers to create, request, deploy to, tag, and delete Amazon EKS clusters using Port workflows. - [Manage EKS clusters](/guides/all/manage-your-eks-clusters.md): Enable agents and developers to create, request, deploy to, tag, and delete Amazon EKS clusters using Port workflows. #### manage-your-kubernetes-deployment Restart Kubernetes deployments, change replica counts, and delete pods with a self-service Port workflow that dispatches GitHub Actions through the GitHub Ocean integration. - [Manage your Kubernetes deployments](/guides/all/manage-your-kubernetes-deployment.md): Restart Kubernetes deployments, change replica counts, and delete pods with a self-service Port workflow that dispatches GitHub Actions through the GitHub Ocean integration. #### map-external-users-and-teams-to-port-accounts Enable agents and developers to link external user and team identities to Port accounts for accurate ownership, access, and workflow routing. - [Map external tool users and teams to Port accounts](/guides/all/map-external-users-and-teams-to-port-accounts.md): Enable agents and developers to link external user and team identities to Port accounts for accurate ownership, access, and workflow routing. #### map-prs-to-services-in-monorepo Enable agents and developers to automatically map pull requests to services in a monorepo using file path analysis through Port's agentic SDLC platform. - [Map PRs to services in a monorepo](/guides/all/map-prs-to-services-in-monorepo.md): Enable agents and developers to automatically map pull requests to services in a monorepo using file path analysis through Port's agentic SDLC platform. #### measure-ai-feedback Enable agents and developers to collect and analyze feedback on AI tools using Port actions, automations, and AI agents to measure effectiveness and guide adoption decisions. - [Measure AI feedback](/guides/all/measure-ai-feedback.md): Enable agents and developers to collect and analyze feedback on AI tools using Port actions, automations, and AI agents to measure effectiveness and guide adoption decisions. #### measure-pipeline-reliability Enable agents and developers to measure CI/CD pipeline reliability at service and team level, including failure rates, failure trends, and failing pipeline identification, using Port's integrations and dashboards. - [Measure pipeline reliability](/guides/all/measure-pipeline-reliability.md): Enable agents and developers to measure CI/CD pipeline reliability at service and team level, including failure rates, failure trends, and failing pipeline identification, using Port's integrations and dashboards. #### measure-pr-delivery-metrics Enable agents and developers to measure PR and MR delivery metrics at service and team level, including cycle time, throughput, stale PRs/MRs, and reviewer coverage, using Port's GitHub Ocean or GitLab integration and dashboards. - [Measure PR delivery metrics](/guides/all/measure-pr-delivery-metrics.md): Enable agents and developers to measure PR and MR delivery metrics at service and team level, including cycle time, throughput, stale PRs/MRs, and reviewer coverage, using Port's GitHub Ocean or GitLab integration and dashboards. #### measure-pull-request-standards Enable agents and developers to implement working agreements and measure pull request standards using Port scorecards and aggregation properties, tracking team performance based on PR metrics like review time, approval count, and merge latency. - [Measuring pull request standards](/guides/all/measure-pull-request-standards.md): Enable agents and developers to implement working agreements and measure pull request standards using Port scorecards and aggregation properties, tracking team performance based on PR metrics like review time, approval count, and merge latency. #### measure-reliability-and-stability Enable agents and developers to measure reliability and stability of your delivery pipeline by tracking workflow failure rates and PRs blocked by failing CI/CD using Port's GitHub integration. - [Measure delivery reliability and stability](/guides/all/measure-reliability-and-stability.md): Enable agents and developers to measure reliability and stability of your delivery pipeline by tracking workflow failure rates and PRs blocked by failing CI/CD using Port's GitHub integration. #### measure-sprint-health-with-jira Enable agents and developers to evaluate sprint health using Jira metrics, Port dashboards, and scorecards. - [Measure sprint health with Jira](/guides/all/measure-sprint-health-with-jira.md): Enable agents and developers to evaluate sprint health using Jira metrics, Port dashboards, and scorecards. #### measure-standards Enable agents and developers to measure standards compliance across your software delivery, tracking quality, security, and organizational alignment using Port's GitHub integration and scorecards. - [Track standards adherence](/guides/all/measure-standards.md): Enable agents and developers to measure standards compliance across your software delivery, tracking quality, security, and organizational alignment using Port's GitHub integration and scorecards. #### migrate-project-from-github-to-gitlab Enable agents and developers to migrate repositories from GitHub to GitLab using a Port workflow and GitHub Actions. - [Migrate repositories from GitHub to GitLab using Port workflows](/guides/all/migrate-project-from-github-to-gitlab.md): Enable agents and developers to migrate repositories from GitHub to GitLab using a Port workflow and GitHub Actions. #### monitor-integrations Enable agents and developers to monitor and manage your Port Ocean integrations for improved visibility and performance tracking. - [Monitor integrations](/guides/all/monitor-integrations.md): Enable agents and developers to monitor and manage your Port Ocean integrations for improved visibility and performance tracking. #### move-port-configurations-between-environments-with-port-ai-and-github-mcp Enable agents and developers to back up Port blueprints and actions to GitHub from one environment and import them into another environment using Port AI and GitHub MCP. - [Sync Port configurations between environments using Port AI and MCP](/guides/all/move-port-configurations-between-environments-with-port-ai-and-github-mcp.md): Enable agents and developers to back up Port blueprints and actions to GitHub from one environment and import them into another environment using Port AI and GitHub MCP. #### notify-users-upon-approval-of-action Enable agents and developers to close the request feedback loop with automated Slack notifications for approved or declined Port actions. - [Notify users upon approval of self-service actions](/guides/all/notify-users-upon-approval-of-action.md): Enable agents and developers to close the request feedback loop with automated Slack notifications for approved or declined Port actions. #### nudge-pr-reviewers-with-port-workflows Enable agents and developers to keep pull request reviews moving with automated reminders from Port Workflows. - [Nudge Pull Request Reviewers (Port Workflows)](/guides/all/nudge-pr-reviewers-with-port-workflows.md): Enable agents and developers to keep pull request reviews moving with automated reminders from Port Workflows. #### onboard-developers-from-internal-docs-using-port-mcp Enable agents and developers to set up onboarding guidance in Port and Cursor using Port MCP, a connected Notion MCP connector, and a custom onboarding skill. - [Onboard developers using internal docs and Port MCP](/guides/all/onboard-developers-from-internal-docs-using-port-mcp.md): Enable agents and developers to set up onboarding guidance in Port and Cursor using Port MCP, a connected Notion MCP connector, and a custom onboarding skill. #### owasp-top-10-scorecard Enable agents and developers to build an OWASP Top 10 security scorecard in Port using vulnerability data from Snyk. - [Build an OWASP Top 10 Scorecard](/guides/all/owasp-top-10-scorecard.md): Enable agents and developers to build an OWASP Top 10 security scorecard in Port using vulnerability data from Snyk. #### prepare-work-items-with-ai Enable agents and developers to use Port AI to enrich work items with context lake data, prepare them for human review, and route approved tickets to coding agents. - [Prepare work items with AI](/guides/all/prepare-work-items-with-ai.md): Enable agents and developers to use Port AI to enrich work items with context lake data, prepare them for human review, and route approved tickets to coding agents. #### promote-to-production-workflow Enable agents and developers to build a "Promote to production" flow using Port Workflows and GitHub Actions, with safety checks, deployment tracking, automated PagerDuty incident creation, and team notifications. - [Promote to production workflow](/guides/all/promote-to-production-workflow.md): Enable agents and developers to build a "Promote to production" flow using Port Workflows and GitHub Actions, with safety checks, deployment tracking, automated PagerDuty incident creation, and team notifications. #### provision-azure-resources-with-ado-mcp Build a Port workflow that reads real Terraform module source from Azure DevOps via MCP, then triggers a Claude Code pipeline to open a pull request that follows your module conventions. - [Provision Azure resources from Terraform with Azure DevOps MCP](/guides/all/provision-azure-resources-with-ado-mcp.md): Build a Port workflow that reads real Terraform module source from Azure DevOps via MCP, then triggers a Claude Code pipeline to open a pull request that follows your module conventions. #### provision-cloud-resources-with-agentic-iac-workflow Build a self-service workflow that fetches service context, drafts an IaC implementation plan with AI, and opens a real pull request against your GitOps repository. - [Provision cloud resources with an agentic IaC workflow](/guides/all/provision-cloud-resources-with-agentic-iac-workflow.md): Build a self-service workflow that fetches service context, drafts an IaC implementation plan with AI, and opens a real pull request against your GitOps repository. #### query-dora-metrics-using-port-mcp Enable agents and developers to query DORA performance data from their IDE using Port MCP. - [Query DORA metrics using Port MCP](/guides/all/query-dora-metrics-using-port-mcp.md): Enable agents and developers to query DORA performance data from their IDE using Port MCP. #### remediate-ci-cd-failures-with-port-cursor-workflow Enable agents and developers to automatically remediate failed CI workflow runs by orchestrating Port, Cursor automations, and Slack notifications. - [Remediate CI/CD failures with Port AI & Cursor](/guides/all/remediate-ci-cd-failures-with-port-cursor-workflow.md): Enable agents and developers to automatically remediate failed CI workflow runs by orchestrating Port, Cursor automations, and Slack notifications. #### remediate-vulnerability-with-ai Use a Port workflow with AI and Claude Code to enrich critical security vulnerabilities and trigger automated fixes - [Remediate vulnerabilities with AI](/guides/all/remediate-vulnerability-with-ai.md): Use a Port workflow with AI and Claude Code to enrich critical security vulnerabilities and trigger automated fixes #### remediate-vulnerability-with-n8n-and-port Enable agents and developers to use Port as a context lake for n8n workflows to enrich vulnerability management with service metadata, ownership, and dependencies. - [Remediate security vulnerability with n8n and Port AI](/guides/all/remediate-vulnerability-with-n8n-and-port.md): Enable agents and developers to use Port as a context lake for n8n workflows to enrich vulnerability management with service metadata, ownership, and dependencies. #### report-a-bug Enable agents and developers to report bugs in Jira through a governed Port workflow. - [Report a bug](/guides/all/report-a-bug.md): Enable agents and developers to report bugs in Jira through a governed Port workflow. #### respond-to-new-relic-alerts Enable agents and developers to respond to New Relic alerts by creating Jira issues or PagerDuty incidents through Port. - [Respond to New Relic alerts](/guides/all/respond-to-new-relic-alerts.md): Enable agents and developers to respond to New Relic alerts by creating Jira issues or PagerDuty incidents through Port. #### rollback-argocd-deployment Enable agents and developers to deploy or roll back Argo CD workloads through a governed Port workflow backed by GitHub Actions. - [Roll back an ArgoCD deployment via GitHub Actions](/guides/all/rollback-argocd-deployment.md): Enable agents and developers to deploy or roll back Argo CD workloads through a governed Port workflow backed by GitHub Actions. #### route-scorecard-failures-to-jira-issues Turn failing scorecard rules into routed Jira issues with Port workflows and Port AI. - [Route scorecard failures to Jira issues with AI](/guides/all/route-scorecard-failures-to-jira-issues.md): Turn failing scorecard rules into routed Jira issues with Port workflows and Port AI. #### scaffold-a-new-service-with-port-workflows Enable agents and developers to scaffold new services through governed Port Workflows. - [Scaffold a new service](/guides/all/scaffold-a-new-service-with-port-workflows.md): Enable agents and developers to scaffold new services through governed Port Workflows. #### scaffold-a-new-service Enable agents and developers to scaffold production-ready services through governed Port self-service actions. - [Scaffold a new service with Actions](/guides/all/scaffold-a-new-service.md): Enable agents and developers to scaffold production-ready services through governed Port self-service actions. #### scaffold-repositories-using-cookiecutter Enable agents and developers to scaffold GitHub, Bitbucket, and Azure DevOps repositories using Cookiecutter templates via Port self-service actions. - [Scaffold repositories using Cookiecutter](/guides/all/scaffold-repositories-using-cookiecutter.md): Enable agents and developers to scaffold GitHub, Bitbucket, and Azure DevOps repositories using Cookiecutter templates via Port self-service actions. #### self-heal-scorecards-with-ai Enable agents and developers to use Port's AI capabilities to detect scorecard degradation and automatically use a coding agent like GitHub Copilot to fix it. - [Auto-fix services when scorecards degrade](/guides/all/self-heal-scorecards-with-ai.md): Enable agents and developers to use Port's AI capabilities to detect scorecard degradation and automatically use a coding agent like GitHub Copilot to fix it. #### send-slack-message-to-user Enable agents and developers to send Slack messages to users using Port's Slack app and Port Workflows. - [Send Slack messages to users using Port Workflows](/guides/all/send-slack-message-to-user.md): Enable agents and developers to send Slack messages to users using Port's Slack app and Port Workflows. #### setup-branch-protection-rules Enable agents and developers to enforce repository governance by evaluating GitHub branch protection rules with Port scorecards. - [Enforce branch protection rules with scorecards](/guides/all/setup-branch-protection-rules.md): Enable agents and developers to enforce repository governance by evaluating GitHub branch protection rules with Port scorecards. #### setup-delivery-performance-scorecard Enable agents and developers to set up Delivery Performance scorecards in Port to grade services, teams, groups, and organizations on PR/MR throughput, cycle time, and stale PR/MR management using Bronze, Silver, and Gold maturity levels. - [Set up delivery performance scorecards](/guides/all/setup-delivery-performance-scorecard.md): Enable agents and developers to set up Delivery Performance scorecards in Port to grade services, teams, groups, and organizations on PR/MR throughput, cycle time, and stale PR/MR management using Bronze, Silver, and Gold maturity levels. #### setup-dora-metrics-jira Enable agents and developers to configure DORA metrics using Jira issues as the deployment and incident source instead of GitHub and PagerDuty through Port's agentic SDLC platform. - [Set up deployments and incidents using Jira issues](/guides/all/setup-dora-metrics-jira.md): Enable agents and developers to configure DORA metrics using Jira issues as the deployment and incident source instead of GitHub and PagerDuty through Port's agentic SDLC platform. #### setup-dora-metrics Set up DORA metrics in Port: model deployments and incidents, then build a dashboard tracking all four delivery metrics. - [Track DORA metrics](/guides/all/setup-dora-metrics.md): Set up DORA metrics in Port: model deployments and incidents, then build a dashboard tracking all four delivery metrics. #### setup-engineering-intelligence-data-model Enable agents and developers to build Port's Engineering Intelligence data model across organizations, teams, services, and repositories. - [Create foundational Engineering Intelligence data model](/guides/all/setup-engineering-intelligence-data-model.md): Enable agents and developers to build Port's Engineering Intelligence data model across organizations, teams, services, and repositories. #### setup-incident-manager-ai-agent Enable agents and developers to set up an Incident Manager AI agent to help developers track and manage incidents efficiently through Port's agentic SDLC platform. - [Set up the Incident Manager AI agent](/guides/all/setup-incident-manager-ai-agent.md): Enable agents and developers to set up an Incident Manager AI agent to help developers track and manage incidents efficiently through Port's agentic SDLC platform. #### setup-pci-dss-code-compliance Enable agents and developers to measure PCI DSS code security compliance using Snyk data and Port scorecards. - [PCI DSS code security scorecard](/guides/all/setup-pci-dss-code-compliance.md): Enable agents and developers to measure PCI DSS code security compliance using Snyk data and Port scorecards. #### setup-pipeline-reliability-scorecard Enable agents and developers to set up Pipeline Reliability scorecards in Port to grade services, teams, groups, and organizations on CI/CD workflow failure rates and reliability trends using Bronze, Silver, and Gold maturity levels. - [Set up pipeline reliability scorecards](/guides/all/setup-pipeline-reliability-scorecard.md): Enable agents and developers to set up Pipeline Reliability scorecards in Port to grade services, teams, groups, and organizations on CI/CD workflow failure rates and reliability trends using Bronze, Silver, and Gold maturity levels. #### setup-platform-request-triage-ai-agent Enable agents and developers to set up a Platform Request Triage AI agent to help developers submit and track requests to the platform team through Port's agentic SDLC platform. - [Set up the Platform Request Triage AI agent](/guides/all/setup-platform-request-triage-ai-agent.md): Enable agents and developers to set up a Platform Request Triage AI agent to help developers submit and track requests to the platform team through Port's agentic SDLC platform. #### setup-pr-enricher-ai-agent Enable agents and developers to set up a Pull Request Enricher using Port Workflows to automatically comment on pull requests with additional context. - [Enrich pull requests using AI](/guides/all/setup-pr-enricher-ai-agent.md): Enable agents and developers to set up a Pull Request Enricher using Port Workflows to automatically comment on pull requests with additional context. #### setup-prd-agent-for-ticket-triage Enable agents and developers to turn thin tickets into clear specifications and route them to AI coding agents or people through governed Port workflows. - [Set up a PRD agent for ticket triage](/guides/all/setup-prd-agent-for-ticket-triage.md): Enable agents and developers to turn thin tickets into clear specifications and route them to AI coding agents or people through governed Port workflows. #### setup-production-readiness-scorecard Build Bronze to Gold production readiness checks on services so you can enforce ownership, documentation, and repository hygiene. - [Set up a service production readiness scorecard](/guides/all/setup-production-readiness-scorecard.md): Build Bronze to Gold production readiness checks on services so you can enforce ownership, documentation, and repository hygiene. #### setup-service-explorer-ai-agent Enable agents and developers to set up a Service Explorer AI agent with MCP to help developers discover services, understand ownership, and access documentation for quick onboarding through Port's agentic SDLC platform. - [Set up the Service Explorer AI agent](/guides/all/setup-service-explorer-ai-agent.md): Enable agents and developers to set up a Service Explorer AI agent with MCP to help developers discover services, understand ownership, and access documentation for quick onboarding through Port's agentic SDLC platform. #### setup-slack-reminders Enable agents and developers to deliver scheduled Slack reminders through Port automations. - [Slack reminders for scorecards](/guides/all/setup-slack-reminders.md): Enable agents and developers to deliver scheduled Slack reminders through Port automations. #### setup-task-manager-ai-agent Enable agents and developers to set up a Task Manager AI agent to help developers track and manage tasks efficiently through Port's agentic SDLC platform. - [Set up the Task Manager AI agent](/guides/all/setup-task-manager-ai-agent.md): Enable agents and developers to set up a Task Manager AI agent to help developers track and manage tasks efficiently through Port's agentic SDLC platform. #### smart-pr-reviewer-assignment-using-port-ai Enable agents and developers to automatically assign qualified PR reviewers using Port AI, CODEOWNERS, ownership data, and capacity constraints. - [Smart PR reviewer assignment using AI](/guides/all/smart-pr-reviewer-assignment-using-port-ai.md): Enable agents and developers to automatically assign qualified PR reviewers using Port AI, CODEOWNERS, ownership data, and capacity constraints. #### streamline-iac-with-ai Enable agents and developers to use Port AI agents with AI coding assistants to streamline Infrastructure as Code (IaC) by automatically provisioning cloud resources like S3 buckets. - [Streamline IaC with AI](/guides/all/streamline-iac-with-ai.md): Enable agents and developers to use Port AI agents with AI coding assistants to streamline Infrastructure as Code (IaC) by automatically provisioning cloud resources like S3 buckets. #### surface-resource-actions-from-jira-with-ai Enable agents and developers to use Port's AI agent to analyze Jira issues and surface relevant self-service actions for cloud resources and permissions. - [Surface resource actions from Jira with AI](/guides/all/surface-resource-actions-from-jira-with-ai.md): Enable agents and developers to use Port's AI agent to analyze Jira issues and surface relevant self-service actions for cloud resources and permissions. #### sync-port-properties-to-github-external-custom-properties Sync Port property values to GitHub external custom properties, so you can search repositories and build GitHub rulesets on top of business context that lives in Port. - [Sync Port properties to GitHub external custom properties](/guides/all/sync-port-properties-to-github-external-custom-properties.md): Sync Port property values to GitHub external custom properties, so you can search repositories and build GitHub rulesets on top of business context that lives in Port. #### sync-service-entities-to-incident-io Enable agents and developers to use Port service context during incidents by synchronizing entities to incident.io. - [Sync Port services to incident.io](/guides/all/sync-service-entities-to-incident-io.md): Enable agents and developers to use Port service context during incidents by synchronizing entities to incident.io. #### terraform-plan-and-apply-aws-resource Enable agents and developers to plan and apply AWS infrastructure through governed Port self-service actions backed by Terraform. - [Provision Cloud Resource using Terraform Plan and Apply](/guides/all/terraform-plan-and-apply-aws-resource.md): Enable agents and developers to plan and apply AWS infrastructure through governed Port self-service actions backed by Terraform. #### track-ai-adoption-and-impact Enable agents and developers to track AI adoption across engineering teams and assess the impact of AI usage on delivery metrics like PR throughput and cycle time using Port's GitHub Ocean integration. - [Track AI adoption and impact](/guides/all/track-ai-adoption-and-impact.md): Enable agents and developers to track AI adoption across engineering teams and assess the impact of AI usage on delivery metrics like PR throughput and cycle time using Port's GitHub Ocean integration. #### track-ai-coding-assistants-costs Enable agents and developers to build a unified dashboard to analyze and compare AI coding tool costs across Cursor, Claude, and GitHub Copilot using data already ingested into Port. - [Track AI coding assistants costs](/guides/all/track-ai-coding-assistants-costs.md): Enable agents and developers to build a unified dashboard to analyze and compare AI coding tool costs across Cursor, Claude, and GitHub Copilot using data already ingested into Port. #### track-ai-driven-pull-requests Enable agents and developers to track and monitor AI-driven pull requests in your development workflow using Port's context lake and automation capabilities. - [Track AI-driven pull requests](/guides/all/track-ai-driven-pull-requests.md): Enable agents and developers to track and monitor AI-driven pull requests in your development workflow using Port's context lake and automation capabilities. #### track-and-show-mtbf-for-services Enable agents and developers to track Mean Time Between Failures (MTBF) for your Pagerduty services to measure reliability and identify improvement opportunities through Port's agentic SDLC platform. - [Track and show MTBF for services](/guides/all/track-and-show-mtbf-for-services.md): Enable agents and developers to track Mean Time Between Failures (MTBF) for your Pagerduty services to measure reliability and identify improvement opportunities through Port's agentic SDLC platform. #### track-gitlab-project-maturity-with-scorecards Enable agents and developers to enforce GitLab repository maturity standards using file-search signals and Port scorecards. - [Enforce code maturity with GitLab file search](/guides/all/track-gitlab-project-maturity-with-scorecards.md): Enable agents and developers to enforce GitLab repository maturity standards using file-search signals and Port scorecards. #### track-health-of-jira-projects Enable agents and developers to identify project risks by evaluating Jira issue hygiene and operational readiness with Port scorecards. - [Set up Jira project health scorecards](/guides/all/track-health-of-jira-projects.md): Enable agents and developers to identify project risks by evaluating Jira issue hygiene and operational readiness with Port scorecards. #### track-leaked-github-secrets-in-port Enable agents and developers to send leaked application secrets from GitHub to Port using Gitleaks. - [Track leaked GitHub secrets in Port](/guides/all/track-leaked-github-secrets-in-port.md): Enable agents and developers to send leaked application secrets from GitHub to Port using Gitleaks. #### track-slos-and-slis-for-services Enable agents and developers to track SLOs and SLIs for your services using Port. - [Track SLOs and SLIs for your services](/guides/all/track-slos-and-slis-for-services.md): Enable agents and developers to track SLOs and SLIs for your services using Port. #### track-team-work-allocation-with-jira Enable agents and developers to measure and visualize work allocation across Roadmap, Tech Debt, and Support categories at the team level using Jira labels and Port dashboards. - [Track team work allocation with Jira](/guides/all/track-team-work-allocation-with-jira.md): Enable agents and developers to measure and visualize work allocation across Roadmap, Tech Debt, and Support categories at the team level using Jira labels and Port dashboards. #### triage-incidents-with-dynatrace-mcp Triage incidents using AI, Dynatrace MCP, GitHub MCP, and Slack - fetch live telemetry with DQL, correlate code context, and post a structured root-cause summary from Port AI. - [Triage incidents with Dynatrace MCP](/guides/all/triage-incidents-with-dynatrace-mcp.md): Triage incidents using AI, Dynatrace MCP, GitHub MCP, and Slack - fetch live telemetry with DQL, correlate code context, and post a structured root-cause summary from Port AI. #### triage-incidents-with-mcp Enable agents and developers to triage incidents in Port AI using live Sentry errors, GitHub code context, and structured root-cause summaries in Slack. - [Triage incidents using external MCP tools](/guides/all/triage-incidents-with-mcp.md): Enable agents and developers to triage incidents in Port AI using live Sentry errors, GitHub code context, and structured root-cause summaries in Slack. #### trigger-ai-coding-assistants-from-port Learn how to trigger GitHub Copilot, Claude Code, and Google Gemini Assistant from Port using governed workflows. - [Trigger AI coding assistants from Port](/guides/all/trigger-ai-coding-assistants-from-port.md): Learn how to trigger GitHub Copilot, Claude Code, and Google Gemini Assistant from Port using governed workflows. #### trigger-datadog-incident-with-port-workflows Trigger a Datadog incident from a Port self-service workflow and sync it to your software catalog. - [Trigger Datadog incident (Workflows)](/guides/all/trigger-datadog-incident-with-port-workflows.md): Trigger a Datadog incident from a Port self-service workflow and sync it to your software catalog. #### trigger-datadog-incident Enable agents and developers to initiate Datadog incident response through a governed Port self-service action. - [Trigger Datadog Incident](/guides/all/trigger-datadog-incident.md): Enable agents and developers to initiate Datadog incident response through a governed Port self-service action. #### trigger-spacelift-stack Enable agents and developers to trigger a Spacelift stack in Port to automate infrastructure workflows. - [Trigger a Spacelift stack](/guides/all/trigger-spacelift-stack.md): Enable agents and developers to trigger a Spacelift stack in Port to automate infrastructure workflows. #### visualize-and-manage-azure-devops-deployments Enable agents and developers to monitor and manage your Azure DevOps deployments using dashboards and self-service actions in Port. - [Visualize and manage your Azure DevOps deployments](/guides/all/visualize-and-manage-azure-devops-deployments.md): Enable agents and developers to monitor and manage your Azure DevOps deployments using dashboards and self-service actions in Port. #### visualize-and-manage-git-deployments Enable agents and developers to ingest, visualize, and manage GitHub and GitLab deployments with dashboards and self-service actions in Port. - [Visualize and manage Git deployments](/guides/all/visualize-and-manage-git-deployments.md): Enable agents and developers to ingest, visualize, and manage GitHub and GitLab deployments with dashboards and self-service actions in Port. #### visualize-and-manage-servicenow-incidents Enable agents and developers to monitor and manage your ServiceNow incidents using dashboards and Port workflows. - [Visualize and manage your ServiceNow incidents](/guides/all/visualize-and-manage-servicenow-incidents.md): Enable agents and developers to monitor and manage your ServiceNow incidents using dashboards and Port workflows. #### visualize-and-manage-statuspage-incidents Enable agents and developers to monitor and manage your Statuspage incidents and components using dashboards and self-service actions in Port. - [Visualize and manage your Statuspage incidents and components](/guides/all/visualize-and-manage-statuspage-incidents.md): Enable agents and developers to monitor and manage your Statuspage incidents and components using dashboards and self-service actions in Port. #### visualize-claude-metrics Enable agents and developers to create dashboards to monitor Claude API usage, track costs, analyze model performance, and measure workspace-level metrics through Port's agentic SDLC platform. - [Visualize Claude metrics](/guides/all/visualize-claude-metrics.md): Enable agents and developers to create dashboards to monitor Claude API usage, track costs, analyze model performance, and measure workspace-level metrics through Port's agentic SDLC platform. #### visualize-claude-skills-adoption Visualize how Claude Skills are adopted, shared and reused across your organization, which skills become part of regular workflows, and where skill-related spend is concentrated, using Port's Claude integration and dashboards. - [Visualize Claude Skills adoption and usage](/guides/all/visualize-claude-skills-adoption.md): Visualize how Claude Skills are adopted, shared and reused across your organization, which skills become part of regular workflows, and where skill-related spend is concentrated, using Port's Claude integration and dashboards. #### visualize-cursor-metrics Enable agents and developers to visualize Cursor adoption, suggestion acceptance, and engineering impact at the user, team, and organization level using Port's native Cursor integration and dashboards. - [Visualize Cursor metrics](/guides/all/visualize-cursor-metrics.md): Enable agents and developers to visualize Cursor adoption, suggestion acceptance, and engineering impact at the user, team, and organization level using Port's native Cursor integration and dashboards. #### visualize-github-copilot-metrics Enable agents and developers to visualize GitHub Copilot adoption, suggestion acceptance, and engineering impact at the user, team, and organization level using Port's GitHub Copilot integration and dashboards. - [Visualize GitHub Copilot metrics](/guides/all/visualize-github-copilot-metrics.md): Enable agents and developers to visualize GitHub Copilot adoption, suggestion acceptance, and engineering impact at the user, team, and organization level using Port's GitHub Copilot integration and dashboards. #### visualize-jira-lead-time Enable agents and developers to monitor Jira lead time at the project, service, and team levels using Port dashboards. - [Visualize lead time using Jira](/guides/all/visualize-jira-lead-time.md): Enable agents and developers to monitor Jira lead time at the project, service, and team levels using Port dashboards. #### visualize-okta-security-insights Enable agents and developers to build a security analytics dashboard for Okta identity and access management using Port's integration. - [Visualize Okta security insights](/guides/all/visualize-okta-security-insights.md): Enable agents and developers to build a security analytics dashboard for Okta identity and access management using Port's integration. #### visualize-service-argocd-runtime Enable agents and developers to visualize ArgoCD service runtime in Port, enhancing monitoring and management of your Kubernetes applications. - [Visualize your services' Kubernetes runtime using ArgoCD](/guides/all/visualize-service-argocd-runtime.md): Enable agents and developers to visualize ArgoCD service runtime in Port, enhancing monitoring and management of your Kubernetes applications. #### visualize-service-k8s-runtime Enable agents and developers to visualize Kubernetes service runtime in Port, improving monitoring and management of your cloud-native applications. - [Visualize your services' k8s runtime](/guides/all/visualize-service-k8s-runtime.md): Enable agents and developers to visualize Kubernetes service runtime in Port, improving monitoring and management of your cloud-native applications. #### visualize-your-wiz-vulnerabilities Enable agents and developers to monitor Wiz issues and gain security insights using dashboards through Port's agentic SDLC platform. - [Visualize your Wiz security issues](/guides/all/visualize-your-wiz-vulnerabilities.md): Enable agents and developers to monitor Wiz issues and gain security insights using dashboards through Port's agentic SDLC platform. #### work-item-blueprint Enable agents and developers to connect Jira issues with services, teams, pull requests, and deployments for autonomous ticket resolution. - [Implement the work item blueprint pattern](/guides/all/work-item-blueprint.md): Enable agents and developers to connect Jira issues with services, teams, pull requests, and deployments for autonomous ticket resolution. ## glossary Read precise definitions of Port terms such as blueprint, entity, and scorecard so you apply them correctly in setup and support. - [Glossary](/glossary.md): Read precise definitions of Port terms such as blueprint, entity, and scorecard so you apply them correctly in setup and support. ## solutions ### agentic-resource-management #### common-use-cases This is a catalog of common use cases we see deliver value across our customers. - [Common use cases](/solutions/agentic-resource-management/common-use-cases.md): This is a catalog of common use cases we see deliver value across our customers. #### getting-started This walkthrough shows how to build an agentic workflow that provisions a new cloud resource using Infrastructure as Code (IaC). A developer or agent expresses the intent to create a resource, and the workflow fetches context, generates an implementation plan, creates a resource request, and opens a pull request against your GitOps repository. - [Getting started](/solutions/agentic-resource-management/getting-started.md): This walkthrough shows how to build an agentic workflow that provisions a new cloud resource using Infrastructure as Code (IaC). A developer or agent expresses the intent to create a resource, and the workflow fetches context, generates an implementation plan, creates a resource request, and opens a pull request against your GitOps repository. #### golden-paths Golden paths are the foundation of agentic resource management. They are how you deliver engineering velocity without giving up governance, for both developers and AI agents. - [Golden paths](/solutions/agentic-resource-management/golden-paths.md): Golden paths are the foundation of agentic resource management. They are how you deliver engineering velocity without giving up governance, for both developers and AI agents. #### governance-at-scale As an organization scales, golden path workflows for day-0 and day-2 actions are no longer enough on their own. Thousands of resources across dozens of teams need oversight that doesn't depend on any one person watching every request. A few patterns help you keep control without becoming the bottleneck. - [Governance at scale](/solutions/agentic-resource-management/governance-at-scale.md): As an organization scales, golden path workflows for day-0 and day-2 actions are no longer enough on their own. Thousands of resources across dozens of teams need oversight that doesn't depend on any one person watching every request. A few patterns help you keep control without becoming the bottleneck. #### multi-cloud Golden paths and guardrails are only as good as their coverage. If they only reach one cloud, the gaps in every other environment keep the too-slow / too-loose tension alive. - [Multi-cloud single pane of glass](/solutions/agentic-resource-management/multi-cloud.md): Golden paths and guardrails are only as good as their coverage. If they only reach one cloud, the gaps in every other environment keep the too-slow / too-loose tension alive. #### overview Give developers and agents Port golden paths for infrastructure so you provision and decommission under platform team standards. - [Agentic resource management](/solutions/agentic-resource-management/overview.md): Give developers and agents Port golden paths for infrastructure so you provision and decommission under platform team standards. ### autonomous-ticket-resolution #### agentic-initiatives Run one coding agent across every service that needs the same change, from a single governed initiative, tracked per service and as a portfolio. - [Agentic initiatives](/solutions/autonomous-ticket-resolution/agentic-initiatives.md): Run one coding agent across every service that needs the same change, from a single governed initiative, tracked per service and as a portfolio. ##### getting-started Build an agentic initiative that fans a coding agent out across every service failing a scorecard rule, with per-service tracking and portfolio-level progress. - [Getting started with agentic initiatives](/solutions/autonomous-ticket-resolution/agentic-initiatives/getting-started.md): Build an agentic initiative that fans a coding agent out across every service failing a scorecard rule, with per-service tracking and portfolio-level progress. #### code-review Enrich PRs with service context, assign smart reviewers, send review nudges, and track security review outputs in your catalog. - [Review the results](/solutions/autonomous-ticket-resolution/code-review.md): Enrich PRs with service context, assign smart reviewers, send review nudges, and track security review outputs in your catalog. #### getting-started-with-atr Build your first end-to-end Autonomous Ticket Resolution workflow. A Jira ticket arrives thin, gets enriched with catalog context, is scored for AI readiness, and is delegated to Cursor with one click. - [Getting started with your first Autonomous Ticket Resolution agentic workflow](/solutions/autonomous-ticket-resolution/getting-started-with-atr.md): Build your first end-to-end Autonomous Ticket Resolution workflow. A Jira ticket arrives thin, gets enriched with catalog context, is scored for AI readiness, and is delegated to Cursor with one click. #### overview Follow Port's autonomous ticket flow from triage to shipping, letting AI route enriched work while you retain key decision gates. - [Autonomous ticket resolution](/solutions/autonomous-ticket-resolution/overview.md): Follow Port's autonomous ticket flow from triage to shipping, letting AI route enriched work while you retain key decision gates. #### roi-dashboard Measure the impact of Autonomous Ticket Resolution (ATR) in Port with an ROI dashboard covering tickets resolved, time saved, and cost impact. - [Measure ATR's impact](/solutions/autonomous-ticket-resolution/roi-dashboard.md): Measure the impact of Autonomous Ticket Resolution (ATR) in Port with an ROI dashboard covering tickets resolved, time saved, and cost impact. #### safe-release Deploy code safely with PR enrichment, smart reviewer assignment, security review tracking, and automated review nudges. - [Release safely with control](/solutions/autonomous-ticket-resolution/safe-release.md): Deploy code safely with PR enrichment, smart reviewer assignment, security review tracking, and automated review nudges. #### turn-tickets-into-actionable-work Enrich Jira tickets with context, evaluate AI delegation eligibility, and produce routing decisions with supporting documentation. - [Turn tickets into actionable work](/solutions/autonomous-ticket-resolution/turn-tickets-into-actionable-work.md): Enrich Jira tickets with context, evaluate AI delegation eligibility, and produce routing decisions with supporting documentation. ##### overview Transform thin tickets into actionable work items with service context, blast radius, PRDs, and AI routing decisions. - [Ticket preparation](/solutions/autonomous-ticket-resolution/turn-tickets-into-actionable-work/overview.md): Transform thin tickets into actionable work items with service context, blast radius, PRDs, and AI routing decisions. ##### routing-decision Determine AI delegation eligibility with deterministic scorecards and LLM confidence scoring. Route work safely between agents and humans. - [Routing decision](/solutions/autonomous-ticket-resolution/turn-tickets-into-actionable-work/routing-decision.md): Determine AI delegation eligibility with deterministic scorecards and LLM confidence scoring. Route work safely between agents and humans. ##### work-item-blueprint-pattern Create a dedicated Port entity for AI-assisted development that tracks workflow state separately from Jira/Linear/ADO tickets. - [Work item blueprint pattern](/solutions/autonomous-ticket-resolution/turn-tickets-into-actionable-work/work-item-blueprint-pattern.md): Create a dedicated Port entity for AI-assisted development that tracks workflow state separately from Jira/Linear/ADO tickets. #### why-port Port provides catalog context, deterministic routing scorecards, entity persistence, and measurable outcomes for autonomous ticket resolution workflows. - [Why Port?](/solutions/autonomous-ticket-resolution/why-port.md): Port provides catalog context, deterministic routing scorecards, entity persistence, and measurable outcomes for autonomous ticket resolution workflows. ### engineering-intelligence #### ai-adoption Track AI tool adoption rates, measure ROI, and correlate usage with delivery performance improvements across teams. - [AI adoption and impact](/solutions/engineering-intelligence/ai-adoption.md): Track AI tool adoption rates, measure ROI, and correlate usage with delivery performance improvements across teams. ##### ai-adoption-survey Run a recurring AI Adoption & Impact pulse survey to complement usage telemetry with self-reported signal on velocity, time saved, quality, and focus. - [AI adoption survey](/solutions/engineering-intelligence/ai-adoption/ai-adoption-survey.md): Run a recurring AI Adoption & Impact pulse survey to complement usage telemetry with self-reported signal on velocity, time saved, quality, and focus. ##### ai-impact Correlate AI tool adoption with delivery performance, incident frequency, and code quality to measure real engineering outcomes. - [AI impact](/solutions/engineering-intelligence/ai-adoption/ai-impact.md): Correlate AI tool adoption with delivery performance, incident frequency, and code quality to measure real engineering outcomes. ##### ai-tools Monitor Copilot, Cursor, and AI tool usage rates, suggestion acceptance, and adoption distribution across teams for ROI analysis. - [Track AI adoption](/solutions/engineering-intelligence/ai-adoption/ai-tools.md): Monitor Copilot, Cursor, and AI tool usage rates, suggestion acceptance, and adoption distribution across teams for ROI analysis. ##### skills-usage Track Claude Skills adoption, depth of usage, and whether knowledge stays personal or becomes reusable across your organization. - [Skills usage](/solutions/engineering-intelligence/ai-adoption/skills-usage.md): Track Claude Skills adoption, depth of usage, and whether knowledge stays personal or becomes reusable across your organization. #### conversational-insights Query and analyze your context lake with AI — through Port agents, MCP-connected tools, or dashboards and reports. - [Conversational insights](/solutions/engineering-intelligence/conversational-insights.md): Query and analyze your context lake with AI — through Port agents, MCP-connected tools, or dashboards and reports. #### devex-surveys Run developer experience surveys, collect qualitative feedback, and turn developer sentiment into actionable improvement initiatives. - [DevEx surveys](/solutions/engineering-intelligence/devex-surveys.md): Run developer experience surveys, collect qualitative feedback, and turn developer sentiment into actionable improvement initiatives. #### getting-started Four-phase Engineering Intelligence journey from baseline metrics through continuous improvement with scorecards, AI agents, and automations. - [Getting started](/solutions/engineering-intelligence/getting-started.md): Four-phase Engineering Intelligence journey from baseline metrics through continuous improvement with scorecards, AI agents, and automations. #### measure-and-track-standards Measure DORA metrics, delivery performance, pipeline reliability, and production readiness - then enforce standards with scorecards. - [Measure and track standards](/solutions/engineering-intelligence/measure-and-track-standards.md): Measure DORA metrics, delivery performance, pipeline reliability, and production readiness - then enforce standards with scorecards. ##### delivery-performance Track PR throughput, cycle time, and stale PRs — then enforce delivery standards with scorecards graded by maturity tier. - [Delivery performance](/solutions/engineering-intelligence/measure-and-track-standards/delivery-performance.md): Track PR throughput, cycle time, and stale PRs — then enforce delivery standards with scorecards graded by maturity tier. ##### dora-metrics Measure the four DORA metrics per service and team, then enforce delivery maturity with DORA scorecards. - [DORA metrics](/solutions/engineering-intelligence/measure-and-track-standards/dora-metrics.md): Measure the four DORA metrics per service and team, then enforce delivery maturity with DORA scorecards. ##### pipeline-reliability Track CI/CD pipeline health and failure trends — then enforce reliability standards with scorecards and automated remediation. - [Reliability](/solutions/engineering-intelligence/measure-and-track-standards/pipeline-reliability.md): Track CI/CD pipeline health and failure trends — then enforce reliability standards with scorecards and automated remediation. ##### production-readiness Score services on ownership, documentation, monitoring, security compliance, and infrastructure hygiene with Bronze/Silver/Gold maturity levels. - [Production readiness](/solutions/engineering-intelligence/measure-and-track-standards/production-readiness.md): Score services on ownership, documentation, monitoring, security compliance, and infrastructure hygiene with Bronze/Silver/Gold maturity levels. #### overview Track DORA, delivery, reliability, and developer experience in Port, then find bottlenecks and improve from catalog-linked data. - [Engineering Intelligence](/solutions/engineering-intelligence/overview.md): Track DORA, delivery, reliability, and developer experience in Port, then find bottlenecks and improve from catalog-linked data. #### why-port Port combines engineering intelligence with orchestration on a unified catalog. Close the loop from insight to execution to measured impact. - [Why Port?](/solutions/engineering-intelligence/why-port.md): Port combines engineering intelligence with orchestration on a unified catalog. Close the loop from insight to execution to measured impact. ### overview Browse Port solutions for resource management, incidents, engineering intelligence, and ticket resolution with humans and agents. - [Solutions overview](/solutions/overview.md): Browse Port solutions for resource management, incidents, engineering intelligence, and ticket resolution with humans and agents. ### self-healing-incidents #### act-on-response Execute pre-authorized actions inside boundaries the system enforces structurally, so autonomy scales without breaking accountability. - [Act on response](/solutions/self-healing-incidents/act-on-response.md): Execute pre-authorized actions inside boundaries the system enforces structurally, so autonomy scales without breaking accountability. #### detect-incidents Score confidence from converging signals instead of a single threshold, and declare only once that confidence clears a threshold set in advance. - [Detect incidents](/solutions/self-healing-incidents/detect-incidents.md): Score confidence from converging signals instead of a single threshold, and declare only once that confidence clears a threshold set in advance. #### diagnose-incidents Reconstruct what changed and quantify impact on the incident record, so remediation targets the real cause instead of the first plausible one. - [Diagnose incidents](/solutions/self-healing-incidents/diagnose-incidents.md): Reconstruct what changed and quantify impact on the incident record, so remediation targets the real cause instead of the first plausible one. #### learn-from-incidents Turn divergence between expected and observed outcomes into a proposed change, reviewed by a human, before the next incident. - [Learn from incidents](/solutions/self-healing-incidents/learn-from-incidents.md): Turn divergence between expected and observed outcomes into a proposed change, reviewed by a human, before the next incident. #### overview Follow five incident stages in Port so agents detect, diagnose, recommend, act, and learn inside gates your team defines up front. - [Self-healing incidents](/solutions/self-healing-incidents/overview.md): Follow five incident stages in Port so agents detect, diagnose, recommend, act, and learn inside gates your team defines up front. #### recommend-response Score response options against explicit criteria and present a ranked, explainable set, instead of collapsing straight to a single answer. - [Recommend response](/solutions/self-healing-incidents/recommend-response.md): Score response options against explicit criteria and present a ranked, explainable set, instead of collapsing straight to a single answer. ## troubleshooting Resolve Port problems using guides for Ocean integrations, actions, the execution agent, and GitHub, GitLab, or Azure DevOps. - [Troubleshooting](/troubleshooting.md): Resolve Port problems using guides for Ocean integrations, actions, the execution agent, and GitHub, GitLab, or Azure DevOps. ### actions Diagnose self-service actions in Port that are stuck in progress, including action backend configuration and Port execution agent setup for Git providers. - [Actions troubleshooting](/troubleshooting/actions.md): Diagnose self-service actions in Port that are stuck in progress, including action backend configuration and Port execution agent setup for Git providers. ### azure-devops Diagnose Azure DevOps Ocean integration bugs in Port - deleted repositories not reflected, syncs that run with no result, test results not ingesting, and inconsistent file ingestion. - [Azure DevOps integration troubleshooting](/troubleshooting/azure-devops.md): Diagnose Azure DevOps Ocean integration bugs in Port - deleted repositories not reflected, syncs that run with no result, test results not ingesting, and inconsistent file ingestion. ### general Answers to common general questions about Port - account setup, organization management, exporting catalog data, embedding content, and security. - [General troubleshooting](/troubleshooting/general.md): Answers to common general questions about Port - account setup, organization management, exporting catalog data, embedding content, and security. ### github Diagnose GitHub Ocean integration bugs in Port - stale data with live events, entities not deleted, partial PR ingestion, workflow run deletion, missing team relations, and migration from the legacy integration. - [GitHub integration troubleshooting](/troubleshooting/github.md): Diagnose GitHub Ocean integration bugs in Port - stale data with live events, entities not deleted, partial PR ingestion, workflow run deletion, missing team relations, and migration from the legacy integration. ### gitlab Diagnose GitLab Ocean integration bugs in Port, including projects not visible after setting up a group access token and version compatibility issues. - [GitLab integration troubleshooting](/troubleshooting/gitlab.md): Diagnose GitLab Ocean integration bugs in Port, including projects not visible after setting up a group access token and version compatibility issues. ### ocean-integrations Diagnose common Ocean integration issues in Port - installation failures, validation errors, mapping problems, and connectivity between the integration and Port's API. - [Ocean integrations troubleshooting](/troubleshooting/ocean-integrations.md): Diagnose common Ocean integration issues in Port - installation failures, validation errors, mapping problems, and connectivity between the integration and Port's API. ### port-agent Diagnose Port execution agent failures - 401 authentication errors, Kafka consumer group authorization, action execution timeouts, and TLS certificate issues on startup. - [Port execution agent troubleshooting](/troubleshooting/port-agent.md): Diagnose Port execution agent failures - 401 authentication errors, Kafka consumer group authorization, action execution timeouts, and TLS certificate issues on startup. ## Optional - [Port agent guide: API authentication, endpoints, and terminology for building with Port](https://docs.port.io/AGENTS.md): Quick reference for agents: authentication, regional base URLs, common API request patterns, and correct Port terminology. - [Port implementation guides by platform pillar](https://docs.port.io/llms/guides.txt): Browse every surviving Port guide grouped under Context lake, Workflows, Port AI, Agent management, Interface builder, Governance, or Platform administration. - [Port MCP server](https://docs.port.io/ai-interfaces/port-mcp-server/overview): Connect AI assistants to Port context, actions, search, and governed MCP connectors. - [Port MCP server installation](https://docs.port.io/ai-interfaces/port-mcp-server/installation): Configure Claude, Cursor, VS Code, Codex, and other MCP clients with Port. - [Port REST API reference (all endpoints)](https://docs.port.io/api-reference/port-api): Full Port REST API: authentication, base URLs, and every endpoint (entities, blueprints, actions, scorecards, workflows). Individual endpoints are omitted from this index to keep it concise; browse them at this page, or use the machine-readable OpenAPI spec at https://docs.port.io/apispec-port-api.yaml. For a single combined OpenAPI spec across all services (Port API, AI, workflow, asset, integration), use https://docs.port.io/unified-services.yaml.