Connect Addressfinder to Bolna

When something happens in Addressfinder, Notis takes the next step in Bolna. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Addressfinder to Bolna

View example

Call a Contact After Addressfinder Validation

Validate a contact's details with Addressfinder, then ask a Bolna agent to place a call using the verified information.

View example

Prepare a Bolna Calling Batch from Validated Leads

Check submitted lead phone numbers with Addressfinder, then create a Bolna batch from the contacts that pass validation.

View example

Set Up Inbound Calls on a Verified Number

Validate a submitted phone number with Addressfinder before adding a Bolna agent for inbound calls.

View example

Create a Bolna Agent for a Verified Contact Flow

Validate the contact details and create a configured Bolna voice agent for a new outreach or service flow.

View example

Create a Bolna Knowledgebase from a Verified Request

Validate the submitted contact information and create a Bolna knowledgebase from the supplied web URLs or PDFs.

View example

Review Your Bolna Agent Inventory on a Schedule

Ask Notis to periodically retrieve the Bolna agent list and send a concise report for review.

View example

Review Bolna Phone Numbers on a Schedule

Periodically retrieve the phone numbers in your Bolna account and receive a short report for review.

View example

Review Bolna Agent Executions on a Schedule

Periodically retrieve executions for a specified Bolna agent and send a concise run report for follow-up.

View example

Check a Bolna Execution by ID on a Schedule

Retrieve the latest details for a specified Bolna execution ID on a recurring schedule and report the result.

Supported Triggers and Actions

Notis builds workflows that link Addressfinder to Bolna. A trigger fires from one place; an action lands in another.

Addressfinder 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

Permanently deletes a voice AI agent and all its associated data.

ActionInstant

Webhook trigger

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

TriggerInstant

Abort workflow campaign

Aborts a running or paused campaign and stops executions; the terminal campaign cannot resume or be deleted.

ActionInstant

Delete batch by id

Permanently deletes a batch campaign; this cannot be undone.

ActionInstant

Add custom LLM model

Registers a custom OpenAI-compatible language model endpoint.

ActionInstant

Fetch all batches by agent id

Lists batches associated with a voice AI agent.

ActionInstant

Add Provider to Bolna

Adds a telephony or voice service provider to the account.

ActionInstant

Get all agents

Lists the voice agents configured in an account.

ActionInstant

Add number to SIP trunk

Adds a DID phone number to a SIP trunk.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.