Review the related Botbaba flow when a process changes
A process update can cue a closer look at the Botbaba flow supporting that work.
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
Get Flow
Tool to retrieve details of a specific flow. Use when you need the full configuration for a given flow ID.
Why this helps
Process changes are easy to document without checking whether the related conversation flow still fits.
- Connect process maintenance with flow review.
- Reduce the chance of relying on outdated conversation setup.
- Keep operational changes easier to follow through.
Setup
Build it in a few focused steps.
- 1Connect Notion and Botbaba to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to retrieve the relevant Botbaba flow after a process update.
- 3Describe how the flow should be identified and reviewed in one plain-language instruction.
- 4Choose Page Properties Updated for the process data source and select a report channel.
- 5Test with one real process update linked to an existing flow.
Questions about this workflow
What does Get Flow return?
It retrieves details and configuration for a specific flow.
Does this update the flow?
No. It retrieves the flow for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Botbaba. A trigger fires from one place; an action lands in another.
Notion triggers
Botbaba actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Shopify Cart Creation Simulator
Tool to simulate a Shopify cart creation webhook payload. Use when generating test payloads for BOTBABA_CART_CREATION_SHOPIFY_WEBHOOK.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cart Creation Shopify Webhook
Tool to receive Shopify Cart Creation webhooks. Use when configuring Shopify webhook for Cart Creation events and forwarding the payload to Botbaba. Must be called upon receiving Shopify payload.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Cart Update Shopify Webhook
Tool to forward Shopify cart update events to BotBaba. Use when processing Shopify Cart Update webhook after configuring the webhook in your store.
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.
Shopify Checkout Creation Webhook Receiver
Tool to receive Shopify checkout creation webhook events. Use when configuring your Shopify store to notify BotBaba of checkout creation events.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Checkout Update Shopify Webhook
Tool to forward Shopify checkout/update events to Botbaba. Use when handling Shopify checkout update notifications.
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 a broadcast campaign
Tool to delete a broadcast campaign. Use when you need to permanently remove a Botbaba broadcast by its ID after confirming it exists.
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.
Delete Contact
Tool to delete a contact. Use when you have the contact ID and want to remove it from Botbaba.
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.
Delete a conversation flow
Tool to delete a conversation flow. Use when you need to permanently remove a Botbaba flow by its ID after confirming it exists.
Connect any two apps with Notis in the middle.
Notion and Botbaba, 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 Botbaba.