🥐Quaso
Log in

Guide

How Quaso works

A tour of the building blocks: connections, triggers, the browser, file processing, and the advanced bits that let your agents run real production workloads.

Overview

Quaso is an AI agent that connects to your tools and gets work done on your behalf. Instead of just answering questions like a chatbot, Quaso actually takes action: it sends emails, updates spreadsheets, files tickets, posts to Slack, and a lot more.

You interact with Quaso through conversation. Describe what you need, and it will ask any clarifying questions it needs, hook up the relevant services, and execute. You can also set triggers so it runs automatically on a schedule, when a specific email arrives, or when another event fires.

Quaso integrates with thousands of apps out of the box, and you can point it at any HTTP API directly if a built-in integration is missing. It also has its own cloud sandbox where it can run code, process files, and (thanks to our partnership with Notte) drive a real browser to interact with software that has no API. Because it reasons step by step, it can handle edge cases that would break a rigid automation tool.

Quaso is built for founders, operators, and professionals who want to automate real work, especially the kind of business processes that need to run reliably around the clock: support triage, lead routing, reporting, ops workflows.

Connections

Connections are how Quaso reaches your apps. There are over 3,000 built-in integrations, plus the ability to call any HTTP API or MCP server. If a service doesn't have an API at all, Quaso can still use it through the browser. Just say something like "Connect my Gmail" to get started.

How connections work

  1. You authorize access. Quaso opens a secure login flow and you sign in directly with the service.
  2. You choose what to grant.Each connection unlocks specific tools (e.g. "send email", "create ticket"). Quaso asks before activating anything new.
  3. The tools become available. From there on Quaso can use them to complete work for you.

Custom APIs & MCP servers

Quaso connects to any HTTP API or MCP server. Register a custom Streamable-HTTP MCP server (like Supabase) under Settings → MCP servers: paste its URL, add a bearer token or header if it needs one, and hit Test connection to see the tools it exposes. From then on the agent can call those tools in chat. Tokens are encrypted at rest and never shown to the model. Works with public APIs and your own internal services too.

Security

  • Credentials are encrypted at rest; Quaso never sees your password.
  • OAuth is used wherever the service supports it.
  • You can revoke access at any time from Settings → Connections.
  • After approving an app, you control exactly which tools Quaso can use. Read-only is fine when that's all you want.

Triggers

Triggers let Quaso run automatically. On a schedule, when an email arrives, when a calendar event changes, or when another service sends an event - anything you can describe.

How to create one

Describe what you want and when. Examples that work right away:

  • "Send me a daily briefing every morning at 9am."
  • "When I get an email with an attachment, file it in Drive."
  • "Every Friday, post a recap of closed deals to #sales."

What you can trigger on

Schedule (daily, weekly, custom schedule), external events (another system sending data to a URL Quaso gives you), RSS feeds, Gmail (new mail or label applied), Google Calendar (event created, changed, starting), Google Drive (file or folder change), Notion (page or database updates), HubSpot (CRM changes), GitHub (PRs, issues, pushes), text messages and email replies for talking to your agents on the go.

Multiple triggers per agent

One agent can hold several triggers. An inbox assistant might run a daily briefing, draft replies on new mail, and star important messages, all from the same agent definition.

Text & Email Messaging

Quaso can send and receive messages over email or text (iMessage and RCS). When someone replies, the agent picks it up and can keep the conversation going or take action on the response.

Email anyone (with permission)

You can add any email address as a contact. The recipient confirms via a one-click verification link, and after that your agent can send them reports, notifications, or approval requests directly.

Two-way conversations

Replies to Quaso's messages land back in the agent. The recipient doesn't need their own Quaso account: they just reply like they would to any other email or text.

Setting it up

  1. Ask your agent to add a contact method.
  2. The recipient verifies (link for email, text reply for phone).
  3. Your agent can message them from then on.

File Processing

Quaso can shuttle files between connections (Gmail, Drive, Slack, APIs), process them, and create new ones from scratch.

What it can do

  • Transfer attachments and downloads between services.
  • Convert images, audio, documents into different formats.
  • Create spreadsheets, PDF reports, even videos with narration.
  • Edit images and clean up data files.
  • Merge & split PDFs and large files.
  • Analyze long CSVs and produce summary stats and charts.

Combine with triggers

File processing pairs naturally with triggers. Pull data from your CRM every morning and generate a summary PDF. Save every receipt that lands in your inbox into a Drive folder and log it in a spreadsheet. Watch a public dataset and alert if anything moves.

Browser

Every Quaso agent has a built-in browser, powered by Notte. That means it can navigate authenticated sites, fill forms, click through multi-step flows, and pull data from pages that don't expose an API. This is what makes Quaso's automation surface essentially endless.

How to use it

Describe what you need. Quaso will open a browser if that's the best tool for the job. You can also say "use the browser to..." if you want to be explicit, though usually it's smarter to let the agent pick: built-in integrations are often faster, cheaper, and more reliable when they exist.

What it can do

  • Navigate complex pages, type, click, scroll dynamic content.
  • Fill forms and walk multi-step flows.
  • Extract data from tables, lists, article bodies.
  • Upload and download files.
  • Hand off sign-in or CAPTCHA to you when a site demands it.

Logins and CAPTCHAs

Quaso never asks for your password. When a site needs you to sign in or solve a challenge, the agent surfaces a live browser preview right in the conversation. You take over, type your credentials or solve the CAPTCHA, hand control back, and the agent resumes.

Persistent sessions

Each agent keeps its own browser profile. Once you've signed in through a preview, the agent stays signed in for future tasks. Cookies, preferences, and any data the site stored carry over the same way.

Use cases

Things people actually run

Real workflows Quaso handles across teams. Click any card to open it in the composer, edit to taste, and hit send.

