Integrations
Set up Zep credentials in Duaer
Store Zep 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.
Fill in the Zep credential
The Duaer Zep Api credential is used by the Zep memory and Zep vector store nodes. The credential dialog notes this Zep integration is deprecated and will be removed in a future version:
- Zep Cloud: turn on Cloud, copy the API key from the project settings in the Zep dashboard, and put it in API Key.
- Zep open source: keep Cloud off, put the server address, such as http://zep:8000, in API URL, and fill in API Key if the server has one.
When Duaer runs in Docker, do not use localhost for the host; use the service name or the host address.
Zep Api fields in Duaer
In Duaer, choose Zep Api when you create a credential, then fill in these fields:
- API Key (secret)
- Cloud: Whether you are adding credentials for Zep Cloud instead of Zep Open Source. Default: off.
- API URL: Default: http://localhost:8000. Shown when Cloud is off.
Note from the dialog: This Zep integration is deprecated and will be removed in a future version.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Zep, Zep Vector Store.
Save the connection in Duaer
Open Credentials and create Zep. 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 Zep secret values appear in Duaer node parameters?
No. In Duaer, Zep secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Zep 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 Zep 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.