Integrations
Set up Linear credentials in Duaer
Store Linear 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 Linear credential type
The Duaer Linear node supports two credentials:
- Linear API: in Linear, open Settings > Security & access > Personal API keys, create a key, and put it in API Key.
- Linear OAuth2 API: in Linear, open Settings > API > OAuth applications, create an app, set Callback URL to the Duaer OAuth Redirect URL, and put Client ID and Client Secret in the credential. With Actor set to User, items are created as the person who authorized; with Application, as the app. For Linear Trigger, turn on Include Admin Scope, because creating webhooks needs the admin scope.
Signing Secret is optional. After Linear Trigger registers its webhook, open that webhook in Linear’s webhook settings and copy its signing secret here. Duaer then checks the linear-signature header on every delivery; when empty, Duaer skips the check.
Linear API
In Duaer, choose Linear API when you create a credential, then fill in these fields:
- API Key (secret)
- Signing Secret (secret): The signing secret is used to verify the authenticity of webhook requests sent by Linear.
Duaer nodes that use it: Linear, Linear Trigger.
Linear OAuth2 API
In Duaer, choose Linear OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
- Actor: Default: User. Options: User, Application.
- Include Admin Scope: Grants the "Admin" scope, Needed to create webhooks. Default: off.
- Signing Secret (secret): The signing secret is used to verify the authenticity of webhook requests sent by Linear.
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.
By default, Duaer requests these scopes: :.
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: Linear, Linear Trigger.
Save the connection in Duaer
Open Credentials and create Linear. 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 Linear secret values appear in Duaer node parameters?
No. In Duaer, Linear secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Linear 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 Linear 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.