Turn a new launch subpage into a next step
A new launch page can cue the conversation that helps you get coordination underway.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Execute Bot Action By User
Tool to execute a bot action for specific users. Use when you need to trigger actions for one or multiple bot users.
Why this helps
Launch planning often creates a page full of intentions but no prompt to begin the next conversation.
- Give new launch work an immediate communication step.
- Reduce time spent figuring out what to do after documenting a plan.
- Start coordination while the project context is fresh.
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 start your launch coordination action for a new subpage.
- 3Describe the desired Botbaba action in one plain-language instruction.
- 4Choose Page Added to Page and select the launch parent page and a report channel.
- 5Test by adding one real launch subpage.
Questions about this workflow
Does this watch all nested descendants?
The trigger is described for a new subpage under the specified parent page.
Can the action use the new page context?
Describe the launch coordination outcome in the prompt so Notis can interpret the page context.
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.