Estimate cost implications from a scope discussion
A new comment flags a possible scope change; prompt a pricing estimate for the Fal.ai endpoints and usage under discussion.
Trigger
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.
Action
Estimate Pricing
Tool to estimate pricing for fal.ai model endpoints. Use when you need to calculate expected costs for API calls or unit-based usage across one or more endpoints.
Why this helps
Scope changes can be discussed informally without anyone checking their impact on expected media costs.
- Connect a scope discussion to a timely pricing check.
- Review cost implications before committing to a change.
- Reduce the chance that budget follow-up gets lost in comments.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fal.ai to Notis once in the portal.
- 2Create an automation from the portal or ask Notis to create it conversationally.
- 3Write one plain-language instruction asking Notis to estimate Fal.ai pricing when a comment proposes a media scope change.
- 4Choose Comment Created, pick a run-report channel, and test with one real scope question.
Questions about this workflow
Will every comment cause an estimate?
Comment Created is broad unless scoped to a page. The instruction should ask Notis to estimate only when a comment raises a media scope change.
What should the comment say?
Describe the change and the relevant endpoint or usage assumptions so the estimate can be grounded.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fal.ai. A trigger fires from one place; an action lands in another.
Notion triggers
Fal.ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel Queue Request
Tool to cancel a queued or in-progress request in fal.ai's queue system. Use when you need to stop a request before it completes. Note that cancellation only succeeds if the request hasn't started processing; if already completed, returns an error status. Even with successful cancellation, the request may still execute if it was near the front of the queue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Estimate Pricing
Tool to estimate pricing for fal.ai model endpoints. Use when you need to calculate expected costs for API calls or unit-based usage across one or more endpoints.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get JWKS for Webhook Verification
Tool to retrieve public keys for webhook signature verification. Returns a JSON Web Key Set containing ED25519 public keys. Use when you need to verify webhook signatures from fal.ai. The keys are cacheable but should be refreshed at least every 24 hours.
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.
Get Models
Tool to discover and search fal.ai model endpoints. Use when you need to list all models, find specific models by ID, or search by category/query. Supports pagination and optional expansion of OpenAPI schemas.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Model Pricing
Tool to retrieve unit pricing for model endpoints. Returns pricing information including unit price, billing unit, and currency. Use when you need to check costs for specific fal.ai models.
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.
Get Queue Request Result
Tool to retrieve the final result of a completed queue request. Use when you need to get the output of a model request that was submitted to the queue and has finished processing. Only works after request status transitions to COMPLETED.
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.
Get Queue Request Status With Logs
Tool to retrieve the current status of a queued request with detailed logging information. Use when you need to monitor a queued request's progress and access execution logs for debugging or tracking purposes. Logs include timestamps, severity levels, and detailed messages about request processing.
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.
Check Queue Request Status
Tool to check the status of a queued request in fal.ai. Use when you need to monitor the progress of an async request. Returns different information based on status: queue position when IN_QUEUE, logs when IN_PROGRESS or COMPLETED.
Connect any two apps with Notis in the middle.
Notion and Fal.ai, 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 Fal.ai.