rodrigo/budget-view-finance
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix: Supabase client access in n8nWorkflowService

Browse Source 
The commit addresses two TypeScript errors in `n8nWorkflowService.ts`. The first error, TS2445, arises from attempting to access the protected `supabaseUrl` property directly. The second error, TS2339, occurs because the `session` property is not directly available on the `SupabaseAuthClient`. The fix involves adjusting how the Supabase client and its properties are accessed to align with the Supabase library's intended usage.
This commit is contained in:
gpt-engineer-app[bot] 2025-05-20 10:56:58 +00:00
parent 8ec8b4a5c6
commit 12c178aeb7
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/services/n8nWorkflowService.ts
View File

@ -1,3 +1,4 @@
// Service dedicated to n8n workflow operations
import { toast } from "@/hooks/use-toast";
import { supabase } from "@/integrations/supabase/client";
@ -36,12 +37,16 @@ export async function createWorkflowInN8n(email: string): Promise<{ id: string }
return { id: grupo.workflow_id };
}
// Get the URL from an environment variable or build it
const supabaseUrl = import.meta.env.VITE_SUPABASE_URL || "https://tnurlgbvfsxwqgwxamni.supabase.co";
// Call our edge function to create the workflow
const response = await fetch(`${supabase.supabaseUrl}/functions/v1/create-n8n-workflow`, {
const response = await fetch(`${supabaseUrl}/functions/v1/create-n8n-workflow`, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': `Bearer ${supabase.auth.session()?.access_token || ''}`
// Use getSession() to get the current session
'Authorization': `Bearer ${(await supabase.auth.getSession()).data.session?.access_token || ''}`
},
body: JSON.stringify({
email: email,