Bring a customer's order history into view
Start a customer page and let Notis fetch the associated Baselinker orders for a faster, more informed reply.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Get Orders by Email
Tool to search for orders by e-mail address. use when you need to retrieve all orders linked to a specific customer email in baselinker.
Why this helps
Switching between customer notes and order records slows replies and risks overlooking prior purchases.
- Makes prior orders easier to find during customer work.
- Reduces repeat searches across tools.
- Provides useful context in the run report.
Setup
Build it in a few focused steps.
- 1Connect Notion and Baselinker to Notis once in the portal.
- 2Create an automation in the portal or by asking Notis in plain language.
- 3In a single prompt, ask Notis to search Baselinker by the email on each new customer page and summarize matching orders in the report channel.
- 4Select Page Created for the customer-page parent, choose a report channel, and test using a real customer record.
Questions about this workflow
What information does the lookup use?
The prompt should tell Notis to use the customer's email from the new Notion page to search Baselinker.
Will it create or change customer records?
No. The available Baselinker action searches for orders by email.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Baselinker. A trigger fires from one place; an action lands in another.
Notion triggers
Baselinker actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get External Storages List
Tool to retrieve a list of available external storages connected to baselinker. use after authenticating to discover connected shops or warehouses.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Inventory Documents
Tool to retrieve a list of inventory documents. use when you need to fetch inventory records with optional filters for id, type, status, date range, warehouse, or pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Inventory Document Series
Tool to retrieve available inventory document series. use when you need to assign a numbering series to a new inventory document.
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.
Get Inventory Purchase Orders
Tool to retrieve a list of purchase orders from baselinker storage. use when you need to fetch purchase orders with optional filters like date range, supplier or pagination.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Inventory Purchase Order Series
Tool to retrieve a list of purchase order document series. use when you need to select a numbering series for a new purchase order.
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.
Get New Receipts
Tool to retrieve receipts waiting to be issued. use after confirming fiscal printer availability; fetch pending receipts and mark them with setorderreceipt.
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 Order Extra Fields
Tool to retrieve extra fields defined for orders. use before fetching orders with include custom extra fields to list available custom order fields.
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 Orders
Tool to download orders from baselinker order manager. use when you need to fetch orders filtered by date, status, or other criteria.
Connect any two apps with Notis in the middle.
Notion and Baselinker, 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 Baselinker.