Skip to content
Notis

Follow up with new leads by voice

Turn a new lead record into a timely voice follow-up with your Bolna agent.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

Make a phone call from agent

Initiate calls

Why this helps

New inquiries can get buried while you switch between your CRM and calling tools.

  • Respond to new leads without manually checking the database.
  • Keep first contact moving during busy workdays.
  • Use a consistent voice agent for routine outreach.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Bolna to Notis once through the portal.
  • 2Create an automation in the portal, or ask Notis conversationally to call new leads added to your Notion database with your Bolna agent.
  • 3Select Notion New Page as the trigger and choose a channel for run reports.
  • 4Test with one real lead entry and check the Bolna call result.

Questions about this workflow

What starts the call?

A new page added to the selected Notion database starts the automation.

Do I map lead fields into Bolna?

No. Describe the intended call in the plain-language automation prompt, and Notis interprets the request.

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.

TriggerScheduled

Delete agent by id

Delete an agent

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete batch by id

Delete a batch

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Fetch all batches by agent id

List all batches for agent

ActionInstant

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.

TriggerInstant

Get all agents

List all agents

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get all phone numbers

List all phone numbers for your account

ActionInstant

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.

TriggerInstant

Get execution by id

Retrieve specific execution by `execution id`

ActionInstant

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.

TriggerInstant

Make a phone call from agent

Initiate calls

ActionInstant

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.

TriggerInstant

Retrieve agent by id

Retrieve an agent

ActionInstant

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.