# Alarm pipeline binding

**URL:** <https://forum.inductiveautomation.com/t/alarm-pipeline-binding/45871>\
**Category:** Ignition\
**Created:** [April 21, 2021, 4:34pm UTC](https://forum.inductiveautomation.com/t/alarm-pipeline-binding/45871 "2021-04-21T16:34:02Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![tnichols](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tnichols/32/73331_2.png) [@tnichols](https://forum.inductiveautomation.com/u/tnichols)\
**Post date:** [December 21, 2021, 4:23pm UTC](https://forum.inductiveautomation.com/t/alarm-pipeline-binding/45871/9 "2021-12-21T16:23:39Z")

</div>

We have multiple projects on the same gateway with the same standard tag provider. Here is what I have come up with…

Within the Tag Browser, have one folder for each project. The names of these top-level folders match the names of the projects. For alarms, bind the Active Pipeline to `split({PathToTag}, '/')[0,0] + '/pipeline name'`.

---

_[View the full topic](https://forum.inductiveautomation.com/t/alarm-pipeline-binding/45871)._