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.
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:
- The workflow uses the credentials from your installed integration.
- Port executes the operation on your behalf.
- Results are returned to the workflow for use in subsequent nodes.
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. 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 |
onFailure | 'continue' | 'terminate' | Whether to continue the workflow if this node fails. Default: 'terminate' |
Finding your installation ID
To find the installation ID for your integration:
- Navigate to your Data Sources page.
- Find the integration you want to use.
- Click on it to view details.
- The installation ID is displayed in the integration settings.