Reference · Credentials
Form.io API credentials
Used by 1 BusyBot node.
Type
formIoApi 5 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Environmentenvironment | options | Yes | Cloud-hosted uses formio.form.io / api.form.io. Self-hosted requires the Domain field below. |
Self-Hosted Domaindomain | string | No | Base URL of your self-hosted Form.io instance (e.g. https://forms.mycompany.com). Required when Environment is "Self-hosted". |
Emailemail | string | Yes | Your Form.io account email address. |
Passwordpassword | password | Yes | Your Form.io account password. |
Webhook Shared SecretwebhookSecret | password | No | Optional shared secret used to verify incoming webhook requests. Auto-generated by the trigger if blank. |
Setting up Form.io API
- 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.
- In BusyBot, open Credentials → Add credential and choose Form.io API.
- Paste each value into the matching field and save.
- 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 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 Form.io API
One credential works across every node below — create it once and reuse it.