Archive Booqable customers from Notion offboarding
When a client offboarding decision is complete, have Notis archive the identified Booqable profile so your active customer list stays easier to manage.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Delete Customer
Tool to delete (archive) a customer by id. use after confirming the customer should be hidden from searches.
Why this helps
Offboarding leaves a loose end when an inactive profile remains in active searches after the decision is final.
- Connect profile cleanup to a completed offboarding decision.
- Reduce active-list clutter from customers who should be hidden.
- Keep the relevant customer ID with the offboarding record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Booqable to Notis once through the portal.
- 2Create an automation in Automations or tell Notis what outcome you need.
- 3In one instruction, ask Notis to archive the customer ID on a Notion record only when offboarding is complete and the archive decision is explicit.
- 4Select Notion's Page Properties Updated trigger and choose a run-report channel.
- 5Test with one approved offboarding record and verify the customer ID.
Questions about this workflow
Does this remove all customer data permanently?
The listed action archives the customer so it is hidden from searches. It is intended for a confirmed decision to hide that profile.
How can I avoid archiving the wrong profile?
Keep the correct Booqable customer ID on the Notion record and state the required offboarding approval clearly in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Booqable. A trigger fires from one place; an action lands in another.
Notion triggers
Booqable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Customer
Tool to create a new customer. use when onboarding a new client and you have verified their details. example: create 'jane doe' with email jane@doe.com.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Order
Tool to create a new order. use after collecting valid customer id and timing details. example: create an order for customer '297f2584-...' starting at '2018-01-01t09:00:00z'.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Product Group
Tool to create a new product group in booqable. use when you have defined the group's name and pricing details and want to organize items under a shared group.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Delete Customer
Tool to delete (archive) a customer by id. use after confirming the customer should be hidden from searches.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Order
Tool to delete (archive) an order by id. use when you need to hide completed or canceled orders from active listings.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Delete Product Group
Tool to delete a product group by id. use when you need to permanently remove a product group from your catalog after confirming its identifier.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Get Customer
Tool to fetch a specific customer by id. use after obtaining a customer identifier to retrieve full customer details.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Get Customers
Tool to retrieve a list of customers. use when you need to paginate through customers.
Connect any two apps with Notis in the middle.
Notion and Booqable, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Booqable.