# Incoming Web Hooks

**URL:** https://meta.discourse.org/t/incoming-web-hooks/97384
**Category:** Support
**Created:** [September 17, 2018, 4:42pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384 "2018-09-17T16:42:36Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![matthoward](https://avatars.discourse-cdn.com/v4/letter/m/6f9a4e/32.png) [@matthoward](https://meta.discourse.org/u/matthoward)
#### Post date: [September 17, 2018, 4:42pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384/1 "2018-09-17T16:42:36Z")

</div>

Does Discourse have functionality to receive an incoming webhook from a service like PagerDuty and post it to a forum? Basically I’d send alerts from PagerDuty to the WebHook URL for Discourse and it would create a new forum topic.

If so, is there a guide that I can follow to set this up?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 17, 2018, 4:46pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384/2 "2018-09-17T16:46:43Z")

</div>

You’ll need to make calls to the Discourse API, perhaps using some intermediary like Zapier, OR write a plugin to catch whatever arbitrary incoming stuff.

If you can get PagerDuty to conform to Discourse’s API, then you’re golden. You can search here for examples and/or see [Reverse engineer the Discourse API](https://meta.discourse.org/t/how-to-reverse-engineer-the-discourse-api/20576).

---

<div class="post-metadata">

### Author: ![matthoward](https://avatars.discourse-cdn.com/v4/letter/m/6f9a4e/32.png) [@matthoward](https://meta.discourse.org/u/matthoward)
#### Post date: [September 17, 2018, 4:51pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384/3 "2018-09-17T16:51:24Z")

</div>

Thanks @pfaffman. So there is only webhooks configuration to send FROM discourse TO another site?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 17, 2018, 4:52pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384/4 "2018-09-17T16:52:03Z")

</div>

Webhooks go out. API calls come in.

---

<div class="post-metadata">

### Author: ![matthoward](https://avatars.discourse-cdn.com/v4/letter/m/6f9a4e/32.png) [@matthoward](https://meta.discourse.org/u/matthoward)
#### Post date: [September 17, 2018, 4:56pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384/5 "2018-09-17T16:56:53Z")

</div>

ok, i only asked because sites like google chat will give you a url you can use to point web hooks to so I could copy that url and put it in pagerduty and have pagerduty send an alert to the google chat webhook url and post in google chat. wasnt sure if there was similar functionality with discourse

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [September 17, 2018, 4:58pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384/6 "2018-09-17T16:58:25Z")

</div>

We support some webhooks, like for email bounce from some SMTP providers in core, and some webhooks in plugins, like Patreon webhooks in the Patreon plugin.

For your need, PagerDuty webhooks into Discourse topics, you will need to write a plugin.

We have a **very similar** plugin in early stage here: [GitHub - discourse/discourse-prometheus-alert-receiver · GitHub](https://github.com/discourse/discourse-prometheus-alert-receiver)

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [May 16, 2021, 7:43pm UTC](https://meta.discourse.org/t/incoming-web-hooks/97384/7 "2021-05-16T19:43:11Z")

</div>


