BusyBot
Search all guides

Reference · Credentials

Connect S3 Compatible to BusyBot

Used by 1 BusyBot node.

Type s3Api 7 fields

Fields

FieldTypeRequiredNotes
Endpoint
endpoint		 string Yes —
Region
region		 string Yes —
Access Key ID
accessKeyId		 string Yes —
Secret Access Key
secretAccessKey		 password Yes —
Force Path Style
forcePathStyle		 boolean No —
Ignore SSL Issues
ignoreSSLIssues		 boolean No —
Session Token
sessionToken		 password No —

Setting up S3 Compatible API

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

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

What does a S3 Compatible credential need?

7 fields: Endpoint, Region, Access Key ID, Secret Access Key, Force Path Style, Ignore SSL Issues, Session Token. Required: Endpoint, Region, Access Key ID, Secret Access Key. The values come from your own S3 Compatible account.

How are S3 Compatible 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 S3 Compatible API

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