Integrations
Set up Vercel AI Gateway credentials in Duaer
Store Vercel AI Gateway connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
Get a Vercel AI Gateway key
The Duaer Vercel AI Gateway credential is used by the Vercel AI Gateway chat model node:
- In the Vercel dashboard, open AI Gateway > API Keys, create a key, and put it in API Key or OIDC Token. When Duaer runs on Vercel, an OIDC token also works.
- Keep https://ai-gateway.vercel.sh/v1 in Base URL.
Vercel AI Gateway fields in Duaer
In Duaer, choose Vercel AI Gateway when you create a credential, then fill in these fields:
- API Key or OIDC Token (required, secret): Your credentials for the Vercel AI Gateway.
- Base URL (required): The base URL for your Vercel AI Gateway instance. Default: https://ai-gateway.vercel.sh/v1.
When you save, Duaer tests the connection with these values.
Save the connection in Duaer
Open Credentials and create Vercel AI Gateway. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.
Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys.
Who can use this credential
Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
Questions
Do Vercel AI Gateway secret values appear in Duaer node parameters?
No. In Duaer, Vercel AI Gateway secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Vercel AI Gateway credential from saving in Duaer?
Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Vercel AI Gateway expects, then confirm you can create credentials in that project.
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.