Connect Notion
Turn every booking, lead or order into a row in a Notion database, and keep that row up to date as things change.
Use this guide when Notion is where you keep track of customers or jobs. You connect a workspace once, point an assistant at a database, and from then on each submission becomes a row there. When its status changes, or the customer moves or cancels a booking, the same row is updated. Notion is on the Growth plan and above.
Open NotionWhat lands in Notion
One row per submission. A customer who finishes a conversation creates the row; anything that happens to that submission afterwards updates it in place, so the database shows where things stand now, not a log of events.
- New submission creates the row.
- Status changed, Booking rescheduled by customer, Booking cancelled by customer and Booking request expired update it.
- A column with nothing to write is left as it is, so an update never blanks what is already there.
One database per assistant
A database is matched to one assistant's questions, so each connection belongs to a single assistant. Two assistants mean two connections, which can point at two databases or, if the columns suit both, the same one.
Connect a workspace
Open Integrations → Notion
Choose Connect Notion. A Notion window opens and asks which workspace to use.
Pick the pages Meerlume may see
Notion asks you to select pages. Select the database you want rows in, or the page you want a new database built inside. Meerlume can only see what you tick here, and you can change it later from the connection's settings inside Notion.
Allow access
You land back on the Notion page in Meerlume with the workspace listed. You can connect more than one workspace.
Add a database
Choose Add a database, pick the assistant, then decide where rows go.
- A database I have — pick one of the databases you shared. Meerlume matches its columns to your questions by name, and you check the result before the first lead arrives.
- Build one for me — pick a page, and Meerlume creates a ready-made table inside it with a column for each question and the mapping already done.
If your database isn't in the list
It wasn't shared when you connected. In Notion, open the database, choose ··· → Connections, and add Meerlume. Then reopen the dialog.
Map the columns
Each column in the database can take one thing from the conversation, or be left empty. The choices are your assistant's questions, plus what Meerlume knows about every submission:
- Customer name, phone and username
- Status, channel, when it was received, a one-line summary, and the assistant's name
- A link back to the conversation in your inbox
- For bookings: appointment start and end, service, staff member and booking status
Title, text, number, select, multi-select, date, checkbox, URL, email and phone columns can all be filled. Appointment times are written in your business time zone, so 14:00 in your calendar is 14:00 in Notion.
Notion's Status columns can't be filled
Notion doesn't let an integration add options to a Status column, so a status it hasn't seen would fail every time. Use a Select column for the submission status instead: it does the same job, and new options appear on their own.
Renaming columns is safe
The mapping follows the column itself, not its name, so tidying your headers in Notion breaks nothing. Deleting a mapped column does: Notion refuses the row, the delivery log on the database's page shows why, and the fix is to map that source to another column.
Test it
Open the database's page in Meerlume and choose Add a test row. Notion has no dry run, so this writes a real row titled “Test from Meerlume” through your mapping. Check it looks right, then delete it in Notion.
When rows stop arriving
- You removed Meerlume's access in Notion. Every database on that workspace is paused and you get one notice. Choose Reconnect on the workspace; the paused databases come back on their own.
- The database was deleted or unshared. Only that connection is paused. Share it again, or point the assistant at another database.
- A row was deleted in Notion. The next change to that submission creates it again.
- Notion is slow or down. Meerlume retries on the same schedule as webhooks, and the delivery log on the database's page shows each attempt.
Rows keep arriving if you go over your monthly conversation limit. Only connecting a new workspace or adding a database waits until the limit lifts.
Related guides
Continue with the next part of the setup once this step is stable.
Connect Slack
Put a card in a Slack channel every time a customer finishes a conversation — the answers, the contact, the booking, and a button into your inbox.
Send webhooks to your own tools
Get a signed JSON request at your server, CRM or automation tool the moment a submission arrives, changes status, or a booking is cancelled, rescheduled or expires.
Triage submissions in the inbox
Read what customers sent, change status, reply or take over the chat, approve or reschedule bookings, and archive — keep follow-up moving without getting buried.