Duaer

Integrations

Set up WooCommerce credentials in Duaer

Store WooCommerce 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 WooCommerce REST API keys

The Duaer WooCommerce API credential uses a key pair generated in the store admin:

  1. In the WordPress admin, open WooCommerce > Settings > Advanced > REST API and click Add key.
  2. Pick an administrator user, set Permissions to Read/Write (Read if you only fetch data), and click Generate API key.
  3. Put Consumer key (starts with ck_) and Consumer secret (starts with cs_) in the credential. The secret is not shown again after you leave the page.
  4. Put the store home page, such as https://shop.example.com, in WooCommerce URL.

The store should use HTTPS. If the server drops the Authorization header, as some hosts and caching plugins do, turn on Include Credentials in Query to send the keys as query parameters.

WooCommerce API fields in Duaer

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

  • Consumer Key (secret)
  • Consumer Secret (secret)
  • WooCommerce URL
  • Include Credentials in Query: Whether credentials should be included in the query. Occasionally, some servers may not parse the Authorization header correctly (if you see a “Consumer key is missing” error when authenticating over SSL, you have a server issue). In this case, you may provide the consumer key/secret as query string parameters instead. Default: off.

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

Duaer nodes that use it: WooCommerce, WooCommerce Trigger.

Save the connection in Duaer

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

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

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

In this section