Duaer

Integrations

Set up Harvest credentials in Duaer

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

Choose a Harvest credential type

The Duaer Harvest node supports two credentials:

  • Harvest API: on Harvest Developers, click Create new personal access token and put it in Access Token. The Account ID on that page goes in the Harvest node.
  • Harvest OAuth2 API: click Create new OAuth2 application on the same page, set Redirect URL to the Duaer OAuth Redirect URL, put Client ID and Client Secret in the credential, then click Connect my account.

Harvest API

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

  • Access Token (secret): Visit your account details page, and grab the Access Token. See Harvest Personal Access Tokens (https://help.getharvest.com/api-v2/authentication-api/authentication/authentication/).

Duaer nodes that use it: Harvest.

Harvest OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: all.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Harvest.

Save the connection in Duaer

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

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

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

In this section