Duaer

Integrations

Set up X (Twitter) credentials in Duaer

Store X (Twitter) 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 an X credential type

The Duaer X (Twitter) node supports two credentials, both set up in a project app on the X developer portal. First, in the app’s User authentication settings, add the redirect URL shown in the Duaer credential dialog to Callback URI and choose Read and write:

  • X OAuth2 API: recommended. Set Type of App to Web App, copy the OAuth 2.0 Client ID and Client Secret from Keys and tokens into the credential, and click Connect my account.
  • X OAuth API: OAuth 1.0a. Copy API Key and API Key Secret from Keys and tokens into Consumer Key and Consumer Secret, and click Connect my account.

The credential dialog notes that some operations need an X API Basic or Pro plan. Refer to the X API docs.

X OAuth API

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

  • Consumer Key (required, secret)
  • Consumer Secret (required, secret)

Register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth1-credential/callback) with the provider, then click Connect my account in Duaer.

Note from the dialog: Some operations require a Basic or Pro API. Refer to X API Docs (https://developer.x.com/en/docs/twitter-api) for more information.

Duaer nodes that use it: X (Formerly Twitter).

X OAuth2 API

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

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

Duaer uses the OAuth2 PKCE 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: tweet.read users.read tweet.write tweet.moderate.write users.read follows.read follows.write offline.access like.read like.write dm.write dm.read list.read list.write.

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.

Note from the dialog: Some operations require a Basic or Pro API. Refer to X API Docs (https://developer.x.com/en/docs/twitter-api) for more information.

Duaer nodes that use it: X (Formerly Twitter).

Save the connection in Duaer

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

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

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

In this section