Integrations
Common issues with OpenAI in Duaer
This page covers common errors Duaer links to when you use OpenAI. Check the credential and node parameters before chasing the error text.
Quota and rate limits
When Duaer calls OpenAI and the provider returns insufficient quota or a rate limit, check the plan and usage in that provider’s console first. Then confirm the model or resource on the node is still allowed.
A valid credential can still hit a quota error. Before you rotate the key, confirm the allowance is not simply exhausted.
Other checks
Confirm the OpenAI credential points at the right environment and that required node parameters are filled. When a product error links here, follow the error text plus the checks above.
Questions
What should you do first when Duaer reports an insufficient OpenAI quota?
Check usage and plan in the OpenAI provider console, then the model or resource selected on the Duaer node. A valid credential can still mean the allowance is used up.
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.