Connect Notion to Callingly
When something happens in Notion, Notis takes the next step in Callingly. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Callingly
Call new qualified leads
When a qualified lead is added to your Notion pipeline, ask Notis to place an outbound call through Callingly so promising inquiries get a prompt response.
Call on demo request updates
When a Notion lead record is updated to request a demo, have Notis initiate a Callingly outbound call so the next step is not buried in a pipeline.
Call on urgent inquiry notes
When the body of a Notion lead page is updated with an urgent callback request, ask Notis to start a Callingly outbound call based on that note.
Call when a callback is requested in comments
When someone adds a comment requesting a lead callback, ask Notis to start a Callingly outbound call and keep the request from being overlooked.
Call new event attendees for follow-up
When a new event attendee record is added to Notion with a clear request for a sales conversation, ask Notis to start a Callingly outbound call.
Call leads marked for re-engagement
When a Notion lead is updated to indicate re-engagement is due, have Notis start a Callingly outbound call to restart the conversation.
Call leads marked for a retry
When a Notion record is updated to request another attempt after an unanswered call, ask Notis to start a Callingly outbound call.
Act on workspace callback comments
When a callback request is posted as a Notion comment anywhere the integration can access, ask Notis to identify the associated lead context and place a Callingly call.
Call after a partner introduction page
When a new partner introduction page is created, ask Notis to place a Callingly call if the page contains an explicit introduction and contact details.
Supported Triggers and Actions
Notis builds workflows that link Notion to Callingly. A trigger fires from one place; an action lands in another.
Notion triggers
Callingly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Activate/Deactivate Client Account
Tool to activate or deactivate a client account. use when you need to toggle client access after onboarding or offboarding. example: "activate client 123" or "deactivate client 456".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Agent
Tool to create a new agent. use when you need to register an agent in callingly after gathering their account id and contact details.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Outbound Call
Tool to create a new outbound call record. use after gathering call and lead details.
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.
Create Client
Tool to create a new client. use when adding a new client to your callingly account.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Team
Tool to create a new team. use when setting up a team configuration before adding agents.
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.
Create Webhook
Tool to create a new webhook for call or lead events. use when you need to receive real-time notifications on specific events. example: "create a webhook for call completed events to http://example.com/callback".
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 Agent
Tool to delete an agent. use when permanently removing an agent after confirming the agent id.
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 Client
Tool to delete a client. use when you need to remove an existing client from your account after confirming its id.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Callingly
Connect any two apps with Notis in the middle.
Notion and Callingly, 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 Callingly.