Duaer

Integrations

Set up SendGrid credentials in Duaer

Store SendGrid 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.

Create a SendGrid API key

The Duaer SendGrid API credential:

  1. In SendGrid, open Settings > API Keys and click Create API Key. For sending only, choose Restricted Access and turn on Mail Send.
  2. Copy the key (it is shown only once) into API Key.

Verify the sender address in SendGrid first, with Single Sender or domain authentication, or sends are rejected.

SendGrid API fields in Duaer

In Duaer, choose SendGrid API when you create a credential, then fill in these fields:

  • API Key (secret)

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: SendGrid.

Save the connection in Duaer

Open Credentials and create SendGrid. 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 SendGrid secret values appear in Duaer node parameters?

No. In Duaer, SendGrid secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a SendGrid 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 SendGrid expects, then confirm you can create credentials in that project.

In this section