BusyBot
Search all guides

Reference · Credentials

Connect Form.io to BusyBot

Used by 1 BusyBot node.

Type formIoApi 5 fields

Fields

FieldTypeRequiredNotes
Environment
environment		 options Yes Cloud-hosted uses formio.form.io / api.form.io. Self-hosted requires the Domain field below.
Self-Hosted Domain
domain		 string No Base URL of your self-hosted Form.io instance (e.g. https://forms.mycompany.com). Required when Environment is "Self-hosted".
Email
email		 string Yes Your Form.io account email address.
Password
password		 password Yes Your Form.io account password.
Webhook Shared Secret
webhookSecret		 password No Optional shared secret used to verify incoming webhook requests. Auto-generated by the trigger if blank.

Setting up Form.io API

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

One node: Form.io Trigger. Create the credential once and select it in that node.

What does a Form.io credential need?

5 fields: Environment, Self-Hosted Domain, Email, Password, Webhook Shared Secret. Required: Environment, Email, Password. The values come from your own Form.io account.

How are Form.io 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 Form.io API

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