Port IO
Port.io provides an agentic developer platform designed to reduce engineering friction and accelerate delivery. With customizable software catalogs, automated workflows, and built-in governance, Port enables developers to self-serve while giving platform teams strong visibility and control. Companies use Port to improve productivity, enforce standards, and deliver more reliable software.
Templates by Port IO
Auto-resolve Jira tickets with GitHub Copilot using Port Context
Auto-resolve Jira tickets with coding agents Coding agents can significantly speed up development, but crucial engineering context often gets lost in the process. This guide demonstrates how to use Port as a context lake in n8n workflows to automatically generate GitHub issues from Jira tickets with rich organizational context, ensuring that important information is preserved when assigning them to GitHub Copilot and linking pull requests back to Jira. This setup helps establish a seamless ticket-to-PR workflow, bridging the gap between Jira and GitHub while leveraging Port's comprehensive software catalog as a source of truth. How it works The n8n workflow orchestrates the following steps: Jira trigger — The workflow listens for Jira issue updates via webhook. Condition check — Verifies that the issue status is "In Progress" and has the required label (e.g., "productapproved") without the "copilotassigned" label. Port context extraction — Uses Port's n8n node to query your software catalog for relevant context about services, repositories, teams, dependencies, and documentation related to the Jira issue. Parse response — Retrieves the AI-generated GitHub issue title and body from Port. Create GitHub issue — Creates a new GitHub issue with the enriched context from Port. Assign to Copilot — Adds a comment to the GitHub issue instructing Copilot to take ownership. Add issue link to Jira ticket — Adds a comment to the Jira ticket with the GitHub issue URL, providing clear traceability. Mark ticket as assigned — Updates the Jira ticket to add the "copilot_assigned" label, preventing duplicate processing. Setup [ ] Connect your Jira Cloud account and enable issue_updated events [ ] Register for free on Port.io [ ] Connect your Port.io account and add the API key [ ] Connect your GitHub account and select the target repository [ ] Ensure a Copilot bot or @copilot user has access to the repository [ ] Confirm the workflow webhook or Jira trigger URL is active [ ] Test by moving a product_approved ticket to In Progress. [ ] You should be good to go! Prerequisites You have a Port account and have completed the onboarding process. Port's GitHub app is installed in your account. Port's Jira integration is installed in your account. You have a working n8n instance (Cloud or self-hosted) with Port's n8n custom node installed. Your GitHub organization has GitHub Copilot enabled, so Copilot can be automatically assigned to any issues created through this guide. ⚠️ This template is intended for Self-Hosted instances only.
By Port IOControl AI agent tool access with Port RBAC and Slack mentions
RBAC for AI agents with n8n and Port This workflow implements role-based access control for AI agent tools using Port as the single source of truth for permissions. Different users get access to different tools based on their roles, without needing a separate permission database. For example, developers might have access to PagerDuty and AWS S3, while support staff only gets Wikipedia and a calculator. The workflow checks each user's permissions in Port before letting the agent use any tools. For the full guide with blueprint setup and detailed configuration, see RBAC for AI Agents with n8n and Port in the Port documentation. How it works The n8n workflow orchestrates the following steps: Slack trigger — Listens for @mentions and extracts the user ID from the message. Get user profile — Fetches the user's Slack profile to get their email address. Port authentication — Requests an access token from the Port API using client credentials. Permission lookup — Queries Port for the user entity (by email) and reads their allowed_tools array. Unknown user check — If the user doesn't exist in Port, sends an error message and stops. Permission filtering — The "Check permissions" node compares each connected tool against allowed_tools and replaces unauthorized ones with a stub that returns "You are not authorized to use this tool." AI agent — Runs with only permitted tools, using GPT-4 and chat memory. Response — Posts the agent output back to the Slack channel. Setup [ ] Connect your Slack account and set the channel ID in the trigger node [ ] Add your OpenAI API key [ ] Register for free on Port.io [ ] Create the rbacUser blueprint in Port (see full guide for blueprint setup) [ ] Add user entities using email as the identifier [ ] Replace YOURPORTCLIENTID and YOURPORTCLIENTSECRET in the "Get Port access token" node [ ] Connect credentials for any tools you want to use (PagerDuty, AWS, etc.) [ ] Update the channel ID in the Slack nodes [ ] Invite the bot to your Slack channel [ ] You should be good to go! Prerequisites You have a Port account and have completed the onboarding process. You have a working n8n instance (self-hosted) with LangChain nodes available. Slack workspace with bot permissions to receive mentions and post messages. OpenAI API key for the LangChain agent. Port client ID and secret for API authentication. (Optional) PagerDuty, AWS, or other service credentials for tools you want to control. ⚠️ This template is intended for Self-Hosted instances only.
By Port IOOrchestrate security vulnerability remediation with Port, OpenAI, Jira and Slack
Complete security workflow from vulnerability detection to automated remediation, with severity-based routing and full organizational context from Port's catalog. This template provides end-to-end lifecycle management including automatic Jira ticket creation with appropriate priority, AI-powered remediation planning, and Claude Code-triggered fixes for critical vulnerabilities. The full guide is available here. How it works The n8n workflow orchestrates the following steps: Webhook trigger: Receives vulnerability alerts from security scanners (Snyk, Wiz, SonarQube, etc.) via POST request. Port context enrichment: Uses Port's n8n node to query your software catalog for service metadata, ownership, environment, SLA requirements, and dependencies related to the vulnerability. AI remediation planning: OpenAI analyzes the vulnerability with Port context and generates a remediation plan, determining if automated fixing is possible. Severity-based routing: Routes vulnerabilities through different paths based on severity level: Critical: Jira ticket (Highest priority) → Check if auto-fixable → Trigger Claude Code fix → Slack alert with fix status High: Jira ticket (High priority) → Slack notification to team channel Medium/Low: Jira ticket only for tracking Jira integration: Creates tickets with full context including vulnerability details, affected service information from Port, and AI-generated remediation steps. Claude Code remediation: For auto-fixable critical vulnerabilities, triggers Claude Code via Port action to create a pull request with the security patch, referencing the Jira ticket. Slack notifications: Sends contextual alerts to the appropriate team channel (retrieved from Port) with Jira ticket reference and remediation status. Prerequisites You have a Port account and have completed the onboarding process. Services and repositories are cataloged in Port with ownership information. Your security scanner (Snyk, Wiz, SonarQube) can send webhooks. You have a working n8n instance (Cloud or self-hosted) with Port's n8n custom node installed. Jira Cloud account with appropriate project permissions. Slack workspace with bot permissions to post messages. OpenAI API key for remediation planning. Setup Register for free on Port.io if you haven't already. Create the Context Retriever Agent in Port following the guide. Import the workflow and configure credentials (Port, Jira, Slack, OpenAI, Bearer Auth). Select your Jira project in each Jira node (Critical, High, Medium/Low). Update default-organization/repository with your default repository for Claude Code fixes. Point your security scanner webhook to the workflow URL. Test with a sample vulnerability payload. ⚠️ This template is intended for Self-Hosted instances only.
By Port IO