Tell Charlie which apps your PAL should use
He adds the connectors while you talk.
Charlie
PALs now work in the tools you already use.
Connect Gmail, Google Calendar, Notion, Linear, Stripe or any of more than twenty apps in one click, add them to a PAL, and ask for what you need the way you'd ask a colleague. It does the work while you keep talking and tells you when it's done. Free on every plan.
Connect once, talk, and it's done
How Connectors work
Pick an app, sign in once
Open Connectors in PAL Maker and pick an app. You get a normal sign-in screen, the same one you'd see connecting that app to anything else. No code and, for most apps, no keys to paste.
Linear
OAUTH · CONNECT
Google Calendar
OAUTH · CONNECT
Notion
OAUTH · CONNECT
Add it to a PAL
Add the connector under Capabilities and tell the PAL what it should use it for. If you build with Charlie, tell him which apps the PAL should use and he adds them while you talk. Add or remove apps later without touching the rest of the PAL.
Linear
ADDED · FILE AND READ ISSUES
Google Calendar
ADDED · READ AND BOOK
Notion
ADDED · READ AND WRITE
Ask like you'd ask a colleague
"Close out yesterday's meeting." "File that bug." "What's the client waiting on?" You never name a tool. The PAL works out which apps the job needs, does the work while you keep talking, and tells you when it's done.
Close out yesterday's pricing meeting.
READING GRANOLA NOTES
FILING 3 ISSUES IN LINEAR
On it. Where were we on the Q1 plan?
Cal.com · Stripe
“Can we talk next week? Tuesday afternoon works.”
Tuesday at 3:00 is open. You’re booked, and the deposit link from Stripe is on its way.
Cal.com
Tuesday 3:00 · booked
Stripe
Deposit link sent · done
THE VISITOR WHO GETS BOOKED
Someone clicks Talk to us on your site and asks for time next week. The PAL checks your availability in Cal.com, books the slot while they're still talking and confirms it out loud. If they need to pay a deposit, Stripe makes the payment link.
Pylon · LogRocket · Linear · Slack
“The export button just spins.”
Found it. The export call is timing out. Filed with the replay, engineering told in Slack, ticket marked waiting on us.
Pylon
Ticket read · done
LogRocket
Session found · done
Linear
Issue filed with replay · running
Slack
Telling #eng · queued
THE BUG THAT FILES ITSELF
A customer in your help widget says the export button just spins. The PAL pulls up their ticket in Pylon, finds the error in their LogRocket session, files the issue in Linear with the replay attached, tells the engineering channel in Slack and moves the ticket to waiting on us.
Granola · Linear · Notion · Google Calendar · Slack
“Close out yesterday’s pricing meeting.”
Done. Owners and dates are in Linear, the log is in Notion, the follow-up is Thursday and the recap is in the channel.
Granola
Notes read · done
Linear
3 issues · running
Notion
Decision log · running
Google Calendar
Follow-up Thursday · booked
THE MEETING THAT CLOSES ITSELF
Say "close out yesterday's pricing meeting" on your way to the next one. The PAL reads the decisions back from your Granola notes, and by the time you sit down the action items are in Linear, the decision log is in Notion, the follow-up is on the calendar and the recap is in Slack.
Gmail · Google Drive
“What’s the client waiting on?”
Two dates for the kickoff, the 14th and the 21st, from the signed contract. The reply is in your drafts, not sent.
Gmail
Thread read · done
Google Drive
Signed contract found · done
Gmail
Reply drafted · waiting for you
THE INBOX, HANDLED
On the ride in, ask what the client is waiting on. The PAL finds the thread in Gmail, pulls the signed contract from Google Drive and drafts the reply with the two dates they asked for. It doesn't send. You arrive, read it over, change a word, and hit send yourself.
Webflow · Stripe
“I need a waitlist page for the pilot. Dark theme. Fifty dollars a seat.”
Live. Webflow published the page, Stripe wired the checkout, and the first signup just came in.
Webflow
Waitlist page published · done
Stripe
Checkout wired to the button · done
SHIP IT BEFORE THE CALL ENDS
"I need a waitlist page for the pilot. Dark theme. Fifty dollars to reserve a seat." Webflow builds and publishes the page and Stripe wires checkout to the button. You're still on the call when the first signup comes in.
Every app your team already runs on.
Twenty-seven pre-built connectors, grouped by what they’re for, plus your own Tavus account and the Tavus docs. Each one is a normal sign-in. Free on every plan.
PRODUCTIVITY
Book it, post it, follow up.
The apps a conversation spills into: calendars, inboxes, support queues and the Zap that reaches everything else.
DESIGN
Describe it. Watch it appear.
Diagrams, pages and video assets, built from what you said out loud.
REVENUE
Know the account. Close the loop.
Prospects, segments, balances and payment links, read out loud or acted on mid-call.
KNOWLEDGE
Find the page. Write it back.
Docs, drives, meeting notes and research, so a PAL answers from what your team already wrote down.
ENGINEERING
File it before the call ends.
Issues, pull requests, tickets and your own documentation, with the detail from the conversation attached.
ANALYTICS
The numbers, out loud.
Ad spend, funnels and session replays, so you hear what matters instead of opening a dashboard.
What it looks like in a call
live call
“Close out yesterday’s pricing meeting.”
On it. I’ll read the notes back and get the follow-ups moving while we keep going.
David
Granola
Reading the pricing meeting · running
“File that export bug.”
Found the session. Filing it now with the replay attached. Keep going, I'll say when it's in.
Deborah
LogRocket
Session found · 504 on export · done
Linear
Filing 1 issue, replay attached · running
“Book Sam in for twenty minutes on Thursday.”
Done, 2:30 on Thursday. The invite's in the card on screen, and Sam has a copy.
Andrea
Google Calendar
Thu 2:30 to 2:50 with Sam · booked
Gmail
Invite sent to Sam · done
“Close out the pricing meeting.”
On it. The issues, the decision log and the follow-up are all moving. I'll call each one out as it lands.
Ray
Granola
Notes read · done
Linear
Filing 3 issues · running
Notion
Writing the decision log · running
Google Calendar
Booking the follow-up · running
Slack
Recap to #pricing · queued
“Send me the recap, I have to run.”
Go. I'll finish the write-up and it'll be in Notion in a couple of minutes.
Nina
Notion
Write-up posted · 2 min after the call
Slack
Recap sent to #design · done
The PAL keeps talking
When you ask for something, the PAL hands the job off and carries on with the conversation. It acknowledges the request, keeps talking, and speaks the outcome the moment the job lands, without waiting for you to ask.
A status line under its face
"Reading Granola notes," then "Filing 3 issues in Linear." A short line appears under the PAL's face so you can see what it's doing without being told. If you'd rather hear every step, or none of them, that's a setting.
A card with a link
When the job lands, the PAL says so and can show a card on Magic Canvas with a link to what it made: the issue, the draft, the booking, the page. The card clears itself once you've seen it.
Several jobs at once
Up to five jobs can run at the same time, so one ask can fan out across several apps while you carry on. Every job reports back, done or not, including one that times out, so you're never left waiting on something the PAL promised and dropped.
It keeps working after you hang up
Ask for the recap on your way out of a call and the PAL finishes the write-up after the window closes. Each connector uses the account that connected it, you can limit which of its tools a PAL may use, and you can disconnect it at any time.
Everything above is in the API, and your own MCP server works the same way
FOR API BUILDERS
Attach and scope
Attach connectors to a PAL with layers.mcp.connectors and the PAL discovers the server's tools itself; there is nothing to import. Use connector_tools to allow-list what each connector may do, so a support PAL can post to Slack while a sales PAL only reads it, on the same connection. Ten connectors per PAL, up to 200 tools each.
Follow every job
Three events keyed by task ID describe each job in your app: agent_start, agent_update and agent_stop, with the result in the stop event. Every start gets exactly one stop, including jobs that never ran. spoken_updates and visual_updates control what the PAL says and shows, from every step to only the outcome.
Bring your own MCP server
Pre-built connectors are the apps Tavus signs you into with one click. A custom MCP server is any server that speaks MCP over HTTPS, including one your team runs. Register it once with its URL and how it authenticates; for OAuth you get an authorize_url to send people to, and Test runtime connection checks the path a live call uses.
Connector questions, answered
Yes. Pre-built connectors are MCP servers Tavus hosts and signs you into with one click. If your team runs its own MCP server, point a PAL at it by URL and it works the same way.
No. The Gmail connector drafts only. The reply waits in your drafts, you read it over, and you send it yourself. Anywhere a PAL can act, you can limit which of a connector's tools it may use.
Yes. Attach connectors to a PAL with layers.mcp.connectors, scope them with connector_tools, and follow every job through the agent_start, agent_update and agent_stop events. The docs cover the setup, the events and the prompt that steers the background agent.
The PAL says so. Every job reports back, done or not, including one that times out, so you're never left waiting on something the PAL promised and dropped. A job still running when the call ends is cancelled.
Yes. Connectors are free on every plan. Open PAL Maker, go to Connectors, and connect the first app your PAL should use.
No. A PAL does the work that used to wait until after the conversation, and you make the final call. It drafts, you send. It files, you review. Each connector uses the account that connected it, and you can disconnect it at any time.
Connect once. Talk. It's done.
