Best answer

No body content when creating GitHub issue directly from Discord (New forum post)

  • 10 July 2024
  • 3 replies


For those using a Discord → GitHub action flow to create issues directly from Discord, is there any plan to allow adding the body content of a new forum post?

Currently, triggering an event with “new forum post” in a Discord channel only allows adding the post title to a GitHub issue. (the other available data posts IDs, which are not useful). Creating GitHub issues directly from Discord without the post body is almost irrelevant; you can't create an issue with only a title.

Interestingly enough, if you use the "New forum message" event, you can access/see/choose the content of that message. Why can't the same data be included for "new forum post"? It's essentially the same content.

options if you choose “New forum post” event

options if you choose “New forum message” 

same topic (but closed) 

same topic (but closed): 



Best answer by ken.a 11 July 2024, 08:39

View original

3 replies

Userlevel 7
Badge +6

Hi there @mat123456,

Welcome to the Community! 🎉

I did some digging into this, and it seems like the Forum post body is unable to be fetched by the “New Forum Post” trigger. However, we have an existing feature request for this exact functionality.

I have added you to the open feature request. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track interest in this feature being implemented
  • Allows us to notify you via email if this feature becomes available in the future

While I don't have an ETA on when this feature might be implemented, we will notify you via email if it is!

Hopefully, this helps.

Hi Ken,

As much as I appreciate your response, the similar feature requests I included have been open for over a year, which leads me to believe this isnt on any near-future roadmap.

This is unfortunate as demand for this “basic” feature request seems to exist. 


Userlevel 7
Badge +6

Hi @mat123456,


I completely understand your frustration.

The main reason for the delay is that with over 5,000+ different integrations on Zapier, priorities are constantly changing and shifting. With so many variables at play, some of which are completely outside our control (for example, we rely on partners to make changes), it's impossible to provide accurate timeframes for feature implementation.

Please know that the feature request has been logged, and we are working on resolving it as quickly as possible. We'll make sure to keep you updated as soon as it gets resolved.

Thank you for your patience and understanding.