Integrations
Set up S3 credentials in Duaer
Store S3 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.
Connect to S3-compatible storage
The Duaer S3 credential is for storage with an S3-compatible API, such as MinIO, Cloudflare R2, or Alibaba Cloud OSS. For Amazon S3 itself, use the AWS credential and the AWS S3 node.
- S3 Endpoint must include http:// or https://, such as http://minio:9000 for MinIO, https://<account-id>.r2.cloudflarestorage.com for R2, or https://oss-cn-hangzhou.aliyuncs.com for OSS.
- Region is where the storage lives. Use auto for R2; keep us-east-1 for MinIO without a region.
- Create Access Key ID and Secret Access Key in the storage console, with read and write on the buckets you need only.
- By default, Duaer puts the bucket name in the host (bucket.endpoint). For path-only services such as MinIO, turn on Force Path Style to use endpoint/bucket instead.
S3 fields in Duaer
In Duaer, choose S3 when you create a credential, then fill in these fields:
- S3 Endpoint
- Region: Default: us-east-1.
- Access Key ID
- Secret Access Key (secret)
- Force Path Style: Default: off.
- Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.
Duaer nodes that use it: S3.
Save the connection in Duaer
Open Credentials and create S3. 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. The matching node is under the related node.
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 S3 secret values appear in Duaer node parameters?
No. In Duaer, S3 secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a S3 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 S3 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 workflow. 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.