How can I get the Discord webhook trigger working in n8n?

Below is some general advice that might help, based on similar issues we document for other trigger nodes. (Note that official documentation for Discord Trigger isn’t included in our current docs, so these are general troubleshooting pointers):

1. Check Your Webhook URL & TLS/HTTPS Configuration

If you’re running n8n behind a reverse proxy (or similar), ensure that your webhook URL is set correctly and uses HTTPS. For example, in other nodes like Telegram you must configure the public webhook URL using TLS/SSL. Make sure your Discord webhook endpoint is also reachable under the expected HTTPS domain.

2. Workflow Activation & Testing

Some trigger nodes show different behavior between testing and production. In other nodes (such as Slack or Telegram), if you test while a workflow remains active in production you can run into issues (for instance, only one webhook registration being accepted). Try one of these approaches:

• Temporarily disable your production workflow when testing your Discord trigger.
• Ensure you’re using the correct webhook URL (test vs. production) as required by Discord.

3. Restarting the Workflow

If the trigger seems “stuck” or doesn’t register events, try exiting the workflow editor and reopening it to force a reset of the canvas. This technique is mentioned in our docs for troubleshooting other trigger nodes.

4. Version & Environment Considerations

Since you’re on n8n version 1.70.4 and running it via npm on Ubuntu desktop, ensure there aren’t any environment-specific issues (such as network restrictions, reverse proxy configurations, or other infrastructural nuances) affecting the webhook’s operation.

Next Steps

Because Discord triggers might have their own quirks and the documentation for them isn’t as extensive as for nodes like Telegram or Slack, you might consider:

• Checking the n8n community forums or GitHub issues for any up-to-date reports or fixes specific to the Discord Trigger.
• Verifying that your bot’s permissions and webhook settings on Discord are configured as expected.

If you continue encountering problems after these steps, providing additional error logs or configuration details on a community forum or GitHub issue may help pinpoint the root cause.

Hopefully, these general troubleshooting ideas help move you forward. Let me know if you need further pointers on a specific part of your setup!

Below is some guidance based on other trigger nodes (like Telegram and Slack) in n8n. Although there isn’t a dedicated "Discord Trigger node common issues" page in the current docs, many troubleshooting concepts are similar across integrations.

---

General Troubleshooting for Discord Trigger Events

1. Webhook URL and Environment
   • Make sure your Discord bot is set up properly and that you’ve configured the correct webhook URL.
   • If you’re using both testing and production modes, verify that only one workflow is active at a time with the appropriate URL. For example, similar to the Slack Trigger node, Discord (like many other platforms) may overwrite your webhook URL if you switch between environments.

2. Reverse Proxy / HTTPS Configuration
   • If you’re running n8n behind a reverse proxy (or on a local machine) make sure that any required HTTPS URLs are properly exposed to Discord’s servers. This is similar to what’s described for the Telegram Trigger node: the external service (Discord) may require that your webhook endpoint is secure (using HTTPS).
   • Check your reverse proxy or tunneling tool configuration to confirm that WebSocket (if applicable) and HTTPS support are enabled.

3. Webhooks Registration Consistency
   • Ensure that your Discord application or bot isn’t trying to register multiple webhooks at once. Many integrations allow only one active webhook per app, causing issues if multiple workflows are testing or running simultaneously.
   • Disable or stop any inactive/testing workflows that might be consuming the webhook so that only one instance interacts with Discord at a time.

4. Logging & Error Messages
   • Check the n8n execution logs for any errors related to webhook registration or propagation. Errors may point to misconfigured URLs, missing scopes/permissions, or network/firewall issues.
   • Make sure that your Discord bot has the correct permissions and that it is listening for the specific events in the channels you need.

5. Version & Known Issues
   • You mentioned that you’re using n8n version 1.70.4. It’s worth checking the GitHub issues page or Discord community to see if there are known bugs specific to the Discord trigger node in your version. Sometimes a minor version update (or a workaround shared by the community) can help if it’s a bug in n8n.

---

Next Steps

• Double-check Credentials and Permissions
  Ensure your Discord bot credentials and webhook settings comply with Discord’s API requirements.

• Activate One Workflow at a Time
  When testing, temporarily disable production workflows (or any others using the same bot) to avoid multiple webhook registrations. This is analogous to the approach used for Slack and Telegram nodes.

• Test with a Tunneling Service
  If running locally (like with your Ubuntu desktop), try setting up a tunnel (e.g. using ngrok) so that Discord can reliably reach your instance with an HTTPS URL.

• Refer to Community Resources
  Although the docs may not have detailed Discord troubleshooting yet, the general guidelines from other trigger nodes might lead you in the right direction. The n8n community channels (such as the Discord server) can be helpful if you need additional tailored advice.

---

Hopefully, these steps will help steer you toward a resolution. If you discover a consistent issue that points to a bug within the Discord trigger node, consider filing an issue on the n8n GitHub so that the team can investigate further.

Happy automating!