Turn capacity plans into team settings
Put a reviewed agent capacity decision into effect without another tool handoff.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Update Team Agent Settings
Tool to update settings (priority, capacity) for a specific team agent. use when adjusting an agent's priority or call capacity after team configuration.
Why this helps
Capacity decisions can remain notes instead of changing how calls are distributed across a team.
- Make approved capacity decisions actionable.
- Keep team distribution settings tied to planning context.
- Reduce manual follow-through after staffing discussions.
Setup
Build it in a few focused steps.
- 1Connect Notion and Callingly to Notis once through the portal.
- 2Create a prompt asking Notis to update a specified team agent's priority or capacity only from an approved plan.
- 3Select Page Created for the capacity plan data source and choose a channel for run reports.
- 4Create one approved test plan and verify the agent setting in Callingly.
Questions about this workflow
Which agent settings can this change?
The action supports updating team agent settings such as priority and capacity.
Can a draft capacity plan change routing?
The prompt should require an explicit approval signal before Notis updates team settings.
When this happens · Trigger
Do this · Action
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.
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.