Pages and database rows created in Notion from contacts, deals and intake answers.
Somebody opens the client's Notion page before a call and reads a history that stops in March. The two things that actually matter happened last week and are in an inbox, so the call starts with an apology.
The page is the record. Your team keeps the client’s history in a Notion page — what was agreed, what changed, what the last call was about — and they keep it because reading it is how anybody picks the account up. Then something happens outside Notion. A form comes in, a payment lands, a meeting is booked. It is on the page only if a person opens the page and types it there, and on a busy week they do not, so the wiki quietly becomes a version of the account from three weeks ago.
Connect Notion and the paragraph is added to the page itself, under what is already written. The record people read stays the record of what happened.
Reach for this when your team's real answer to a question is a page, not a dashboard. The wiki is where new people are told to start. Updating it by hand is the step that gets skipped when the week is full.
Need more than it doesTell us what the connection has to do and we will wire the rest of it.
The update is added to the page itself, below what is there. Not filed somewhere else for a person to copy across later.
Something that needs an answer is left as a comment on the page. It reaches the team the way anything else on that page would.
An existing record is found before a new one is made. The account stays a single page that grew, instead of four with the same name.
One job going through, start to finish, with nobody watching it. The steps are what this connection actually does; the times beside them are illustrative.
You will find it under Settings → Integrations → Notion.
Open the setup guide →
Pages: making one, finding one, and adding content to the end of it. Database rows: creating, updating, archiving and restoring them, and finding one before deciding. Comments on a page. That is the scope.
New text at the bottom of the page, under everything already on it. The call, the payment, the form answer, in the words you chose. Whoever opens it next reads the whole history in one place, in order.
Yes. A row is created for a new client, and updated as things change about them. Rows can be archived when the work ends and brought back if it restarts. The table stays a fair picture of who you are working with.
The existing record is looked for first, and used when it is there. One client stays one row and one page. You avoid the week somebody spends merging three versions of the same account into one.
It writes the way a colleague does, at the bottom of the page. Nobody is asked to change how they take notes or where they keep them. The difference is that the page they trust is now current without anyone maintaining it.
An hour, watching a lead arrive and a job get scheduled. Then you tell us where it would not fit your work.