Duaer

Integrations

Set up Lemlist credentials in Duaer

Store Lemlist 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 lemlist API key

The Duaer Lemlist API credential needs one key:

  1. In lemlist, open Settings > Integrations and generate a key in the API section.
  2. Put it in API Key and save.

Lemlist Trigger registers a webhook with the service, so Duaer must be reachable from the internet.

Lemlist API fields in Duaer

In Duaer, choose Lemlist 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: Lemlist, Lemlist Trigger.

Save the connection in Duaer

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

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

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

In this section