# Slack Action Query

**URL:** <https://discuss.elastic.co/t/slack-action-query/56387>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [July 26, 2016, 11:16am UTC](https://discuss.elastic.co/t/slack-action-query/56387 "2016-07-26T11:16:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [July 26, 2016, 11:16am UTC](https://discuss.elastic.co/t/slack-action-query/56387/1 "2016-07-26T11:16:58Z")

</div>

Hi,  
Is the slack action able to work behind a proxy? We have elasticsearch started with options for proxyHost and proxyPort yet the slack action times out. If we use a webhook that works but throws an exception because the slack api returns an empty body.

Regards,  
David

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [July 26, 2016, 2:13pm UTC](https://discuss.elastic.co/t/slack-action-query/56387/2 "2016-07-26T14:13:03Z")

</div>

Hey,

if you configure a global proxy in your `elasticsearch.yml` setting proxy port/host like this, this should work for webhook/slack/pagerduty/hipcaht actions as well as the http input.

```auto
watcher.http.proxy:
  host: localhost
  port: 8080

```

--Alex

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:44pm UTC](https://discuss.elastic.co/t/slack-action-query/56387/3 "2017-07-06T13:44:19Z")

</div>