Reference · Credentials
Connect TimescaleDB to BusyBot
Used by 1 BusyBot node.
Type
timescaleDb 7 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Hosthost | string | Yes | — |
Portport | number | Yes | — |
Databasedatabase | string | Yes | — |
Useruser | string | Yes | — |
Passwordpassword | password | No | — |
SSLssl | options | No | — |
Allow Unauthorized CertsallowUnauthorizedCerts | boolean | No | — |
Setting up TimescaleDB
- In TimescaleDB, create the credential this connection needs — the values listed in the table above. These are issued from your own TimescaleDB account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose TimescaleDB.
- Paste each value into the matching field and save.
- Add the TimescaleDB 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 TimescaleDB credentials?
One node: TimescaleDB. Create the credential once and select it in that node.
What does a TimescaleDB credential need?
7 fields: Host, Port, Database, User, Password, SSL, Allow Unauthorized Certs. Required: Host, Port, Database, User. The values come from your own TimescaleDB account.
How are TimescaleDB 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 TimescaleDB
One credential works across every node below — create it once and reuse it.