# Parametrized notification - question about the concept

**URL:** <https://forum.ansible.com/t/parametrized-notification-question-about-the-concept/20857>\
**Category:** Ansible Project\
**Created:** [March 14, 2016, 8:35am UTC](https://forum.ansible.com/t/parametrized-notification-question-about-the-concept/20857 "2016-03-14T08:35:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomas\_Kadlec](https://avatars.discourse-cdn.com/v4/letter/t/919ad9/32.png) [@Tomas\_Kadlec](https://forum.ansible.com/u/Tomas_Kadlec)\
**Post date:** [March 14, 2016, 8:35am UTC](https://forum.ansible.com/t/parametrized-notification-question-about-the-concept/20857/1 "2016-03-14T08:35:39Z")

</div>

Hi,

I am playing around with parametrized notifications (handler calls) and I have came to the following questions:

1/ Is it documented somewhere? I did not find anything about the subject in official docs only several issues on github (e.g. [https://github.com/ansible/ansible/issues/4853#issuecomment-28719258](https://github.com/ansible/ansible/issues/4853#issuecomment-28719258)). So please forgive me that I am only guessing.

2/ I have not found any valid reason to parametrize a notification with role variable only. Is there any? I am confused by this kind of behavior.

To be clear I am trying to notify a handler named client-handler-something and that something is stored as a variable. The task that notifies an appropriate handler may look as follows.

`