Duaer

Integrations

Set up Postmark credentials in Duaer

Store Postmark 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 a Postmark server API token

The Duaer Postmark API credential serves Postmark Trigger:

  1. In Postmark, open Servers, pick the server whose events you want, and go to the API Tokens tab.
  2. Copy the Server API token into Server API Token.

Use the server token, not the Account API token. Postmark Trigger registers a webhook on that server, so Duaer must be reachable from the internet.

Postmark API fields in Duaer

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

  • Server API Token (secret)

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

Duaer nodes that use it: Postmark Trigger.

Save the connection in Duaer

Open Credentials and create Postmark. 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.

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 Postmark secret values appear in Duaer node parameters?

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

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

In this section