# (Another) Discourse to Discord webhook

**URL:** <https://meta.discourse.org/t/another-discourse-to-discord-webhook/61178>\
**Category:** Extras\
**Created:** [18.Апрель.2017 08:17:33 UTC](https://meta.discourse.org/t/another-discourse-to-discord-webhook/61178 "2017-04-18T08:17:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![DanielMarquard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/danielmarquard/32/74010_2.png) [@DanielMarquard](https://meta.discourse.org/u/DanielMarquard)\
**Post date:** [18.Апрель.2017 22:23:41 UTC](https://meta.discourse.org/t/another-discourse-to-discord-webhook/61178/4 "2017-04-18T22:23:41Z")

</div>

> [@erlend\_sh](#):
>
> I don’t know how specific @DanielMarquard’s code is to Crit Cola though; that might justify keeping the two codebases separate, at least in the short term.

Crit Cola’s Discourse-to-Discord webhook will work for anyone, but limitations in Discord’s embeds led me to go in my own direction in terms of the appearance of the embeds and what information they’re inclusive of. Here’s what the embeds look like using Crit Cola’s config, but with no other code changes as compared to what’s in the public repo:

 ![](https://global.discourse-cdn.com/meta/original/3X/a/0/a0c6553702ff4fe5e4740dc9ef8e32df3ab598af.jpg)

This can be easily forked and customized to achieve a different layout, but this isn’t required.

> [@erlend\_sh](#):
>
> Err, not really 😛 Since both are written in PHP, we’d strongly prefer it if the two of you ended up maintaining a single project together. There’s much more to be gained from that.

I’d very much favor a more native solution that doesn’t use PHP. I work a lot with Node.js and PHP, but not so much with Ruby. 😕

---

_[View the full topic](https://meta.discourse.org/t/another-discourse-to-discord-webhook/61178)._
