Integrations
Common issues with Telegram Trigger in Duaer
Common Telegram Trigger issues in Duaer: stuck while testing, HTTPS required, and test or production only.
Stuck waiting for a trigger event
When you test Telegram Trigger in the editor, Duaer pushes results back to the page over WebSocket. If a self-hosted Duaer sits behind a reverse proxy that does not forward WebSocket, the page keeps waiting.
Turn on WebSocket forwarding in your proxy (Nginx, Caddy, Traefik, and so on). If you cannot, set DUAER_PUSH_BACKEND to sse. Then close and reopen the digital organization.
Bad Request: bad webhook: An HTTPS URL must be provided for webhook
Telegram only accepts HTTPS webhook URLs. On self-hosted Duaer, set up TLS on the reverse proxy, then set DUAER_WEBHOOK_URL to the public https:// address.
Only testing or production receives messages
A bot can register one webhook. Each switch between the test and production URL overwrites it, so a published digital organization and an editor test cannot both receive messages. Unpublish while testing, or create a separate bot for testing.
Questions
Why does the Duaer Telegram Trigger miss messages while testing?
A Telegram bot registers one webhook. If the Duaer digital organization is published, unpublish before testing or use a separate test bot.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.