# How to get global input and use it across all pipeline steps

**URL:** <https://forum.buildkite.community/t/how-to-get-global-input-and-use-it-across-all-pipeline-steps/1872>\
**Category:** General\
**Created:** [January 28, 2022, 6:07pm UTC](https://forum.buildkite.community/t/how-to-get-global-input-and-use-it-across-all-pipeline-steps/1872 "2022-01-28T18:07:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jeremy](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/jeremy/32/1040_2.png) [@jeremy](https://forum.buildkite.community/u/jeremy)\
**Post date:** [January 29, 2022, 12:56am UTC](https://forum.buildkite.community/t/how-to-get-global-input-and-use-it-across-all-pipeline-steps/1872/4 "2022-01-29T00:56:19Z")

</div>

Since `my-input` would be stored as meta-data, it would not be available in a [conditional](https://buildkite.com/docs/pipelines/conditionals#navicon) within the pipeline, but you would be able to access it in Step B. If you are wanting to use it in a conditional though, you would need to use the `buildkite-agent meta-data` command and some scripting. There is a great example of how to do this over in this thread:

> [@Meta-data in conditional clause](https://forum.buildkite.community/t/meta-data-in-conditional-clause/1190/6):
>
> Hi folks! After a deep discussion we’ve decided not to support meta-data in conditionals just yet, sorry! We want to do it well, and have an answer for what happens when meta-data changes over the lifecycle of a build, and we haven’t quite figured that out yet. For now, you can do this with the buildkite-agent and a bit of scripting — and it’s not super different, like: # buildkite.yml steps: - block: "Request release" prompt: "Fill out the details for release" fields: - text: …

Hope that helps!

---

_[View the full topic](https://forum.buildkite.community/t/how-to-get-global-input-and-use-it-across-all-pipeline-steps/1872)._