How it works
To connect Google BigQuery and Supabase, you don't need a developer: a ready-made scenario links them in minutes.
- Starts when: File Created
- Check: Loop Over Items
- Then: Set File ID
- Check: Validate File
- If yes: Check for Duplicates
- Check: IF Duplicate Check
- If yes: Log Duplicate
- Then: Slack Duplicate Notification
- If no: Debug File ID
- Then: Delete old Doc
- Then: Delete Old Data Rows
- Then: Insert Metadata
- Then: Download File
- Check: Switch
- If yes: Extract from File PDF
- Then: Supabase Vector Store
- If no: Extract from TXT
- If no: Extract from CSV
- Then: Aggregate
- Then: Summarize
- Then: Set Schema
- Then: Schema Document Metadata
- Then: Insert Table Rows
- If no: Extract from XLSX
- If no: Extract from RTF
- If no: Extract from DOC
- If no: Set Error Type
- Then: Error Logger
- Then: Error Notification
- Starts when: Update to File
- Then: Embeddings OpenAI
- Then: Default Data Loader
- Then: RAG AI Agent
- Then: OpenAI Chat Model
- Then: Postgres Chat Memory
- Then: List Documents
- Then: Query Document Rows
- Then: Character Text Splitter
- Starts when: When chat message received
- Then: Edit Fields2
- Then: Supabase Vector Store2
- Then: Embeddings OpenAI2
- Then: Get Full Document Text - Get File Contents
You can launch this Google BigQuery + Supabase integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.