# argoproj/argo-events

Event-driven Automation Framework for Kubernetes

Repository: https://github.com/argoproj/argo-events
Canonical: https://ross.abutalabs.com/products/argo-events
Homepage: https://argoproj.github.io/argo-events/
Language: Go
License: Apache-2.0
License Family: permissive
Topics: kubernetes, event-driven, cloudevents, workflows, triggers, automation-framework, cloud-native, argo, pipelines, event-source, workflow-automation, eventing-framework
Last push: 2026-08-22T13:20:41+00:00

## Health v2 (maintenance only)
Score: 93/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 81, longevity 100
- inputs: {"age_days": 3030, "days_push": 11, "days_rel": 51, "gap_med": 67.0, "n_releases_24m": 9}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2687, forks 838 (observed 2026-08-28T04:07:10.777734+00:00)

## What it is
Argo Events is an event-driven workflow automation framework for Kubernetes that triggers actions like creating Kubernetes objects, invoking Argo Workflows, or calling serverless workloads in response to events. It supports 20+ event sources (webhooks, S3, cron schedules, Kafka, SNS/SQS, GCP PubSub) and 10+ triggers, and is CloudEvents compliant.

## Use cases
- trigger kubernetes workflows from s3 events
- run pipelines on a cron schedule in kubernetes
- react to kafka messages with kubernetes actions
- build event-driven automation on kubernetes
- trigger serverless functions from webhooks
- automate ci/cd pipelines with events
- wire messaging queues to kubernetes objects

## When to choose
- you run workloads on Kubernetes and need event-driven automation
- you want to trigger Argo Workflows or serverless functions from diverse event sources
- you need CloudEvents-compliant event routing with multi-source dependency management

## When to avoid
- you are not running Kubernetes
- you need a simple standalone message queue consumer without Kubernetes orchestration
- you only need basic cron scheduling outside a cluster

## Facets
- artifact type: framework
- maturity: active
- function: workflow-automation, message-queue, webhook, scheduling, deployment, microservices
- domain: cloud-computing, microservices
- platform: go, cloud, self-hosted
- tags: event-driven, argo, cloudevents, event-sources, sensors, triggers, cloud-native, kubernetes-operator, devops, automation, containers, kubernetes, docker

## Member repositories
- argoproj/argo-events (main) score 93

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:10.777734+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:17:45.383733+00:00, confidence not recorded.
  - readme: https://github.com/argoproj/argo-events (fetched 2026-08-28T04:07:10.777734+00:00, sha d56451fe0faa)
  - homepage: https://argoproj.github.io/argo-events/ (fetched 2026-08-29T09:59:47.241556+00:00, sha 785bfeece51b)
- Data as of 2026-08-30T08:39:29.467469+00:00.