Comms

Morning briefingEvery morning at 8am, summarize my calendar, urgent emails, and Linear assignments into a one-page brief and Slack it to me.Inbox triageRead my Gmail: archive newsletters and promos, draft replies to anything that needs an answer, and surface what's truly urgent.Meeting recapWhen a new Fireflies transcript lands, pull action items into Linear tickets and email attendees a clean recap.Focus block defenderWhen my day is fragmented, look for meetings I can move and propose a schedule that gives me back a 2-hour focus block.Slack ping nudgerIf someone @mentions me on Slack and I haven't answered in 2 hours, text me the thread link with context.Support triageRun first-line support: triage incoming tickets, draft answers from our docs, escalate the hard cases to me.

Operations

Chief of staffBe my chief of staff. Watch the team Slack and Linear, surface what needs my attention today, and ping me only when something is on fire.Stripe to ledgerWhen Stripe sends a payment webhook, log the line item in my accounting sheet and update the customer's CRM record.Release notesWhen PRs merge to main on GitHub, summarize the diffs and update our public changelog in Notion.Reconcile QBOEvery Monday, reconcile my QuickBooks entries against my bank feed and flag any mismatches.Publishing queueWhen I move a post to 'Ready' in Notion, schedule it on Hootsuite and notify #marketing with the publish time.Webhook backboneBe the glue between our tools. Receive incoming webhooks, route them to the right humans, and persist the right rows to Supabase.

Admin

Receipts collectorPull receipts out of my Gmail and Doordash inbox, then file them into the right month folder in Drive.Personal assistantBe my PA. Connect to my calendar, email, and tasks, and let me text you to schedule things, draft replies, or remember details.Pay stub archiveLog into Workday, download my last 12 months of pay stubs and tax forms, and save them under 2026/HR/ in Dropbox.Subscription auditorAudit my recurring charges across email receipts and bank statements, flag the unused ones, and use the browser to cancel them.ParalegalBe my paralegal. Watch contract deadlines through the Clio API, summarize new docs, and flag anything that needs attorney review.Office huntOpen the browser, find me office space in SoHo within these specs, email landlords, and walk the lead through negotiation.

Growth

LinkedIn sourcingUse the browser on LinkedIn, find prospects matching this ICP, enrich with Hunter.io, and drop them into the right HubSpot pipeline.Pre-meeting briefingWhen a Calendly booking comes in, research the attendee's company and post a 5-line brief to #sales.Re-engage VIPsFind high-value customers we haven't talked to in 60 days, suggest a relevant event we could invite them to, and draft the outreach.Daily LinkedInEach weekday, send 5 connection requests to ICP folks in my network and repost 2 relevant pieces from my industry feed.Sales qualificationRun the first round of sales conversations until a lead is qualified, then text me when it's ready for handoff.Open-rate follow-upTrack opens on my outbound emails with a pixel. When a prospect opens one, research them and draft a personalized follow-up for me to review.

Insights

Competitor watchWatch competitor pricing and feature pages weekly. For major changes, research and tell me what it means for our positioning.Podcast monitorListen across these podcasts and Substacks for anything related to [topic], and email me a weekly digest with timestamps.Company enrichmentWhen I add a company to my Airtable tracker, enrich it with tech stack, funding round, and key contacts.Weekly exec digestEach Friday, summarize what shipped across Linear and GitHub. Call out velocity shifts and what's stuck.Deep researchWhen I label a Gmail thread 'research', do a Perplexity-style deep dive on the topic and reply with findings.Sales call coachWeekly, review our sales call transcripts. Surface what closers do differently and send concrete coaching notes to those who need it.

Security

How we keep your data safe

Quaso is built by the team behind Notte, the browser infrastructure company powering AI agents at production scale. Quaso runs on the exact same stack: same browser fleet, same isolation guarantees, same security posture. You get a product surface built for end users, on infrastructure already vetted by enterprise teams running browser agents in production.

SOC 2 compliant

We follow SOC 2 controls across security, availability, and confidentiality. Every control, our auditor reports, sub-processor list, and policy documents live on our public trust portal: trust.notte.cc. Request access there to download the latest report under NDA.

Isolated execution

Every Quaso agent runs in its own sandboxed environment. Browser sessions, code execution, and any virtual machines we spin up for an agent are fully isolated from other workspaces. Your data, code, and credentials never cross tenant boundaries.

Your data is yours

  • We do not sell customer data, ever.
  • Your conversations and outputs are never used to train third-party AI models.
  • Credentials you share for direct API connections are stored in an encrypted vault with strict access controls. Quaso never sees plaintext passwords for OAuth integrations: the service you connect to handles auth directly.
  • Internal access to customer data is gated by our admin tooling and requires explicit customer approval. Nobody on the team browses workspaces uninvited.

Encryption

Data is encrypted at rest with AES-256 and in transit with TLS 1.2+. Secrets and integration tokens get an additional layer of envelope encryption inside the credential vault.

Sub-processors

We keep the list short and intentional. The full, always-current roster lives on trust.notte.cc. High-level: Anthropic and OpenAI for model inference, Supabase for the application database, Vercel for hosting the web app, Notte for browser infrastructure, and Stripe for billing.

Vulnerability disclosure

If you find a security issue, please email security@notte.cc instead of disclosing publicly. We will acknowledge within one business day, work in good faith to fix it, and keep you in the loop. We do not pursue researchers acting in good faith under a reasonable disclosure policy, and we may extend a bounty for high-impact reports at our discretion.

Deleting your data

You can delete your workspace at any time from settings. That wipes your conversations, threads, agent files, browser session state, and integration credentials. Retention for backups follows the schedule documented on the trust portal.

Legal

Full agreements: Terms of Use and Privacy Policy.