Turn customer issues in Notion into Kommo tasks
Log a customer issue once and let Notis create a follow-up task in Kommo.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Kommo Tasks
Action to create a task in kommo crm.
Why this helps
Customer issues can be documented clearly yet still lack a concrete next action in the system you revisit for follow-up.
- Give customer issues a clear follow-up path.
- Keep related work visible in Kommo.
- Reduce the chance that documented concerns are left without action.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kommo to Notis once through the portal.
- 2Create an automation and prompt Notis to create a Kommo task when a new customer issue record is added in Notion.
- 3Select the Notion New Page trigger scoped to the issue data source and choose a channel for run reports.
- 4Test with one real customer issue and confirm its follow-up task appears in Kommo.
Questions about this workflow
Can the task include the customer context?
Describe in the prompt that the task should carry the relevant context from the Notion issue record.
Will this work with an issue database?
Yes. Select the New Page trigger scoped to the Notion data source containing the issue records.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kommo. A trigger fires from one place; an action lands in another.
Notion triggers
Kommo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Kommo Companies
Action to add one or more companies into the kommo account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Kommo Contact
Action to create one or more contacts in kommo crm.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Kommo Lead
Action to create one or more leads in kommo crm.
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.
Create Kommo Tasks
Action to create a task in kommo crm.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Kommo Companies
Action to list kommo companies with various filter options.
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.
List Kommo Contacts
Action to list contacts in kommo crm.
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.
List Kommo Custom Fields
Action to list custom fields in kommo crm.
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.
List Kommo Leads
Action to list leads in kommo crm.
Connect any two apps with Notis in the middle.
Notion and Kommo, 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 Kommo.