--- title: Automation with Argo (Events and workflows) | daily.dev description: An introduction to Argo Events and Argo Workflows on Kubernetes. Argo Events is an event-driven automation framework with three core components: Event Source... canonical: https://daily.dev/posts/automation-with-argo-events-and-workflows--bhuvffrzs twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Automation with Argo (Events and workflows) | daily.dev og:description: An introduction to Argo Events and Argo Workflows on Kubernetes. Argo Events is an event-driven automation framework with three core components: Event Source... og:url: https://daily.dev/posts/automation-with-argo-events-and-workflows--bhuvffrzs og:image: https://api.daily.dev/og/posts/BHuvffRZs.png og:image:alt: Automation with Argo (Events and workflows) og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Automation with Argo (Events and workflows) **[Medium](https://daily.dev/sources/medium_js)** · 9 min read · 1 upvotes · 0 comments ## Summary An introduction to Argo Events and Argo Workflows on Kubernetes. Argo Events is an event-driven automation framework with three core components: Event Source (receives events from webhooks, SNS, SQS, etc.), Event Bus (NATS-based message transport), and Sensor (listens for events and triggers actions). Argo Workflows defines sequences of automated tasks as Kubernetes Custom Resources, supporting template types including Container, Script, Resource, Suspend, DAG, and Steps. The post covers YAML examples for each component, explains the Workflow Controller and Argo Server architecture, and describes how workflows are submitted, validated, and executed within a Kubernetes cluster. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are the main components of Argo Events and how do they work together? Argo Events consists of three main components: Event Source, EventBus, and Sensor. Event Source generates or receives events (webhooks, SNS, SQS, S3, etc.), the EventBus (typically backed by NATS or Kafka) distributes those events, and the Sensor listens for specific events and fires a Trigger, which can start an Argo Workflow, create a Kubernetes resource, or call a webhook. _Teams wiring event-driven pipelines on Kubernetes track Argo Events patterns like these on daily.dev._ ### What are the six template types available in an Argo Workflow spec? An Argo Workflow spec supports six template types split into two groups: template definitions (Container, Resource, Script, Suspend) which define work to be done, and template invocators (DAG and Steps) which call other templates and control execution order, including parallel or sequential dependencies. _Developers designing complex Kubernetes pipelines can keep up with Argo Workflows template patterns on daily.dev._ ### Which messaging backends can Argo Events use for its EventBus? Argo Events requires an EventBus implementation to function, and it supports Native NATS (deployed automatically), JetStream (recommended for production use), an existing NATS cluster, or Kafka where supported by the deployment version. Native NATS is the default option where the broker is deployed automatically without user configuration. _Engineers choosing a messaging backend for Kubernetes event pipelines compare Argo EventBus options on daily.dev._ ## Similar posts on daily.dev - [Argo CD GitOps: Automated Kubernetes Deployments 2026](https://daily.dev/posts/argo-cd-gitops-automated-kubernetes-deployments-2026-phznycqfy) · Medium · 4 upvotes · 0 comments - [The Missing Primitive: Orchestrating Cloud-Native Stacks Beyond GitOps](https://daily.dev/posts/the-missing-primitive-orchestrating-cloud-native-stacks-beyond-gitops-iue7z2cxd) · ITNEXT · 0 upvotes · 0 comments - [How to Deploy to Kubernetes using Argo CD and GitOps](https://daily.dev/posts/how-to-deploy-to-kubernetes-using-argo-cd-and-gitops-loemaf7pl) · DigitalOcean Community · 4 upvotes · 0 comments - [Tools and Workflows for Kubernetes in CI/CD](https://daily.dev/posts/tools-and-workflows-for-kubernetes-in-ci-cd-lvjbufec7) · Cloud Native Now · 2 upvotes · 0 comments - [ArgoCon North America 2026: What to expect as the Argo community looks toward CD 4.0](https://daily.dev/posts/argocon-north-america-2026-what-to-expect-as-the-argo-community-looks-toward-cd-4-0-c3tk2igds) · CNCF · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#architecture](https://daily.dev/tags/architecture), [#workflow-orchestration](https://daily.dev/tags/workflow-orchestration) [View this post on daily.dev](https://daily.dev/posts/automation-with-argo-events-and-workflows--bhuvffrzs) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Automation with Argo (Events and workflows)","url":"https://daily.dev/posts/automation-with-argo-events-and-workflows--bhuvffrzs","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/automation-with-argo-events-and-workflows--bhuvffrzs"},"datePublished":"2026-07-22T07:33:19.690Z","dateModified":"2026-09-14T06:49:44.358Z","description":"An introduction to Argo Events and Argo Workflows on Kubernetes. Argo Events is an event-driven automation framework with three core components: Event Source...","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/automation-with-argo-events-and-workflows--bhuvffrzs","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,architecture,workflow-orchestration","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"Automation with Argo (Events and workflows)"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/automation-with-argo-events-and-workflows--bhuvffrzs#faq","mainEntity":[{"@type":"Question","name":"What are the main components of Argo Events and how do they work together?","acceptedAnswer":{"@type":"Answer","text":"Argo Events consists of three main components: Event Source, EventBus, and Sensor. Event Source generates or receives events (webhooks, SNS, SQS, S3, etc.), the EventBus (typically backed by NATS or Kafka) distributes those events, and the Sensor listens for specific events and fires a Trigger, which can start an Argo Workflow, create a Kubernetes resource, or call a webhook. Teams wiring event-driven pipelines on Kubernetes track Argo Events patterns like these on daily.dev."}},{"@type":"Question","name":"What are the six template types available in an Argo Workflow spec?","acceptedAnswer":{"@type":"Answer","text":"An Argo Workflow spec supports six template types split into two groups: template definitions (Container, Resource, Script, Suspend) which define work to be done, and template invocators (DAG and Steps) which call other templates and control execution order, including parallel or sequential dependencies. Developers designing complex Kubernetes pipelines can keep up with Argo Workflows template patterns on daily.dev."}},{"@type":"Question","name":"Which messaging backends can Argo Events use for its EventBus?","acceptedAnswer":{"@type":"Answer","text":"Argo Events requires an EventBus implementation to function, and it supports Native NATS (deployed automatically), JetStream (recommended for production use), an existing NATS cluster, or Kafka where supported by the deployment version. Native NATS is the default option where the broker is deployed automatically without user configuration. Engineers choosing a messaging backend for Kubernetes event pipelines compare Argo EventBus options on daily.dev."}}]} ```