Create your FREE Codefresh account and start making pipelines fast. Create Account

Trigger a Codefresh Pipeline from Argo CD

6 min read

Codefresh is an awesome platform for doing GitOps deployments to Kubernetes. Starting last year, the Codefresh team has been adding rich integrations with Argo CD and Argo Rollouts, GitOps observability dashboards, and more. Codefresh pipelines, in particular, have played an integral role in our customers’ progressive delivery workflows by allowing them to orchestrate all of the testing, analysis, and rollback activities that work in conjunction with Argo CD synchronization.

While it is quite common to have one or two primary pipelines that handle these large workflows, it can also be useful to trigger an occasional helper pipeline, based on events in Argo CD. For example, you might want to trigger a pipeline whenever an Argo CD application enters a failed or error state. Perhaps you’d like such a pipeline to gather a log bundle or open a ticket.

The goal of this article is to show you how you can use events in Argo CD to trigger pipelines in Codefresh.


To follow along with this article, you should already have a Codefresh account and be using Argo CD for GitOps-style deployments to Kubernetes.

Earlier this year, the Argo team released Argo CD Notifications, which is an official add-on tool for alerting on Argo CD state changes. In this article, we’ll be leveraging this tool to watch for an example event and trigger a corresponding pipeline in Codefresh.

If you haven’t already installed Argo CD Notifications, then I recommend you follow this quick installation guide from the documentation: The installation consists primarily of applying 2 manifest files. Sometimes the documentation can lag behind the releases slightly, so I also recommend that you use the manifest files from the latest release, which can be found here:

Configure Argo CD Notifications

Argo CD Notifications should be installed into the same namespace as Argo CD, which by default is called argocd. We’ll be configuring it via a Secret and a ConfigMap within this namespace.

First, let’s update the secret to add an API Key for authenticating to Codefresh. You can create an API Key in the Codefresh UI by navigating to the Settings area at the bottom-left, then User Settings, and then API Keys.

Now go ahead and edit the secret.

In your editor, scroll down to the bottom and add a stringData: section with a single key:value pair. Call the key codefresh-api-key. For its value, paste in your Codefresh API Key.

Codefresh API Key

Save the Secret and exit.

Next, let’s create a little example pipeline in Codefresh. This is the pipeline that we’ll be triggering from Argo CD Notifications. For illustrative purposes, we’ll have it print out all the “ARGOCD” variables that we’ll be passing in from the event in Argo CD.


After you save the pipeline, click the Settings tab and then copy its PIPELINE ID. We’ll need this in a moment.

Pipeline Settings

We’ll be performing all the rest of our configuration via the ConfigMap I mentioned. Let’s go ahead and edit it.

If you followed the aforementioned install guide for Argo CD Notifications, then the data section of this ConfigMap will already contain lots of code. Copy the 3 code blocks from below, and append them to the end of your data section.

I’ll explain what’s going on in these code blocks. The first two blocks define our webhook which will communicate with Codefresh:

  • service.webhook.codefresh – this service defines the base URL and credentials for connecting to Codefresh. It could be used by multiple templates that make different REST calls to Codefresh.
  • template.codefresh-simple-test-pipeline – this template defines the specific REST URL (appended to the base URL) and data that we’ll use to tell Codefresh to run our specific pipeline. You can see that a large part of this data consists of ARGOCD_ variables that we’ll be able to use within the pipeline.


The third block of code, trigger.sync-operation-change ties some events in Argo CD to the webhook defined in the previous 2 blocks. The events we’re specifying here are Error and Failed sync events.

Before you save the ConfigMap, we need to make some changes. Replace all instances of my-build-id (there should be two) with the Pipeline ID that you copied previously (it was 6061fd6a9732973e2e6fde89 in the previous example screenshot).

If the pipeline you created earlier has a trigger, then we’ll need to update all 4 trigger-related values. If it doesn’t have a trigger (or if you want to ignore the trigger when you run the pipeline), then you can just delete these 4 lines.

Here is a pipeline trigger that you can use as an example:

Pipeline Trigger

For this example, you would update the trigger-related values like this:


Now save and exit the ConfigMap! Whew, we’re almost done. For the ArgoCD Notification service to read the updated ConfigMap, we’ll want to restart its pod. Since its pod is controlled by a deployment resource, we can just delete the pod, and the deployment will create a new one for us.


Now we’re ready to test!! To create the failure event we’ve defined, we just need to break a manifest in one of the Git repos that Argo CD is syncing. I chose a manifest in one of my teammate’s repositories… doh, sorry Brandon!

ArgoCD state

This should be enough to trigger our pipeline in Codefresh!

Be Happy!

Now go check the output from your awesome new pipeline, which was just triggered by a failed sync event in Argo CD!

Freestyle step

Wow, that looks great. Look at all the rich Argo CD sync information that our pipeline can now access as variables – totally worth the setup effort. And I’m sure Brandon would agree!

Ted Spinks

Ted Spinks

Ted Spinks is a Solution Architect at Codefresh. He is huge fan of DevOps automation. He loves writing code, diving into new APIs, and solving automation challenges. Before Codefresh, Ted worked as a CI/CD engineer for an autonomous driving software company, Zenuity, and as a consultant at AHEAD and VMware.

Leave a Reply

* All fields are required. Your email address will not be published.

Get a head start on building better pipelines!