Reference · Credentials
Connect FileMaker to BusyBot
Used by 1 BusyBot node.
Type
fileMakerApi 4 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Hosthost | string | Yes | myserver.example.com |
Databasedb | string | Yes | — |
Loginlogin | string | Yes | — |
Passwordpassword | password | Yes | — |
Setting up FileMaker API
- In FileMaker API, create the credential this connection needs — the values listed in the table above. These are issued from your own FileMaker API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose FileMaker API.
- Paste each value into the matching field and save.
- Add the FileMaker node to a workflow, select this credential, and run a simple operation to confirm it authenticates.
Security
- Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
- Grant the minimum scopes or permissions the operations you actually use require.
- Rotate the credential periodically, and immediately if it may have been exposed.
- Credentials are scoped to your account — a workflow cannot use another account's.
Frequently asked questions
Which BusyBot nodes use FileMaker credentials?
One node: FileMaker. Create the credential once and select it in that node.
What does a FileMaker credential need?
4 fields: Host, Database, Login, Password. Required: Host, Database, Login, Password. The values come from your own FileMaker account.
How are FileMaker secrets stored?
Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.
Nodes that use FileMaker API
One credential works across every node below — create it once and reuse it.