Duaer

Integrations

Set up PostHog credentials in Duaer

Store PostHog 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 the PostHog project API key

The Duaer PostHog node sends events and identifies users with the project API key:

  1. In PostHog, open Project settings, copy the Project API Key (starts with phc_), and put it in API Key.
  2. Set URL for the project region: https://us.i.posthog.com for the US, https://eu.i.posthog.com for the EU, or your own address when self-hosted.

PostHog API fields in Duaer

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

  • URL: Default: https://app.posthog.com.
  • API Key (secret)

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

Duaer nodes that use it: PostHog.

Save the connection in Duaer

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

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

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

In this section