Notion

Connect Notion to create an organized database page for every confirmed Dlopo booking. Dlopo keeps the same page up to date when the booking is rescheduled or cancelled, while leaving the booking flow available if Notion cannot be reached.

Before You Begin

You need:

• A Notion workspace.
• Permission to add a connection to the pages you want Dlopo to access.
• A Notion database with a title property.
• A signed-in Dlopo account.

Notion only makes pages and databases you explicitly select during authorization available to Dlopo. Choose the smallest set of pages needed for your booking workflow.

The Notion integration is included on all Dlopo plans.

Connect Notion

1. In Dlopo, open Settings and select Integrations.
2. Find Notion and select Connect.
3. In Notion, choose the workspace and the pages or databases that Dlopo may access.
4. Approve the connection. Notion returns you to the Notion integration in Dlopo.
5. Under Database, choose where new booking pages should be created.
6. Select Save Changes.

The database must contain a title property. If it also has a select or status property containing the options Confirmed, Rescheduled, and Cancelled, Dlopo keeps that property synchronized automatically. Otherwise, the booking state is still recorded inside the page.

If the database you want does not appear, reconnect Notion and grant Dlopo access to it.

What Dlopo Sends to Notion

A new confirmed booking creates one Notion page containing:

• Booking and booking-link title
• Guest name and email address
• Host details
• Start and end time
• Meeting location or join URL
• A link back to the Dlopo booking
• Booking notes
• Answers to custom booking questions

Dlopo stores the relationship between the booking and its Notion page. This allows later changes to update the existing record instead of creating a new page.

Guests do not interact with Notion and do not need a Notion account. Their booking experience and confirmation remain unchanged.

Reschedules and Cancellations

When a booking is rescheduled, Dlopo updates the existing Notion page and adds a reschedule callout with the time of the change.

When a booking is cancelled, Dlopo updates the same page and adds a cancellation callout. Dlopo does not delete the page, so notes and historical context remain available.

If Dlopo cannot locate a previously synchronized page, it creates a new page where possible instead of blocking the booking change.

Review Sync Activity

Open Settings → Integrations → Notion, then select View Logs to review the latest synchronization attempts.

Each entry shows:

• The booking lifecycle event
• The destination database
• Delivery status
• Attempt count
• The error returned for a failed attempt
• A link to the Notion page after a successful sync

For a failed attempt, correct the connection or database access first, then select Retry. Dlopo retries temporary Notion and network failures automatically before recording a failure.

A Notion outage or failed write does not prevent a guest from completing, rescheduling, or cancelling a booking.

Reconnect or Change the Database

Select Edit on the connected Notion integration to run authorization again. Use this when:

• You need to grant access to another database.
• The connected workspace changed.
• Notion authorization was revoked.
• Dlopo reports that the selected database is unavailable.

After reconnecting, choose the destination under Database and select Save Changes.

Changing the destination affects new synchronization attempts. Existing pages remain in their original Notion database.

Disconnect Notion

1. Open Settings → Integrations → Notion.
2. Select Disconnect.
3. Confirm the disconnection.

Disconnecting removes usable Notion credentials and the selected destination from Dlopo. New bookings stop synchronizing immediately. Existing Notion pages and their content are not deleted.

Reconnect Notion at any time and choose a database to resume synchronization.

Resolve Common Problems

No databases appear

Reconnect Notion and explicitly select the page containing the database. A database that has not been shared with the Dlopo connection is not visible through the Notion API.

The selected database is unavailable

The database may have been deleted, moved, or unshared. Restore its access or select another shared database.

Notion needs attention

Open the integration and read the latest error under View Logs. Revoked authorization requires reconnection. A missing database requires updated page access or a different destination.

A status property does not change

The property must be a Notion select or status property containing Confirmed, Rescheduled, and Cancelled. The page still receives lifecycle callouts when no compatible status property is available.

A sync failed during a Notion outage or rate limit

Dlopo retries temporary failures automatically. If the final attempt fails, wait until Notion is available, open View Logs, and select Retry.