<!--
---
title: "Triggers and EventListeners"
linkTitle: "Triggers"
weight: 3
description: >
  Event Triggers
---
-->
# Tekton Triggers

Triggers enables users to map fields from an event payload into resource
templates. Put another way, this allows events to both model and instantiate
themselves as Kubernetes resources. In the case of `tektoncd/pipeline`, this
makes it easy to encapsulate configuration into `PipelineRun`s and
`PipelineResource`s.

![TriggerFlow](https://github.com/tektoncd/triggers/blob/master/images/TriggerFlow.png?raw=true)

## Learn More

See the following links for more on each of the resources involved:

- [`TriggerTemplate`](triggertemplates.md)
- [`TriggerBinding`](triggerbindings.md)
- [`EventListener`](eventlisteners.md)
- [`ClusterTriggerBinding`](clustertriggerbindings.md)

## Getting Started Tasks

- [Create an Ingress on the EventListener Service](create-ingress.yaml)
- [Create a GitHub webhook](create-webhook.yaml)

<!--
---
title: "Triggers and EventListeners"
linkTitle: "Triggers"
weight: 3
description: >
  Event Triggers
cascade:
  github_project_repo: https://github.com/tektoncd/triggers
---
-->
# Tekton Triggers

Triggers enables users to map fields from an event payload into resource
templates. Put another way, this allows events to both model and instantiate
themselves as Kubernetes resources. In the case of `tektoncd/pipeline`, this
makes it easy to encapsulate configuration into `PipelineRun`s and
`PipelineResource`s.

![TriggerFlow](https://github.com/tektoncd/triggers/blob/master/images/TriggerFlow.png?raw=true)

## Learn More

See the following links for more on each of the resources involved:

- [`TriggerTemplate`](triggertemplates.md)
- [`TriggerBinding`](triggerbindings.md)
- [`EventListener`](eventlisteners.md)
- [`ClusterTriggerBinding`](clustertriggerbindings.md)

## Getting Started Tasks

- [Create an Ingress on the EventListener Service](create-ingress.yaml)
- [Create a GitHub webhook](create-webhook.yaml)

Fix 'Edit this page' and 'Create an issue' links on the website
Fix 'Edit this page' and 'Create an issue' links on the website

Add a cascading page property to the frontmatter of docs/README.md
that will apply to all child pages displayed in the Triggers section
of the docs on the website.

This ensures the 'Edit this page' and 'Create an issue' links in
the sidebar point to the Triggers repo instead of the website repo.
