BusyBot
Search all guides

Reference · Credentials

Connect Elastic Security to BusyBot

Used by 1 BusyBot node.

Type elasticSecurityApi 5 fields

Fields

FieldTypeRequiredNotes
Base URL
baseUrl		 string Yes Kibana URL (include port)
Authentication Type
authType		 options Yes Authentication method
Username
username		 string No Kibana username (required for Basic Auth)
Password
password		 password No Kibana password (required for Basic Auth)
API Key
apiKey		 password No Kibana API key (required for API Key auth)

Setting up Elastic Security API

  1. In Elastic Security API, create the credential this connection needs — the values listed in the table above. These are issued from your own Elastic Security API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Elastic Security API.
  3. Paste each value into the matching field and save.
  4. Add the Elastic Security 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 Elastic Security credentials?

One node: Elastic Security. Create the credential once and select it in that node.

What does a Elastic Security credential need?

5 fields: Base URL, Authentication Type, Username, Password, API Key. Required: Base URL, Authentication Type. The values come from your own Elastic Security account.

How are Elastic Security 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 Elastic Security API

One credential works across every node below — create it once and reuse it.