Bring agent execution details into a Notion follow-up
Update an agent follow-up page and have Notis retrieve the relevant Bolna execution details.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Retrieve agent execution details
Retrieve specific execution by an agent
Why this helps
Looking up one execution can interrupt the follow-up task that prompted the check.
- Gather specific execution details as follow-up work begins.
- Avoid a separate manual lookup step.
- Keep review context near the Notion page that prompted it.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bolna to Notis once through the portal.
- 2Create an automation explaining which execution the page refers to and asking Notis to retrieve its agent execution details.
- 3Select Notion Page Updated as the trigger and scope it to the specified page.
- 4Choose a channel for run reports and test with one real page update.
Questions about this workflow
How is this different from getting an execution by id?
This action retrieves execution details through the agent context, while Get execution by id retrieves a specific execution directly.
Can it watch one Notion page?
Yes. Scope the Page Updated trigger to the page used for follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bolna. A trigger fires from one place; an action lands in another.
Notion triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Fetch all batches by agent id
List all batches for agent
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 all agents
List all agents
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get all phone numbers
List all phone numbers for your account
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.
Get execution by id
Retrieve specific execution by `execution id`
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.
Make a phone call from agent
Initiate calls
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.
Retrieve agent by id
Retrieve an agent
Connect any two apps with Notis in the middle.
Notion and Bolna, 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 Bolna.