Integrations
Set up Supabase credentials in Duaer
Store Supabase 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 the Supabase host and secret key
The Duaer Supabase API credential needs two values:
- Host: the project URL, such as https://<project-ref>.supabase.co. If you copied the Data API URL, remove the trailing /rest/v1.
- Secret Key: create or copy a secret key under the project’s API Keys settings. Legacy service_role secrets also work.
A secret key bypasses Row Level Security and can read and write the whole project. Keep it in the Duaer credential only, never in node parameters or front-end code.
Use Supabase OAuth2
- Create an OAuth app in Supabase.
- In Duaer, create a Supabase OAuth2 API credential and connect it.
- On the Supabase node, set Authentication to OAuth2 and select that credential.
- Choose the project. Host and Secret Key are not used in this mode.
The same Supabase OAuth2 API credential can be offered to an MCP connection that uses Supabase OAuth2.
Supabase API
In Duaer, choose Supabase API when you create a credential, then fill in these fields:
- Host: Your Supabase project URL without the /rest/v1 path. If you copied the full Data API URL, remove the /rest/v1 suffix.
- Secret Key (secret): Your Supabase project secret key. You can create one in the API Keys settings (https://supabase.com/dashboard/project/_/settings/api-keys) of your project. Legacy service_role secrets are also supported.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Supabase.
Supabase OAuth2 API
In Duaer, choose Supabase OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
Duaer uses the OAuth2 Authorization Code grant for this type.
In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.
Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.
Duaer nodes that use it: Supabase.
Save the connection in Duaer
Open Credentials and create Supabase. 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 Supabase secret values appear in Duaer node parameters?
No. In Duaer, Supabase secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Supabase 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 Supabase expects, then confirm you can create credentials in that project.
Can the Supabase node in Duaer use OAuth?
Yes. Set Authentication to OAuth2 and select a Supabase OAuth2 API credential. That mode connects by project and does not use Host or Secret Key.
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.