BusyBot
Search all guides

Reference · Credentials

Connect MISP to BusyBot

Used by 1 BusyBot node.

Type mispApi 3 fields

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes MISP automation key from Event Actions > Automation.
Base URL
baseUrl		 string Yes URL of your MISP instance (e.g., https://misp.example.com).
Allow Unauthorized Certs
allowUnauthorizedCerts		 boolean No Connect even if SSL certificate validation fails.

Setting up MISP API

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

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

What does a MISP credential need?

3 fields: API Key, Base URL, Allow Unauthorized Certs. Required: API Key, Base URL. The values come from your own MISP account.

How are MISP 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 MISP API

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