-title:Promotion building blocks

localurl:/gitops/promotions/promotion-components/

-title:Promotion setup guidelines

localurl:/gitops/promotions/create-promotion-sequence/

localurl:/gitops/promotions/create-promotion-sequence/

-title:YAML specs

localurl:/gitops/promotions/yaml/

-title:Triggering promotions

url:"/promotion-policy"

-title:Promotion Workflows

url:"/promotion-workflow"

-title:Service accounts for Promotion Workflows

url:"/service-accounts-promotion-workflows"

-title:Promotion hooks

url:"/promotion-hooks"

url:"/promotion-hooks"

-title:Service accounts for Promotion Workflows

url:"/service-accounts-promotion-workflows"

-title:Promotion contexts in promotion hooks

url:"/promotion-context-promotion-workflows"

-title:Product promotion settings

Defining a promotion context with the custom parameters and then**exporting the context** makes these custom values available to all subsequent hooks in the same Promotion Flow. Each hook can access and use the values from the promotion context as needed.

Using promotion contexts enables scenarios like notifying specific Slack channels or linking Jira tickets to releases. See[How promotion context works during execution](#how-promotion-context-works-during-execution).

To see a practical example, follow the[Walkthrough: Using promotion hooks in Promotion Flows to handle promotion failures](#walkthough-using-promotion-hooks-in-promotion-flows-to-handle-promotion-failures), where you create different Promotion Workflows with hooks, define a promotion context in a workflow, and assign hooks at different stages of the Promotion Flow.

To see a practical example, follow the[Walkthrough: Using promotion hooks in Promotion Flows to handle promotion failures](#walkthrough-using-promotion-hooks-in-promotion-flows-to-handle-promotion-failures), where you create different Promotion Workflows with hooks, define a promotion context in a workflow, and assign hooks at different stages of the Promotion Flow.

Explore examples in[Codefresh Hub for Argo](https://codefresh.io/argohub/){:target="\_blank"}.

A default set of arguments are available to all Promotion Workflows with hooks. See[Default arguments in Promotion Workflows with hooks](#default-arguments-for-promotion-hooks).

A default set of arguments are available to all Promotion Workflows with hooks. See[Default arguments in Promotion Workflows with hooks](#default-arguments-in-promotion-workflows-with-hooks).

|`FAILED_ENVIRONMENTS`| The environment or environments which failed in the release with this information: {::nomarkdown}<ul><li><b>Name</b>: The name of the environment that failed to complete the release. For example, production</li><li><b>Status</b>: The release or promotion status for the environment. Can be one of the following: <ul><li>Successful</li><li>Running</li><li>Suspended</li><li>Failed</li><li>Terminated</li></ul></li><li><b>Error-message</b>: The system-generated error message identifying the reason for the failed promotion. For example, <codeclass="highlighter-rouge">Product release was automatically terminated because the workflow state remained unknown</code>. {:/}| OnFailed hooks only|

In a Promotion Flow, hooks may need custom parameters beyond the default ones available to the promotion mechanism. Because promotion hooks run within GitOps Runtimes in your own clusters, they do not automatically have access to these custom internal parameters. To pass custom values like Jira ticket IDs, approver names, or Slack channel information between hooks in the same Promotion Flow, you must define and export a promotion context. For details, see[Creating and exporting a promotion context](#creating-and-exporting-a-promotion-context).

In a Promotion Flow, hooks may need custom parameters beyond the default ones available to the promotion mechanism. Because promotion hooks run within GitOps Runtimes in your own clusters, they do not automatically have access to these custom internal parameters. To pass custom values like Jira ticket IDs, approver names, or Slack channel information between hooks in the same Promotion Flow, you must define and export a promotion context. For details, see[Promotion contexts in promotion hooks]({{site.baseurl}}/docs/promotions/promotion-context-promotion-workflows/).