Retrieve Bubble context when an external signal arrives
Let a custom tool's incoming request cue a Bubble lookup, so the next decision can use current record details.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Trigger Bubble Workflow via GET
Trigger a Bubble API workflow using an HTTP GET request. API workflows are server-side workflows in Bubble that can be triggered externally. Use GET for simple workflows that don't require a request body (parameters passed as query strings). For workflows requiring complex data or file uploads, use the POST version instead. Before using: The workflow must be created in Bubble's workflow editor and marked as "Expose as a public API workflow". The Bubble app must have API access enabled in its subscription.
Why this helps
External signals can require context that lives in Bubble, adding a manual search before the work can continue.
- Connect custom signals to current app context.
- Reduce manual searching before a follow-up.
- Support workflows that need a fresh record check.
Setup
Build it in a few focused steps.
- 1Connect Bubble to Notis once and prepare the incoming webhook source.
- 2Create an automation in the portal or tell Notis what to do when the request arrives.
- 3Write one instruction explaining how the request identifies a Bubble record and why its details are needed.
- 4Choose an incoming Notis webhook trigger, configure the Bubble API workflow for GET, and select a channel for run reports.
- 5Test with one real request and confirm the expected record details are retrieved.
Questions about this workflow
What does the Bubble workflow need?
The API workflow must be exposed as a public API workflow, and the app must have API access enabled.
When should I use GET?
Use GET for simple workflow calls where parameters can be passed in the query string. Complex request bodies need POST.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bubble. A trigger fires from one place; an action lands in another.
Notion triggers
Bubble actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Create Things
Tool to bulk create multiple Things in Bubble via newline-separated JSON. Use when you need to insert many records at once. Must have Create via API permission.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Thing
Tool to create a new Thing. Use when providing a complete JSON payload to add a new record.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Thing By ID
Tool to delete a Bubble Thing by its unique ID. Use when you need to remove a specific record via the Bubble Data API.
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 Thing By ID
Retrieves a single Thing (record) from a Bubble Data Type by its unique ID. This is a read-only operation that fetches complete details of a specific record. The response includes all custom fields defined in the Data Type, plus standard Bubble fields (_id, created_by, created_date, modified_date). Use when you need to: - Fetch details of a specific record you know the ID of - Verify a record exists - Get the latest field values for a Thing Note: Requires the Data API to be enabled in your Bubble app settings and the specific Data Type to be exposed via the API.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Patch Thing By ID
Tool to modify selected fields on a Thing by its unique ID. Use after confirming the Thing exists.
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.
Replace Thing by ID
Tool to replace all editable fields on a Thing by its Unique ID. Use when you need a full overwrite of a Thing's fields and reset omitted fields to default.
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.
Download File
Tool to download a file given its URL. Use when you need to retrieve file content and obtain an s3key for subsequent upload tests.
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.
Create Temp File
Tool to upload bytes as a temporary file to Cloudflare R2 and return an S3 key. Use when you need a short-lived file reference before persisting it in a Thing.
Connect any two apps with Notis in the middle.
Notion and Bubble, 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 Bubble.