# N8n collection?

**URL:** <https://discourse.crowdsec.net/t/n8n-collection/2740>\
**Category:** crowdsec\
**Created:** [January 6, 2026, 5:38pm UTC](https://discourse.crowdsec.net/t/n8n-collection/2740 "2026-01-06T17:38:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![icanthelp](https://avatars.discourse-cdn.com/v4/letter/i/b38774/32.png) [@icanthelp](https://discourse.crowdsec.net/u/icanthelp)\
**Post date:** [January 6, 2026, 5:38pm UTC](https://discourse.crowdsec.net/t/n8n-collection/2740/1 "2026-01-06T17:38:49Z")

</div>

[Searching for n8n](https://app.crowdsec.net/hub?filters=search%3Dn8n) on the hub yields no results.  
How come nobody has come up with a collection for such a popular web app?

---

<div class="post-metadata">

**Author:** ![iiAmLoz](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/iiamloz/32/386_2.png) [@iiAmLoz](https://discourse.crowdsec.net/u/iiAmLoz)\
**Post date:** [January 7, 2026, 4:05pm UTC](https://discourse.crowdsec.net/t/n8n-collection/2740/2 "2026-01-07T16:05:04Z")

</div>

Often people create their own parsers/scenarios and dont share them, so if you get round to doing it then you can create a pull request on the [hub](https://github.com/crowdsecurity/hub)

---

<div class="post-metadata">

**Author:** ![icanthelp](https://avatars.discourse-cdn.com/v4/letter/i/b38774/32.png) [@icanthelp](https://discourse.crowdsec.net/u/icanthelp)\
**Post date:** [January 7, 2026, 7:14pm UTC](https://discourse.crowdsec.net/t/n8n-collection/2740/3 "2026-01-07T19:14:03Z")

</div>

I see. It’s going to be a while before I feel confident enough to write a parser/scenario, but thanks!

---

<div class="post-metadata">

**Author:** ![iiAmLoz](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/iiamloz/32/386_2.png) [@iiAmLoz](https://discourse.crowdsec.net/u/iiAmLoz)\
**Post date:** [January 8, 2026, 10:50am UTC](https://discourse.crowdsec.net/t/n8n-collection/2740/4 "2026-01-08T10:50:08Z")

</div>

or if you can, create an issue on the hub with logs (PII redacted) and somebody might come and make it