Supabase Grid Integration

The Supabase Grid integration allows users to view, search, inline-edit, create, and delete rows from any Supabase PostgreSQL database table directly inside AppColab Grid without complex ETL or data pipelines.

Supabase Live Grid Preview

What’s Deployed

Component Name Purpose
Named Credential Supabase Connects to your Supabase Project REST endpoint via Supabase External Credential
External Credential Supabase Custom authentication with apikey and Authorization: Bearer <anon_key> headers
Apex Client SupabaseClient.cls PostgREST client supporting listRecords, getRecord, createRecord, updateRecord, deleteRecord, getTableSchema
Apex Data Provider SupabaseGridDataProvider.cls Implements appcg.GridDataProviderV1 and appcg.GridDataMutationProviderV1 with dynamic schema describe and full CRUD
Permission Set Integration_Admin Grants access to Supabase → ApiKey external credential principal

One-Time Manual Setup

1. Get Your Supabase Project URL & Anon Key

  1. Sign in to your Supabase Dashboard and select your project.
  2. Click Project Settings (⚙️) in the sidebar → navigate to API Keys.
  3. Under the Project API keys section:
    • Copy the Project URL (e.g. https://xyzcompany.supabase.co).
    • Copy the anon (public) key (starts with eyJhbGci...).

Supabase API Keys

2. Configure Credentials in Salesforce Setup

2.1 Create the External Credential

  1. Go to Setup (gear icon ⚙️ → Setup).
  2. In the Quick Find box, enter Named Credentials and select Named Credentials.
  3. Click the External Credentials tab → click New:
    • Label: Supabase
    • Name: Supabase
    • Authentication Protocol: Custom
    • Click Save.
  4. In the Principals section, click New:
    • Parameter Name: ApiKey
    • Sequence: 1
    • Click Save.
  5. In the Custom Headers section, click New:
    • Name: apikey
    • Value: Paste your anon key (eyJhbGci...)
    • Sequence Number: 1
    • Click Save.
  6. Click New again under Custom Headers:
    • Name: Authorization
    • Value: Bearer followed by the same anon key (e.g. Bearer eyJhbGci...)
    • Sequence Number: 2
    • Click Save.

Supabase External Credential Setup

2.2 Create the Named Credential

  1. Click the Named Credentials tab (next to External Credentials) → click New:
    • Label: Supabase
    • Name: Supabase
    • URL: Paste your Supabase Project URL (e.g. https://xyzcompany.supabase.co)
    • External Credential: Select Supabase
    • Generate Authorization Header: Leave Unchecked (handled by custom Authorization header)
    • Allow Formulas in HTTP Header: Checked
  2. Click Save.

Supabase Named Credential Setup

3. Assign Permission Set Access

  1. In Salesforce Setup, enter Permission Sets in Quick Find.
  2. Select Integration Admin (or Appcolab Grid Admin).
  3. Click External Credential Principal Access → click Edit.
  4. Add Supabase - ApiKey to Enabled External Credential Principals.
  5. Click Save and verify the permission set is assigned to your Salesforce users.

Creating a Supabase Grid Definition

  1. In Salesforce, open AppColab Grid app → Grid Definitions tab → click New Grid Definition.
  2. Fill in:
    • Grid Settings Name: Supabase_Contacts_Grid
    • Grid Label: Supabase Contacts
    • Is Active?: Checked
    • Data Provider Class: SupabaseGridDataProvider
    • Data Provider Configuration:
      {
  "table": "contacts"
}
  3. Click Save & Next → proceed to Preview.
  4. The Grid automatically discovers all database columns, maps PostgreSQL data types to Grid types, and displays live database records!

Supabase Grid Definition

Supported Grid Features

Feature Details
Dynamic Schema Discovery Queries OpenAPI schema definition to discover column names and types automatically
Inline Editing Modifying cell values sends instant PATCH requests to Supabase PostgREST
Row Insertion Click + Add Row to create new PostgreSQL records directly from Salesforce
Row Deletion Delete database records with automatic UI removal
Server-Side Pagination Supports limit and offset for high-performance navigation through tens of thousands of database rows

Troubleshooting

  • 401 Unauthorized / Invalid API Key: Ensure both apikey and Authorization headers are present in the Supabase External Credential.
  • PGRST200 / relation does not exist: Check that the "table" name in your Data Provider Configuration JSON matches the exact table name in Supabase (e.g., contacts).
  • RLS Blocked: If you have Row Level Security enabled in Supabase, make sure your table policies permit select/insert/update operations for the anon role, or disable RLS for that specific table.