BusyBot
Search all guides

Reference · Credentials

Connect AWS Lambda to BusyBot

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, 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 AWS Lambda credentials?

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

What does a AWS Lambda credential need?

4 fields: Access Key ID, Secret Access Key, Region, Session Token. Required: Access Key ID, Secret Access Key, Region. The values come from your own AWS Lambda account.

How are AWS Lambda 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 AWS Lambda

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