Reference · Credentials
Connect Splunk to BusyBot
Used by 1 BusyBot node.
Type
splunkApi 3 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Auth TokenauthToken | password | Yes | Splunk authentication token. Generate in Splunk: Settings > Tokens > New Token. |
Base URLbaseUrl | string | Yes | Splunk management API URL (protocol, domain, and port). |
Allow Self-Signed CertificatesallowUnauthorizedCerts | boolean | No | Whether to connect even if SSL certificate validation is not possible. |
Setting up Splunk API
- In Splunk API, create the credential this connection needs — the values listed in the table above. These are issued from your own Splunk API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Splunk API.
- Paste each value into the matching field and save.
- Add the Splunk 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 Splunk credentials?
One node: Splunk. Create the credential once and select it in that node.
What does a Splunk credential need?
3 fields: Auth Token, Base URL, Allow Self-Signed Certificates. Required: Auth Token, Base URL. The values come from your own Splunk account.
How are Splunk 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 Splunk API
One credential works across every node below — create it once and reuse it.