Keep agent availability in view as Notion records change
A property update can prompt Notis to list Landbot agents, so the current roster is easy to review during operational changes.
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
List Agents
Tool to retrieve a list of agents in your landbot account. use after authenticating your account to enumerate all agents and their details.
Why this helps
A changed ownership or status record can prompt a separate search for who is available in Landbot.
- Surface the Landbot agent roster when a Notion record changes.
- Keep a useful operational lookup alongside the change.
- Avoid a separate manual trip into Landbot.
Setup
Build it in a few focused steps.
- 1Connect Notion and Landbot to Notis once in the portal.
- 2Create an automation and describe the roster lookup in one plain-language instruction.
- 3Select Page Properties Updated as the trigger; optionally scope it to a relevant data source in the trigger setup.
- 4Choose where Notis should report automation runs.
- 5Test with one real property update and check the roster report.
Questions about this workflow
Can I limit this to a particular Notion database?
The trigger supports an optional data source scope. Notis then runs the instruction when a page property in that source changes.
Does this assign an agent?
No. The Landbot action retrieves and reports the agent list; it does not assign agents.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Landbot. A trigger fires from one place; an action lands in another.
Notion triggers
Landbot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Bot
Tool to delete a specific bot from your account. use when you need to remove an unused or test bot after confirming the bot id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Customer By Phone
Tool to retrieve customer details by phone number. use when you need to fetch a customer's profile by their phone. example: "find customer with phone +1234567890".
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Agents
Tool to retrieve a list of agents in your landbot account. use after authenticating your account to enumerate all agents and their details.
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.
List Bots
Tool to list all bots in your landbot account. use after authenticating to discover your configured bots.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Channels
Tool to list all channels integrated with your account. use after authenticating your account to enumerate available messaging channels and metadata.
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.
List Customers
Tool to list customers who have interacted with your bot. use when you need to retrieve customer records with optional filters (channel id, opt in, search) and pagination.
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.
List WhatsApp Templates
Tool to list all whatsapp message templates available for the account. use after obtaining your whatsapp channel id to fetch template ids and parameter counts.
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.
Connect any two apps with Notis in the middle.
Notion and Landbot, 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 Landbot.