# Ansible Tower Slack Notifications

**URL:** <https://forum.ansible.com/t/ansible-tower-slack-notifications/20507>\
**Category:** Ansible Project\
**Created:** [February 10, 2016, 11:36am UTC](https://forum.ansible.com/t/ansible-tower-slack-notifications/20507 "2016-02-10T11:36:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Matthews](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@Mark\_Matthews](https://forum.ansible.com/u/Mark_Matthews)\
**Post date:** [February 10, 2016, 11:36am UTC](https://forum.ansible.com/t/ansible-tower-slack-notifications/20507/1 "2016-02-10T11:36:20Z")

</div>

Hi

I trying to get Ansible callback notifications to work with Tower. They are working perfectly if I run a playbook from the Ansible server, but not working if I run a playbook from Tower.

I am trying to send notifications to Slack.

I have placed the following Slack callback file in the following location: /usr/share/ansible\_plugins/callback\_plugins

I then had to add a few environment variables…but after that notifications work from the Ansible server. Used this Slack call back plugin: [https://github.com/sivel/ansible/blob/v2-slack-callback/lib/ansible/plugins/callback/slack.py](https://github.com/sivel/ansible/blob/v2-slack-callback/lib/ansible/plugins/callback/slack.py)

Any ideas what needs to be done to get the callback to work with Tower? Is there a specific place that the plugin needs to be located for Tower to read it?

Ansible: 2.0.0.1

Ansible Tower: 2.4.3

OS: CentOS

Cheers

Mark

---

<div class="post-metadata">

**Author:** ![Bill\_Nottingham](https://avatars.discourse-cdn.com/v4/letter/b/3e96dc/32.png) [@Bill\_Nottingham](https://forum.ansible.com/u/Bill_Nottingham)\
**Post date:** [February 10, 2016, 4:25pm UTC](https://forum.ansible.com/t/ansible-tower-slack-notifications/20507/2 "2016-02-10T16:25:00Z")

</div>

This list is for open source Ansible only - for Tower releated questions please contact [support@ansible.com](mailto:support@ansible.com).

Thanks,

Bill
