How to Set Up a Notion CRM That Captures Website Bookings as Leads
26 Aug 2026 · by Hattie Smithson
If you use Notion as a lightweight CRM, the danger is not usually the database itself. It is the gap between someone booking a call on your website and that prospect becoming a visible contact and opportunity your team can follow up.
Notion can work perfectly well as a simple CRM, especially when you are still close enough to the sales process to know most of the people in the pipeline.
The problem usually starts one step earlier.
Someone lands on your website, books a discovery call, and gives you the important details during the booking flow. The meeting appears in the calendar, which is useful, but the sales record still has to be created somewhere else. If nobody adds the contact and opportunity to Notion, the lead only exists as a calendar invite, an email notification, or a memory.
That is a weak place to keep a potential customer.
A better setup is simple: build a Notion CRM with a contacts database and a deals database, connect the two with a relation, then use calendr.so to send website bookings into that structure. The calendar handles the meeting. Notion holds the follow-up. The booking form becomes the bridge between them.
Start with the minimum CRM structure
Do not start by trying to build a perfect CRM in Notion. That is how people end up with 40 properties, three dashboard views, and a system nobody wants to update.
For this kind of workflow, you need two databases:
- Contacts: the people who enquire, book, buy, or may buy from you.
- Deals or opportunities: the possible pieces of business connected to those people.
Keeping those separate matters. A person can book more than one call, enquire about more than one service, or come back later with a different need. If you treat the person and the opportunity as the same record, the CRM gets messy as soon as the relationship becomes slightly more interesting.
A contact is who the person is. A deal is what might happen next.
Create your Contacts database in Notion
Your Contacts database should give you enough information to recognise the person and follow up intelligently. It does not need to become a full biography.
A simple version could include:
- Name: the main title field.
- Email: so contacts can be matched when the same person books again.
- Phone: useful if your sales or service process sometimes moves to a call.
- Organisation: the company, firm, or business they are connected to.
- Source: website, LinkedIn, referral, ad campaign, partner, or another channel.
- Status: prospect, active opportunity, customer, partner, not a fit, or whatever fits your business.
- Notes: a light field for context that does not deserve its own column yet.
If you are early-stage, this is enough. You can always add properties later once you know what your team actually uses.
Create your Deals or Opportunities database
The Deals database is where the sales process becomes visible. This is the board you can look at on Monday morning and understand what needs attention.
A useful first version could include:
- Deal name: something readable, such as the person's name plus the meeting or service interest.
- Contact: a relation property pointing back to your Contacts database.
- Stage: new lead, discovery booked, qualified, proposal sent, won, lost, or nurture.
- Owner: the person responsible for follow-up.
- Meeting date: when the booking or qualifying form submission happened.
- Service interest: what they want help with.
- Next step: the specific action someone needs to take after the meeting.
This is where a lot of lightweight CRMs go wrong. They track the lead, but they do not make the next action obvious. A deal without a next step is just a record of something that happened. A deal with an owner, stage, date, and next step is something your team can work.
Connect Contacts and Deals with a relation
In Notion, add a relation property on your Deals database that points to your Contacts database. You might call it Contact, Contact Name, Prospect, or Client. The exact name is less important than the structure.
This relation is the link that lets one person have one or more opportunities attached to them. It also gives calendr.so the place to connect the records when a prospect books through your website.
Before connecting any tool, create one test contact and one test deal manually. Link them together. Open both records and check that the relationship makes sense. This small test often catches naming problems, missing properties, and over-complicated CRM ideas before you automate them.
Decide which website bookings should become deals
Not every booking page needs to create a sales opportunity.
A support call, customer check-in, hiring interview, or internal planning meeting may not belong in your sales CRM. A discovery call, consultation, demo request, quote call, or high-intent enquiry probably does.
Start with one website booking page where the intent is clear. For example:
- Book a discovery call.
- Book a consultation.
- Book a product demo.
- Talk to us about a project.
This keeps the first version controlled. You can prove the workflow works before applying it to every meeting type in the business.
Add the booking page to your website
The booking page is where the prospect takes action while their interest is highest. You can use a button that links to the Calendr booking page, or you can use embeddable booking pages if you want the booking flow to sit directly on your website.
The page around the booking flow should explain one thing clearly: what the person is booking and why it is worth their time. Do not ask the website visitor to choose from five vague meeting types if they are already on a discovery-call page. Give them the next step that matches the page they are on.
If the booking page is for sales, keep the meeting name clear. "Discovery call", "Sales consultation", or "Product demo" is easier to manage later than "Chat". The event type name can become useful context in both the calendar and the Notion record.
Use booking forms to collect the lead details
A booking form should collect the information that changes how you prepare, qualify, or follow up. It should not become a full CRM data-entry exercise for the prospect.
For a simple website lead flow, useful questions might include:
- Name.
- Email.
- Phone, if you genuinely use it.
- Organisation or company name.
- What they want help with.
- Company size, team size, or expected number of seats.
- How soon they are looking to make a decision.
With booking forms in calendr.so, this context is collected as part of the booking flow. That means the person is not just choosing a time. They are also giving the host enough information to make the first conversation useful.
If you need to route people before they book, qualifying forms can sit earlier in the journey. For example, a small company might be sent to a starter resource, while a larger opportunity is sent to a discovery page for the right team. The same Notion integration can work with qualifying form submissions, so early-stage prospects can enter the pipeline before they select a meeting time.
Connect Notion to calendr.so
Once your Notion structure exists, connect it to calendr.so from the integration settings. A firm admin can authorise the Notion workspace, then refresh the database list after the Contacts and Deals databases have been shared with the Calendr connection inside Notion.
That sharing step matters. If Calendr cannot see the database in Notion, it cannot offer it as a target for your booking page or qualifying form.
After the databases are visible, configure the relevant event type or qualifying form. Choose:
- The Notion contacts database.
- The Notion deals or opportunities database.
- The relation property that links the deal to the contact.
When someone confirms a booking, calendr.so can look for an existing Notion contact using their email address. If the contact already exists, the new deal can be linked to that person. If not, calendr.so can create a new contact, create a deal or opportunity row, and connect the two through your chosen relation property.
Standard Notion property types such as title, email, phone, date, select, and rich text fields can be detected from the shared database schema. That gives you enough structure to capture the core details without rebuilding your Notion workspace around the booking tool.
Test the full flow before publishing it widely
Do one test booking as if you were a prospect. Use a real-looking name, email, company, and service interest. Then check three places:
- The calendar invite: confirm the meeting appears with the right host, time, and meeting details.
- The Notion contact: confirm the person was matched or created correctly.
- The Notion deal: confirm the opportunity was created, linked to the contact, and placed in the right starting stage.
This is also a good moment to check the human workflow. Who reviews new deals? What stage should new website bookings start in? What happens after the call? Who closes out dead opportunities? The integration can create the records, but the team still needs a habit for working them.
A simple workflow you can launch this week
If you want the smallest useful version, build this:
- Create a Contacts database in Notion with name, email, phone, organisation, source, and status.
- Create a Deals database with deal name, contact relation, stage, owner, meeting date, service interest, and next step.
- Add a relation from Deals to Contacts.
- Create one Calendr discovery-call event type for your website.
- Add a short booking form that collects company and enquiry context.
- Share both Notion databases with Calendr, connect Notion, refresh databases, and map the event type.
- Run a test booking and check the linked contact and deal in Notion.
Once that works, you can improve the flow. You might add a sales scheduling page for team-based demo routing, use round robin if several people can handle the same call, or add a qualifying form before the booking page if not every website visitor should reach the same calendar.
Where this setup helps most
This is especially useful when you are not ready for a heavy CRM, but you are past the stage where leads can live in your inbox.
A founder can see which website enquiries have become booked calls. A sales lead can review new opportunities in one Notion board. A small team can stop asking whether someone remembered to create the CRM record after the meeting was booked.
That is the real win. The meeting is not treated as an isolated calendar event. It becomes the start of a visible sales process, with the contact, opportunity, meeting context, and next action in one place.
The goal is not to make Notion pretend to be an enterprise CRM. The goal is to make sure every serious website booking creates a record your team can actually follow up.
Start with one lead flow
Turn website bookings into Notion CRM records
Use calendr.so to collect booking form details, create or match Notion contacts, and add linked deals to the pipeline your team already uses.
Start a free trialMore resources for Growing Sales Teams with Processes
How to Use LinkedIn Sales Navigator to Generate Leads Without Making Outreach Weird
LinkedIn Sales Navigator is useful when it helps you find the right people, spot a relevant reason to start a conversation, and avoid sending strange copy-and-paste outreach. This guide shows small sales teams how to build focused lists, use signals with restraint, and turn good conversations into booked calls.
Sales Operations for Small Teams: What to Standardise Before You Hire More Reps
If your sales process only works because the founder remembers every lead, adding more reps will multiply the mess. This guide explains the sales operations basics to standardise first, from lead ownership and meeting types to routing, handoffs, booking links, and reporting.
How to Build a Sales Playbook That Actually Gets Meetings Booked
A useful sales playbook does more than define scripts, stages, and CRM fields. It tells the team exactly how to turn interest into the right booked meeting, with the right person, before momentum disappears.
Why Calendr
Google Calendar Appointment Schedule vs a Proper Booking Tool
Google Calendar Appointment Schedule is a useful option when one person needs a simple booking page. It starts to feel limited when a growing team needs consistent meeting types, multi-person availability, lead routing, controlled booking links, and reporting that goes beyond checking individual calendars.
How Event Types Make Interview Scheduling Easier for Hiring Teams
Interview scheduling gets messy when every stage is treated like the same calendar link. This video shows how different event types can help hiring teams manage screening calls, hiring manager interviews, final interviews, required hosts, fallback options, and ad hoc meetings without rebuilding the process in email every time.
Appointment Scheduling Software for Client-Facing Teams: A Calendr.so Overview
If your team books sales calls, onboarding sessions, support reviews, legal appointments, or client consultations, a basic booking link can start to create more admin than it removes. This video walkthrough shows how calendr.so helps client-facing teams control meeting types, find the right colleague's link, coordinate multi-person meetings, and report on booking activity without turning scheduling into another spreadsheet.
Built for teams that need more than a booking link
calendr helps customer-facing teams move faster with team-first scheduling, multi-host bookings, and smarter availability controls.
Google
Microsoft 365
No credit card required