The week you actually had, not the one you remember
By Friday afternoon most of the week has gone. You know it was busy. You could not reliably list what happened in it, and the interesting parts are exactly the ones that felt routine at the time.
Connecting Google gives the Friday review something to work from: the threads you actually replied to, and the meetings that actually happened. Read-only, and it never writes anything back.
Connecting it
- 1In Inklined, open Settings and connect Google. You approve it on Google’s own screen and come back.
- 2Two permissions are asked for, both read-only: your Gmail, and events on your primary calendar. Nothing can be sent, changed or deleted with either.
- 3The connection is yours rather than your organisation’s. Where an account has several people on it, each connects their own and nobody sees anyone else’s.
What Inklined takes
- →Threads you took part in. A message that arrived and sat there is never selected, because a thread you did not reply to says nothing about your week.
- →Meetings that actually took place. Solo holds, declined invitations, all-day markers and cancelled events all drop out.
- →Claims rather than content. What gets stored is the distilled fact, not the message. There is a test in the codebase whose entire job is to fail if a message body is ever written at rest.
What happens to it
The first thing that happens to a transcript is that the names come out of it. People become role descriptors, so a participant is stored as “Host [GTM Consultant]” rather than by name. Companies become sector descriptors, so a client called Acme Corp is stored as “a B2B SaaS startup”. Email addresses, phone numbers, office addresses and profile links are removed. This runs once, on the way in, before anything else touches the text.
What is left is split into passages and indexed, so that when Inklined asks you something tomorrow it can show you the 40 seconds of the call the question came from rather than asserting that you said it.
Then a second rule applies, and it is the one that matters most if your calls are client work. Only speech attributed to you can become something you publish. On a typical consulting corpus most of the words belong to the other person, and offering those back to you as “something you said” is how somebody ends up publishing a client’s thinking under their own name. Anything that still names an organisation after all that asks you to confirm before it will draft from it.
One limitation worth stating rather than hiding: a client name that opens a sentence is not always caught, because “Sona ran this play” is shaped exactly like “Pricing pages need an owner”. The title check is the reliable one, and the confirmation step exists because no automatic check is enough on its own.
More on this: how Inklined works.
When it does not work
A connection that authenticates and then returns nothing looks exactly like a healthy one, which is why Google Workspace going quiet is hard to diagnose from the outside.
- It says connected but the Friday review is thin
- Usually a genuinely quiet week rather than a fault. Only threads you replied to and meetings that really happened are selected, so a week of being copied into things produces very little on purpose.
- One source is missing from the review but it still arrived
- Deliberate. Email and calendar are guarded separately, so a revoked permission or a Google outage on one records a marker and the review is built from whatever else is available. It never blocks the Friday send.
- Google asked you to approve it again
- Access is refreshed quietly in the background, but revoking it in your Google account, or changing your password in some cases, ends that. Reconnecting takes one click and nothing already distilled is affected.
Questions
Sync runs every 4 hours. Setup steps checked against the product on 24 September 2026. Using something else? See what Inklined connects to.
The calls are already happening.
Start with the strategy session. No card needed for that part.