Workflows & tools
Workflows are currently in open beta. The feature is available to all users, but may undergo changes without prior notice. There is no SLA or guaranteed issue-resolution timeline during this period.
Workflows are Port's system of action — one governed execution layer shared by humans, automation, and AI agents. A workflow a developer triggers from the self-service hub is the same workflow an agent invokes as an MCP tool. Same logic, same permissions, same audit trail.
💡 Don't have a Port account yet? Sign up for freeThe engine
Every workflow is a directed graph of nodes connected by edges. Nodes are either triggers (entry points), actions (operations), or conditions (branching logic). Edges define execution order and pass data between steps.
For a full breakdown of node types, data flow, and JSON structure, see concepts and structure.
Trigger types
A workflow can be entered from any of four trigger types. A single workflow can define multiple triggers.
| Trigger | When it fires |
|---|---|
| Human form | A user submits the self-service hub form or calls the API directly. |
| Catalog event | An entity in your software catalog is created, updated, or deleted. |
| Agent tool | An AI agent invokes the workflow via the Port MCP server. |
| Schedule | A time-based rule fires on a recurring interval or cron expression. |
Use case patterns
Workflows cover three broad patterns:
- Automate a process - React to catalog events to enforce policies, send notifications, or keep data consistent without human intervention.
- Self-service - Give developers a governed form to request infrastructure, deployments, or any other operation — with built-in approvals and guardrails.
- Agent tool - Expose a workflow as an MCP tool so AI agents can invoke governed operations autonomously. See expose workflow as a tool.
One governed layer
The central design principle: you build a workflow once and it is invokable from everywhere. When a human fills the form and when an agent calls trigger_run, the same nodes execute, the same permissions are checked, and the same run record appears in the audit trail.
This means every action an agent can take is explicitly defined, governed, and observable — not a separate automation path that bypasses your controls.
Actions & automations is Port's legacy execution system. It remains fully supported. For new work, workflows offer multi-step logic, agent tool invocation, and a richer trigger model.
Next steps
- Concepts and structure - Learn about workflow components and structure.
- Quickstart and build with AI - Get started building your first workflow.
- Expose workflow as a tool - Make workflows invokable by AI agents through the Port MCP server.
- Interact with runs - Monitor and manage workflow executions.
- Workflow catalog and ownership - Assign team ownership to workflows and control access via the
_workflowblueprint. - Examples - See real-world workflow examples.