Duaer

Integrations

Set up Marketstack credentials in Duaer

Store Marketstack 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 Marketstack API key

The Duaer Marketstack API credential needs one key:

  1. Sign in to the Marketstack dashboard and copy the API Access Key.
  2. Put it in API Key and save.

Use HTTPS works on paid plans only; keep it off on the free plan.

Marketstack API fields in Duaer

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

  • API Key (secret)
  • Use HTTPS: Whether to use HTTPS (paid plans only) Default: off.

Duaer nodes that use it: Marketstack.

Save the connection in Duaer

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

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

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

In this section