One obvious way to use n8n is with Discourse’s pre-existing RSS feeds.
I use RSS as a way to set up an active search for terms that I’m interested in across different platforms. RSS is the one protocol that pretty much everything speaks, or can be translated into ( e.g. rss-bridge).
It looks like someone has built an n8n node for Discourse, so that will probably be pretty easy to use. And as the documentation says, if any API calls you’re expecting aren’t supported you can always drop down to the HTTP Node and make REST calls if you know what you’re doing.
I’ve used n8n for marketing automations and I think it’s a pretty decent tool. I’m happy that it’s open source, which I think makes a much stronger case for owning your intellectual property, i.e. not building out a huge part of your business logic on a propriety platform subject to rate changes and arbitrary deplatforming. So there might be some common sentiment with those in the Discourse community.