Day 11: Two Alternatives to n8n — Google Workspace Studio (VIP-Email Demo) and Lyzr Agent Studio (Knowledge Bases, Sub-Agents, a Manager, and API Deployment)

Access: a registered Google Workspace business account (akhil@outskill.com); personal Gmail shows no 'Workspace Studio' icon. Vocabulary maps one-to-one to n8n: Starters (on schedule, email received, chat message, Sheet row added/updated, Drive file added, meeting, form response); Actions (Tasks, Docs, Drive, Sheets add/update row, Gmail label/star) that are 'compatible and super fast within the Google ecosystem'; check/filter branches; AI skills - recap 100 emails, extract information, summarize, decide - and Ask Gemini for anything else. Turning a workflow on 'is as good as publishing inside my n8n canvas.' A discovery page offers templates (daily AI-news briefing 'Monday 8 AM, weekdays').

Limits stated: Google-only (no Outlook), very early ('first 0.1% of folks... getting the demo'), and a fallback rather than a replacement because n8n already covers the ground.

Platform: 'reimagined agentic AI automation', chat-first, compliance badges (HIPAA, CCPA, ISO, GDPR, SOC 2); provider-agnostic models (OpenAI incl. cheap tiers, Anthropic Claude 3.5/3.7 Sonnet, Google, Bedrock, Perplexity, Kimi K2, Llama); memory either Lyzr-native or AWS Agent Core in your own account; a voice feature 'recently introduced... use with a pinch of salt.' Knowledge Base: Create new -> name/description -> default vector store -> add text / website / file (drag a PDF) -> query it directly to preview the closest chunks. Agent: Create Agent -> Name, Description, Model (GPT-4o Mini for the demo) -> Role, Goal, Instructions; 'Generate with AI' interviews you, asks about output format, and recommends tools (Perplexity for breadth vs a News API for control) because live information needs tool calling 'just the way we have done it in n8n.' Tools -> Add -> Configure more tools -> Hacker News -> Top Stories -> Connect (then edit instructions to name the tool). Memory slider (5, 10), optional file/image output, and a Hallucination Manager gated to higher plans. Observed flaw: the news briefer returned a 2023-dated item when asked for the last 24 hours - the knowledge base is static, so 'dynamic' data needs a real tool.

The e-commerce build on three documents (product catalog for 'Awesome Shopper' in INR/USD, return & refund policy, active return tickets): Shopping Assistant (catalog KB, 5 chunks, basic retrieval, memory 10), Refund Specialist (policy KB, instructed tone - 'oh, that's strange', 'sorry to hear that'), Returns Specialist (tickets KB). The argument for splitting: a single agent's context grows with the catalog and ticket volume and drags the whole scope onto an expensive model; modules let you extend 'without having a bumped price for the entirety of operations.' Manager: a normal agent with 'Make this manager' toggled below Instructions, which reveals 'Add an agent' to attach sub-agents; Lyzr recommends high-reasoning models for it (GPT-4o or Claude 3.5); no knowledge base of its own, deeper memory allowed; a canvas view under orchestration shows the graph with editable connection descriptions. Test: 'I want to purchase new shoes and return my umbrella' hit both specialists, including a ticket lookup by customer name.

Launch Agent -> confirm quality -> Name, Category (productivity / customer experience), Industry (retail), Function (customer service), optional welcome message -> Launch App (private by default) -> View Agent opens a hosted chat UI. No HTML embed could be found live; Lyzr appears to have moved to API integration: a custom front end (vibe-coded) posts the message field to the deployed agent endpoint and renders the response - '10, 15 lines of code' - with the key in the environment file as taught in the vibe-coding session; Studio changes propagate without redeploying.

Verdict on 'if starting today': Lyzr is chat-agent scoped - no first-class video/image or broad workflow nodes, limited connectors (HubSpot, Notion, 'major things'), but RAG, vector stores and orchestration are abstracted and model costs bundled into the subscription (Pro ~$99, Startup ~$30-40, as heard). n8n gives 'granular control plus more automation possibilities' at the price of managing RAG, deployment and API keys yourself. Whether Jerry could live on Lyzr depends on whether its connectors cover Gmail, calendar and meetings.

Commercial: keep workflows confidential by selling outcomes on retainer rather than handing over JSON; monetize a custom-GPT coaching bot as a metered SaaS via the OpenAI Assistants API and Stripe (also for revenue shares); one website for a multi-service agency is fine; Samriddhi's method - discovery call -> whiteboard the flow -> client approval -> build; enterprise entry is referrals and free pilots. 'AI wrapper': thin = a prompt on someone else's model; thick = proprietary data + workflow on top (Uber and Perplexity as thick-wrapper examples). Technical: client-side Gmail auth via Firebase rather than credentials in nodes; Google Cloud Console API + custom webhooks to consolidate calendars from non-API sources; Outlook node has near-parity with Gmail; free model routes - Kimi K2, Ollama GPT-OSS, Groq credits (no free API trials from the big labs); AWS EC2 or DigitalOcean for your own server; Perplexity Comet or Claude's Chrome extension for browser automation like LinkedIn requests (HeyReach for rate-limit safety); Apify debugging - swap the static 'dataset' URL segment for the variable, unpin data, enable community nodes, rotating-IP nodes for Meta blocks; exact image matching = reference image + Google Vision API + an accuracy layer; small-doc RAG for coding tools = file injection over Pinecone; Lindy is a simpler prompt-driven alternative to n8n.