Find company settings without leaving the Notion discussion
Ask the question where it comes up and let Notis retrieve the relevant Firmao configuration.
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
List Company Settings
Tool to list company settings. Use when retrieving custom configurations for a company, optionally filtered by organization or company ID.
Why this helps
A policy question can pull you away from work while you search through unfamiliar company settings.
- Bring relevant configuration into the discussion context.
- Avoid manual browsing through settings when answering a simple question.
- Get a run report that makes the lookup easy to revisit.
Setup
Build it in a few focused steps.
- 1Connect Notion and Firmao to Notis once in the portal.
- 2Create an automation in the portal or tell Notis to look up Firmao company settings when a Notion comment asks a policy question.
- 3Write one plain-language prompt that describes relevant questions and the summary format.
- 4Select the Notion Comment Created trigger and choose a channel for run reports.
- 5Test with a real comment asking about a known Firmao setting.
Questions about this workflow
Does this change company settings?
No. This workflow lists settings for review; it does not update or delete them.
Can this trigger on any workspace comment?
Yes, if the Notion integration can access the comment and its permissions include reading comments.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Firmao. A trigger fires from one place; an action lands in another.
Notion triggers
Firmao actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Tool to create an invoice. Use after gathering all invoice details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Company Setting
Tool to delete a specific company setting. Use when you need to remove a company setting by its unique ID after confirming the ID is valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Contact
Tool to delete a contact by marking it as deleted. Use when you need to soft-delete a contact after confirming its existence.
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.
Delete Invoice
Tool to delete an invoice. Use when you need to soft-delete a specific invoice by marking it deleted=true. Implements robust endpoint fallbacks and graceful degradation to ensure a validated response even when the API denies access or returns unexpected shapes.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Offer
Tool to delete an offer. Use when you need to soft-delete an existing offer by marking its deleted flag to true. After this call, the offer is considered deleted within the system.
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 Invoice
Tool to retrieve a specific invoice by its ID. Use when you need the full invoice data by its unique 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.
Get Offer
Tool to retrieve offer details. Use when you need complete information for a specific offer by 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.
Get Task
Tool to retrieve details of a specific task by its ID. Use when you need to fetch a task after knowing its ID.
Connect any two apps with Notis in the middle.
Notion and Firmao, 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 Firmao.