Duaer

Integrations

Set up FileMaker credentials in Duaer

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

Connect to the FileMaker Data API

The Duaer FileMaker API credential uses the FileMaker Server Data API:

  • Enable the FileMaker Data API in the FileMaker Server Admin Console first.
  • Host is the server address; Database is the file name without .fmp12.
  • Login and Password are an account in the database whose privilege set has the fmrest extended privilege.

FileMaker API fields in Duaer

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

  • Host
  • Database
  • Login
  • Password (secret)

Duaer nodes that use it: FileMaker.

Save the connection in Duaer

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

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

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

In this section