Give client comments a dependable next step
A client comment can be easy to miss among conversations. Let Notis turn relevant Notion comments into JobNimbus follow-up tasks.
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
Create Task
Tool to create a new task. use when scheduling or tracking tasks linked to contacts or jobs.
Why this helps
Requests embedded in comments are easy to overlook when they are not captured as actionable work.
- Captures comment-driven work as a task.
- Helps the team follow up without scanning comment threads repeatedly.
- Keeps a client's request connected to operational work.
Setup
Build it in a few focused steps.
- 1Connect Notion and JobNimbus to Notis once through the portal, with Notion comment access enabled.
- 2Create an automation in the portal or ask Notis to turn relevant Notion comments into JobNimbus tasks.
- 3Write one instruction explaining which comments need follow-up and what action Notis should record.
- 4Choose the Notion Comment Created trigger, select a channel for reports, and test with one real comment.
Questions about this workflow
Does Notion comment access need extra setup?
The Notion integration needs the Read comments capability. If it was authorized before that capability was enabled, reconnect it.
Can I scope this to one page?
The Comment Created trigger can be scoped to a page when you configure the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Jobnimbus. A trigger fires from one place; an action lands in another.
Notion triggers
Jobnimbus actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Location
Tool to create a new location in jobnimbus. use after gathering address and contact details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Activity by ID
Tool to retrieve a specific activity by its id. use after confirming the activity's jnid is valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Contact by ID
Tool to retrieve a contact by id. use after obtaining the contact’s jnid to fetch full 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.
List Contacts
Tool to list all contacts. use when you need to fetch multiple contacts, e.g., for reporting or synchronization.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create File Attachment Type
Tool to create a new file attachment type. use when you need to register a custom document category before uploading files.
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 Material Order
Tool to create a new material order (v2). use when you need to place a materials order for a contact after gathering item details.
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.
Create Task
Tool to create a new task. use when scheduling or tracking tasks linked to contacts or jobs.
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.
Create Workflow Status
Tool to create a new status in an existing workflow. use after confirming the workflow id to add specialized status entries like 'lead' or 'inspection'.
Connect any two apps with Notis in the middle.
Notion and Jobnimbus, 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 Jobnimbus.