How-To Guide Intermediate 8 min read

Setting Up Notion Views and Resource Matching

Use the Notion views your team already trusts, then choose which Notion resources should connect to Local Business Pro availability calendars.

Use the Notion integration when your team plans work in Notion and wants Local Business Pro to turn the right records into operational contacts, jobs, appointments, and availability calendars.

The strongest setup uses Notion views as the source. Your Notion database may hold everything, but the view is usually where the real operating decision lives: confirmed jobs, the right region, the right truck, the right calendar, and no records the crew should ignore.

Before you start

Your Local Business Pro account is connected to the right business.
Your Notion integration has access to the databases and views you want to sync.
Your Notion views already filter out records that should not show up in LBP.
You know which Notion resources should match LBP availability calendars.

Remote resources can be Notion pages that represent calendars, trucks, routes, crews, equipment, or other scheduling resources. Match them on purpose. Local Business Pro should not create new availability calendars just because a Notion field exists.

Step 1: Open Notion preferences

In Local Business Pro, go to Connect / Integrations, find Notion, open the card menu, and choose Edit Preferences.

The drawer shows the Notion databases and views available to your integration.

Step 2: Choose the Notion view for each record type

For each record type you want to import, choose the Notion database view that should act as the source.

Common mappings:

Contacts: a customer or contacts database.
Jobs: the view that represents confirmed or active jobs.
Appointments: the view that represents scheduled work.
Calendars/resources: the database or view that represents trucks, routes, crews, or other scheduling resources.

Choose the view that already contains the right filters. For example, if tentative jobs should not appear in Local Business Pro, keep them out of the Notion view instead of relying on the sync to guess.

Step 3: Map the fields

Map each Local Business Pro field to the matching Notion property.

For scheduling, the most important fields are usually:

Appointment date
Appointment start time
Appointment title
Status
Location
Customer relation
Calendar or resource relation

If a Notion property is a relation, Local Business Pro can use it to connect records. For example, an appointment can link to a customer page or to a truck, route, crew, equipment, or calendar page.

Step 4: Match Notion resources to LBP calendars

After the database mappings are saved, use Match Notion Resources to decide what each remote resource should do.

For each Notion resource, choose one option:

Don't Sync: the Notion resource will not create or route appointments to an LBP calendar.
Existing LBP calendar: appointments related to that Notion resource will use the selected availability calendar.
Create a new calendar: Local Business Pro creates a new availability calendar for that Notion resource.

This step is intentional. Adding a Notion calendar or resource field does not automatically create calendars. Creation happens only when you choose Create a new calendar during resource matching.

Step 5: Save and run the initial sync

Click Save Mapping after the fields and resources are configured. That saves the setup, but it does not pull the records yet.

After saving, run Initial Data Sync from the Notion setup drawer. That sync imports records from the selected Notion views into Local Business Pro. Existing records can be updated when the next sync reads the same Notion pages again.

Local Business Pro reads from Notion for normal sync. It does not update your Notion pages during this setup flow.

Troubleshooting

If a Notion view is missing, confirm the Notion integration has access to the page, database, and view. Reopen the drawer after access changes so Local Business Pro can refresh the available sources.

If appointments appear on the wrong calendar, check the resource relation on the Notion appointment and the resource matching table in Local Business Pro. The related Notion resource must be matched to the intended LBP availability calendar.

If only some appointments appear, check the selected Notion view filters first. Local Business Pro imports what the selected view exposes. If the record is hidden by the view, LBP will treat it as out of scope.

If the sync completes with errors, open the integration drawer again and review which record type failed. Fix the source mapping or Notion access issue, then run sync again.