Overview

Integration actions allow workflows to trigger operations in connected platforms like GitHub. These actions leverage Port's existing integrations to perform operations directly, without requiring you to set up separate webhook authentication.

Available integrations

GitHub - Trigger GitHub Actions workflows.

Expanding integration support

Support for GitLab, Azure DevOps, and Jenkins is coming soon. If you need a specific integration, please reach out to Port's support team.

How it works

Integration actions use your existing Port integrations to authenticate and execute operations.

When you configure an integration action:

1. The workflow uses the credentials from your installed integration.
2. Port executes the operation on your behalf.
3. Results are returned to the workflow for use in subsequent nodes.

Secrets not supported

Secrets are not supported with integration actions. This includes both encrypted user inputs and organization secrets (.secrets.*) in JQ templates.

Common configuration

All integration actions share these fields:

Field	Type	Description
type	"INTEGRATION_ACTION"	Required. Must be "INTEGRATION_ACTION"
installationId	string	Required unless deferIntegrationInstallation is true. The ID of the installed integration.
integrationProvider	string	Required. The integration provider (e.g., "GITHUB")
integrationInvocationType	string	Required. The type of operation
integrationActionExecutionProperties	object	Required. Operation-specific configuration
deferIntegrationInstallation	boolean	Save the workflow before the integration is installed. Default: false. See deferring integration installation.
onFailure	'continue' | 'terminate'	Whether to continue the workflow if this node fails. Default: 'terminate'

Deferring integration installation

You can build a workflow before the integration it depends on is installed. This is common when Port AI generates a workflow, or when you author one manually and plan to connect the integration later.

Set deferIntegrationInstallation to true on an integration action node to save the workflow without the integration installed:

• Omit installationId and Port sets it to the value of integrationProvider, or set installationId equal to integrationProvider yourself.
• Finish setup from the workflow setup checklist — installing the integration satisfies the node with no further edits.

{
  "identifier": "trigger-github-workflow",
  "title": "Trigger GitHub Deployment",
  "config": {
    "type": "INTEGRATION_ACTION",
    "integrationProvider": "github-ocean",
    "deferIntegrationInstallation": true,
    "integrationInvocationType": "dispatch_workflow",
    "integrationActionExecutionProperties": {
      "org": "my-org",
      "repo": "my-repo",
      "workflow": "deploy.yml"
    }
  }
}

Finding your installation ID

To find the installation ID for your integration:

1. Navigate to your Data Sources page.
2. Find the integration you want to use.
3. Click on it to view details.
4. The installation ID is displayed in the integration settings.