BusyBot

Reference · Credentials

AWS Lambda credentials

Used by 1 BusyBot node.

Type awsLambdaApi 4 fields

Fields

FieldTypeRequiredNotes
Access Key ID
accessKeyId		 string Yes AWS IAM access key ID. Found in the AWS IAM console under Security Credentials.
Secret Access Key
secretAccessKey		 password Yes AWS IAM secret access key. Shown only once when creating the access key.
Region
region		 string Yes AWS region where your Lambda functions are deployed (e.g., us-east-1, eu-west-1).
Session Token
sessionToken		 password No Optional AWS STS session token for temporary credentials. Leave empty for permanent IAM credentials.

Setting up AWS Lambda

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

Nodes that use AWS Lambda

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