LogoLogo
PipekitPricingBlogPipekit StatusRelease Notes
  • Introduction
  • Getting Started
  • CLI
    • Cron Workflows
  • Pipekit Agent
    • Helm Install
  • Pipekit
    • Authentication
      • Okta
    • Runs
    • Pipes
      • Managing Pipes
        • Run Conditions
        • Secrets
        • Alerting
      • Pipe Runs
        • Run Graph (DAG)
        • Pod Logs
        • Workflow Logs
        • Workflow YAML
      • Cron Workflows
      • Externally Triggered Workflows
    • Metrics
    • Templates
    • Clusters
    • Organization
      • Creating an Organization
      • Managing Users
      • Managing Alert Providers
      • Settings
      • Permissions
  • Python SDK
    • Jupyter Notebooks
    • Python Scripts
  • Self-Hosting Pipekit
    • Dependencies and Pre-requisites
    • Container Images
    • Kubernetes Permissions
    • Self-Hosted Pipekit Helm Chart
    • License Key
    • Initial Login and Break Glass Account
    • Integrating with your Git Provider
    • Configuring SSO
  • Additional Information
    • Free Trial Cluster
  • REST API
Powered by GitBook
On this page
  1. Pipekit
  2. Pipes

Externally Triggered Workflows

Externally-triggered Workflows

Last updated 9 months ago

Pipekit supports the ability to query your cluster for Workflows that have not been triggered by Pipekit. It will then display the workflow details in a Pipe and Runs accordingly. This feature is useful if you are just transitioning to Pipekit and you already have a preferred method of triggering Workflows, or you intend to keep using your existing method and to not use Pipekit to trigger Workflows.

How to enable

This feature is disabled by default. To enabled it, you need to modify your .

CronWorkflows are not supported by this feature.

All users in the Pipekit Organization will see externally-triggered Workflows in the of the Pipekit UI.

Runs dashboard
pipekit-agent installation