Duaer

Integrations

Set up Toggl credentials in Duaer

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

Fill in the Toggl credential

The Duaer Toggl API credential is used by Toggl Trigger, which polls for new time entries:

  1. Put the Toggl Track account in Email Address and Password.
  2. To avoid storing a password, copy the API Token from Toggl Profile settings into Email Address and put api_token in Password.

Toggl API fields in Duaer

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

  • Email Address
  • Password (secret)

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

Duaer nodes that use it: Toggl Trigger.

Save the connection in Duaer

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

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

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

In this section