A: Hey Zeroleft!

Yes, you can definitely do most of that with AgenticFlow:

1. Train Chatbot (Claude 3.7 Sonnet, URLs, PDFs):
Yes! Connect your Anthropic API key (BYOK) to use Claude 3.7 Sonnet.
Upload PDFs directly to the Agent's Knowledge Base (this feature is live!).
Add URLs for the agent to crawl for knowledge.

2. Embed on Site:
Yes, you can embed the trained agent as a chat widget on your site using the provided script.

3. Authenticate Users with Supabase & Conditional Logic:
Yes, this is achievable via API calls.
When a user interacts with the embedded chat, your website frontend would first handle the login/identification.
Your frontend calls your Supabase backend to check if the user exists.

Based on Supabase's response:
- User Exists: Your frontend then initializes/allows the AgenticFlow chat for that authenticated user.
- User Doesn't Exist: Your frontend can redirect them to a sales form/contact, or display a message to contact sales, before even loading the full AgenticFlow chat if desired.

Alternatively, within an AgenticFlow workflow (triggered by the chat), you could use the API Call node to query your Supabase table (if Supabase exposes a suitable REST API endpoint for user lookup). The workflow could then branch its logic based on the API response (e.g., provide standard info if user exists, or give a "contact sales" message if not).

In short: Training with PDFs/URLs and embedding is standard. Supabase authentication requires your frontend to interact with Supabase first, or for AgenticFlow to call a Supabase API endpoint, then control chat access/flow accordingly.

— Sean