Integrations
The interview asks like someone who was there.
“What did you work on today?” is a question for strangers. Connect where your day actually happens and the director reads it before writing tonight’s questions: the commit that took all afternoon, the call that overran, the payment that landed at four.
Three rules hold for every connection on this page.
- 1. It feeds the questions, never the footage. What goes in an episode is only ever you, on camera, saying it yourself.
- 2. You see everything it gathered before you film, and tick what tonight is allowed to know.
- 3. Everything is read-only, keys are stored encrypted, and disconnecting deletes them.
What shipped
The work itself, seen where it happened, so the interview asks why it mattered rather than what it was.
GitHub
OAuth, read-only.
Commits since your last episode. It can see what went out from any machine, and it can never write to your repositories.
A local repository
Your browser reads the folder, with your permission. No account, no key, nothing leaves your machine.
The cheapest connection there is, and the first one worth making: commit messages are the skeleton of a build day.
Linear
Personal API key, read-only.
Issues you closed today: the half of the work that never becomes a commit.
Vercel
Access token, read-only.
Production deploys. The day something went live is usually the day worth talking about.
Your meetings
Who you met and what was said, from tools you already run. This is the one group that touches other people, so its rule is absolute: transcripts are context for your questions and never become footage. Nobody else's voice ends up in an episode.
Google Calendar
OAuth, read-only, titles and times only.
“What came out of the pricing call?” is the question you would never think to prompt yourself with. It never reads what was said in a meeting.
Zoom
OAuth, read-only, your own cloud recordings.
Transcripts of calls you recorded, so the interview knows what the afternoon actually held.
Fathom
API key made in your Fathom settings.
Transcripts of meetings your notetaker sat in. Paste a key, done: no approval queue on either side.
Fireflies
API key made in your Fireflies settings.
Same as Fathom, for the other notetaker. If both saw the same call, you'll only see it once.
A transcripts folder
Your browser reads the folder, with your permission.
The fallback for recorders that sync to disk, including Meet transcripts saved locally.
Your numbers
The pulse of the business, because the day the first payment lands is the episode this whole product exists to catch, and you would be too busy celebrating to write it down.
Stripe
A restricted, read-only key you make yourself.
Payments since your last episode. “Who was the first to pay you?” beats anything a day note would have said.
Plausible
API key plus your site domain.
Today's visitors and pageviews, one line. The day traffic moves, the interview can ask what moved it.
PostHog
Personal API key plus your project.
Usage since your last episode. The day something spikes, tonight can be about why.
And the ones only you can supply
No integration can see how the day felt. Voice notes on a walk, fifteen-second moments to camera, screenshots of the thing itself, and pages you point it at: the founder’s half of the homework, and the half that matters most.