Skip to content

Argo Workflow Trigger

Argo workflow is K8s custom resource which help orchestrating parallel jobs on Kubernetes.

Argo Workflow Trigger

Trigger a workflow

  1. Make sure to have the eventbus deployed in the namespace.

  2. We will use webhook event-source and sensor to trigger an Argo workflow.

  3. Let's set up a webhook event-source to process incoming requests.

    kubectl apply -n argo-events -f
  4. Create the sensor.

    kubectl apply -n argo-events -f
  5. Let's expose the webhook event-source pod using port-forward so that we can make a request to it.

    kubectl -n argo-events port-forward <name-of-event-source-pod> 12000:12000
  6. Use either Curl or Postman to send a post request to the http://localhost:12000/example.

    curl -d '{"message":"ok"}' -H "Content-Type: application/json" -X POST http://localhost:12000/example
  7. List the workflow using argo list.


Similar to other type of triggers, sensor offers parameterization for the Argo workflow trigger. Parameterization is specially useful when you want to define a generic trigger template in the sensor and populate the workflow object values on the fly.

You can learn more about trigger parameterization here.


Trigger policy helps you determine the status of the triggered Argo workflow object and decide whether to stop or continue sensor.

Take a look at K8s Trigger Policy.

Argo CLI

Although the sensor defined above lets you trigger an Argo workflow, it doesn't have the ability to leverage the functionality provided by the Argo CLI such as,

  1. Submit
  2. Resubmit
  3. Resume
  4. Retry
  5. Suspend

To make use of Argo CLI operations, The sensor provides the argoWorkflow trigger template,

      version: v1alpha1
      resource: workflows
      operation: submit  # submit, resubmit, resume, retry, suspend or terminate

Complete example is available here.