Reference · Credentials
Connect Elasticsearch to BusyBot
Used by 1 BusyBot node.
Type
elasticsearchApi 3 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Base URLbaseUrl | string | Yes | Elasticsearch cluster URL (include port) |
Usernameusername | string | Yes | Elasticsearch username |
Passwordpassword | password | Yes | Elasticsearch password |
Setting up Elasticsearch API
- In Elasticsearch API, create the credential this connection needs — the values listed in the table above. These are issued from your own Elasticsearch API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Elasticsearch API.
- Paste each value into the matching field and save.
- Add the Elasticsearch 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 Elasticsearch credentials?
One node: Elasticsearch. Create the credential once and select it in that node.
What does a Elasticsearch credential need?
3 fields: Base URL, Username, Password. Required: Base URL, Username, Password. The values come from your own Elasticsearch account.
How are Elasticsearch 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 Elasticsearch API
One credential works across every node below — create it once and reuse it.