Reference · Credentials
Connect Supabase to BusyBot
Used by 1 BusyBot node.
Type
supabaseApi 2 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Supabase URLhost | string | Yes | Your Supabase project URL. Found in project settings under API > Project URL. |
Service Role KeyserviceRole | password | Yes | Service role key from Supabase project settings > API > Project API Keys. |
Setting up Supabase API
- In Supabase API, create the credential this connection needs — the values listed in the table above. These are issued from your own Supabase API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Supabase API.
- Paste each value into the matching field and save.
- Add the Supabase 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 Supabase credentials?
One node: Supabase. Create the credential once and select it in that node.
What does a Supabase credential need?
2 fields: Supabase URL, Service Role Key. Required: Supabase URL, Service Role Key. The values come from your own Supabase account.
How are Supabase 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 Supabase API
One credential works across every node below — create it once and reuse it.