Replies: 1 comment
|
Great proposal! Discord integration would be an excellent addition to Heym. This fits naturally with the existing patterns. Don't hesitate to contribute! After following the contribution steps (workflow DSL implementation, unit tests, documentation, Agent.md covers all you need), please send a single PR. Community would really appreciate this node. If you can also submit some public templates(trigger/submit) to the website(https://heym.run/templates please click submit yours), that'd be awesome for wider adoption (optional but highly recommended). Thanks in advance! Looking forward to this contribution. 🚀 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
The project already supports Slack and Telegram, and I think Discord should be supported as well. In my view, Discord would have many valuable use cases in agent workflows, especially for notifications, interactive triggers, operational coordination, and AI-driven assistant experiences.
For now, the focus on two practical phases: Discord webhook first, then inbound Discord-triggered workflows.
Phases
Phase 1
Add a native discord node for sending messages to Discord via webhook.
This phase would cover the most common use cases, such as workflow alerts, AI-generated summaries, error notifications, and operational updates. It is the lowest-risk way to bring Discord into Heym and fits closely with the existing outbound Slack-style integration pattern.
Phase 2
Add a native discordTrigger node to start workflows from incoming Discord events or interactions.
This phase fits the current architecture well because Heym already supports similar trigger patterns for platforms like Slack and Telegram. The expected flow is straightforward: receive the inbound Discord request, verify authenticity, acknowledge quickly when needed, map the payload into workflow inputs, and execute the workflow asynchronously.
To keep scope manageable, the first version should stay narrow and support one inbound entry path first, such as:
This would open the door for Discord-driven AI assistants, bot workflows, operational commands, and human-in-the-loop flows inside Discord.
Related Links
discord webhook
All reactions