Check Callerapi credits as you build an operations view
When you create a new Notion view for tracking work, let Notis fetch Callerapi account details while you are already setting up your workflow.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Get User Information
Tool to retrieve information about the authenticated user, including email and credit usage details. use after authentication to fetch credits spent, monthly allocation, and credits left.
Why this helps
A new tracking setup often prompts several small checks, and account usage can be one more detail that slips through.
- Pair a workspace setup moment with a quick account information check.
- See Callerapi credit availability in a run report without a separate task.
- Keep operations setup details easier to gather in one place.
Setup
Build it in a few focused steps.
- 1Connect Notion and Callerapi to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Tell Notis to retrieve Callerapi account information when a new view is created and summarize credits spent, allocation, and credits left.
- 4Select View Created as the trigger and choose a channel for run reports.
- 5Test by creating a Notion view and checking the resulting summary.
Questions about this workflow
Why use a view-created trigger for an account check?
It can pair a new tracking setup with an account review, though a recurring schedule may suit routine monitoring better.
What information does the Callerapi action return?
It retrieves authenticated user details, including email and credit usage information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Callerapi. A trigger fires from one place; an action lands in another.
Notion triggers
Callerapi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Phone Number Information
Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Information
Tool to retrieve information about the authenticated user, including email and credit usage details. use after authentication to fetch credits spent, monthly allocation, and credits left.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Callerapi, 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 Callerapi.