Find billing contacts from Notion comments
Bring contact context into the discussion when a comment signals the next client step.
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
Get Contacts
Tool to retrieve a list of contacts. use after authentication to fetch contacts in batches. example: 'list page 2 of active company contacts sorted by name.'
Why this helps
Useful client requests in comments can be separated from the billing contact information needed to act.
- Connect a new client discussion to billing contact context.
- Reduce searching after a comment signals work to do.
- Make follow-up easier to carry forward.
Setup
Build it in a few focused steps.
- 1Connect Notion and Elorus to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one instruction asking Notis to retrieve the matching Elorus contact when a comment is added to the chosen client page.
- 4Choose Comment Created, scope it to the client page, and select a channel for run reports.
- 5Test with one real client comment and check the contact result.
Questions about this workflow
What does this trigger require?
The Notion integration needs the Read comments capability. A connection authorized before it was enabled may need reauthorization.
Does it act on every workspace comment?
Scope the comment trigger to the relevant client page when setting up the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Elorus. A trigger fires from one place; an action lands in another.
Notion triggers
Elorus actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Tool to create a new invoice. use after gathering all invoice details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
CREATE_PRODUCT
Tool to create a new product or service in elorus. use when you need to add or configure items/services in your product catalog.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Email Invoice
Tool to email an existing invoice to specified contacts. use after generating an invoice and obtaining contact ids.
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 Bills
Tool to retrieve a list of bills. use when you need to list bills with optional filters after creation.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Contacts
Tool to retrieve a list of contacts. use after authentication to fetch contacts in batches. example: 'list page 2 of active company contacts sorted by name.'
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 Credit Notes
Tool to retrieve a list of credit notes. use when you need to fetch credit notes filtered by page, contact, date range, or currency.
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 Email Templates
Tool to retrieve a list of email templates. use when you need to fetch and page through existing templates in the organization.
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 Estimates
Tool to retrieve a list of estimates. use when you need to list estimates with pagination after creation.
Connect any two apps with Notis in the middle.
Notion and Elorus, 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 Elorus.