Create agents from approved onboarding updates
Turn a completed, approved agent record into the next setup step.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
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.
Why this helps
Agent details can sit in an onboarding queue because someone must remember to recreate them in Callingly.
- Reduce duplicate agent setup entry.
- Tie creation to a visible approval point.
- Keep agent onboarding progress connected to its Notion record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Callingly to Notis once through the portal.
- 2Create a prompt asking Notis to create a Callingly agent only when an updated onboarding record is approved and contains required details.
- 3Select Page Properties Updated for the agent onboarding data source and choose a channel for run reports.
- 4Approve one real test agent record and verify the agent appears in Callingly.
Questions about this workflow
Can a record update create an agent before approval?
Tell Notis to wait for an explicit approved status and to act only when the record is complete.
Does this add the agent to a team?
No. It creates the agent; team membership is handled separately.
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.