Connect Notion to Landbot
When something happens in Notion, Notis takes the next step in Landbot. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Landbot
Check Landbot bot inventory when a Notion page is added
Use a new Notion page as a cue to review the current Landbot bot inventory and report the available bots, helping keep launches and planning aligned with what is actually configured.
Review Landbot agents after a Notion property change
When a Notion page property changes, have Notis retrieve the Landbot agent roster and report it, giving operations a quick reference while a workflow or ownership record is being updated.
Review WhatsApp templates after a Notion content edit
When Notion page content changes, have Notis retrieve the available Landbot WhatsApp templates and report them for review, helping keep message planning grounded in the templates the account actually has.
Check Landbot customer records after a Notion comment
A new Notion comment can prompt a Landbot customer list lookup, making customer records available for a follow-up review without leaving the team's discussion context.
Retrieve Landbot channels when a Notion database row is added
When a page is added to a Notion database, have Notis list Landbot channels and report their details as a quick operational reference for the newly tracked work.
Check the Landbot bot catalog when a Notion subpage is added
A new subpage under a selected Notion page can prompt Notis to list Landbot bots, giving project documentation a current bot inventory to review.
List Landbot channels when a Notion view is created
When someone creates a Notion view, prompt Notis to retrieve Landbot channels and report them, offering a timely setup reference as the team's way of organizing work changes.
Review Landbot bots after a Notion schema change
A Notion data source schema update can cue a bot inventory review, helping founders check the Landbot setup when a tracked workflow or intake structure changes.
Check WhatsApp template availability when a Notion database is created
When a Notion database container is created, have Notis retrieve the Landbot WhatsApp template list so a new intake or operations database can be planned with current messaging options in view.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Landbot
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.