Integrations
Set up Grist credentials in Duaer
Store Grist 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.
Choose a Grist credential type
The Duaer Grist node supports two credentials:
- Grist API: in Grist, open the account menu at the top right, choose Account settings > Developer, and create or copy an API key for API Key.
- Grist OAuth2 API: register an OAuth app in Grist (self-managed Grist must have OAuth apps enabled), set Redirect URI to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, then click Connect my account.
Grist URL: for hosted Grist, leave it empty in the API key credential (keep the default https://api.getgrist.com in OAuth2). For one team, use https://<team>.getgrist.com; self-managed, use your address. Do not include /api.
Grist API
In Duaer, choose Grist API when you create a credential, then fill in these fields:
- API Key (required, secret): In Grist, open the account menu (top right) > Account settings > Developer to create or copy your API key.
- Grist URL: Leave empty for hosted Grist (https://api.getgrist.com). Use https://YOUR_TEAM.getgrist.com for a single team, or your own URL if self-managed. Do not include /api.
Duaer nodes that use it: Grist.
Grist OAuth2 API
In Duaer, choose Grist OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
- Grist URL (required): Defaults to hosted Grist. Use https://YOUR_TEAM.getgrist.com for a single team, or your own URL if self-managed with OAuth apps enabled. Do not include /api. Default: https://api.getgrist.com.
- Custom Scopes: Define custom scopes. Default: off.
- Enabled Scopes: Space-separated list of OAuth2 scopes to request. Default: offline_access doc:read doc:write. Shown when Custom Scopes is on.
Duaer uses the OAuth2 PKCE 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.
By default, Duaer requests these scopes: offline_access doc:read doc:write.
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: Grist.
Save the connection in Duaer
Open Credentials and create Grist. 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 Grist secret values appear in Duaer node parameters?
No. In Duaer, Grist secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Grist 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 Grist 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.