Clear outdated support markers automatically
Let a resolved Notion issue remove its corresponding tag from the customer profile in Intercom.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Remove tag from a contact
You can remove tag from a specific contact. this will return a tag object for the tag that was removed from the contact.
Why this helps
Old issue tags can continue to signal urgency after the underlying work is complete.
- Keep customer markers current as work changes.
- Reduce forgotten cleanup tasks.
- Make support signals easier to trust.
Setup
Build it in a few focused steps.
- 1Connect Notion and Intercom to Notis once.
- 2Create an automation through the portal or ask Notis in plain language.
- 3In one instruction, explain which cleared issue should remove which tag from the matching Intercom contact.
- 4Choose Page Properties Updated and select a channel for run reports.
- 5Test with one real cleared issue and confirm the tag is removed.
Questions about this workflow
Can this remove any contact tag?
The action removes a tag from a contact; specify the relevant tag and matching contact clearly.
What triggers the cleanup?
A change to a Notion page's properties starts the workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Intercom. A trigger fires from one place; an action lands in another.
Notion triggers
Intercom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add subscription to a contact
You can add a specific subscription to a contact. in intercom, we have two different subscription types based on user consent - opt-out and opt-in: 1.attaching a contact to an opt-out subscription type will opt that user out from receiving messages related to that subscription type. 2.attaching a contact to an opt-in subscription type will opt that user in to receiving messages related to that subscription type. this will return a subscription type model for the subscription type that was added to the contact.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add tag to a contact
You can tag a specific contact. this will return a tag object for the tag that was added to the contact.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Assign conversation
Assigns a conversation to a specific admin or team in intercom
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.
Attach a contact to a company
You can attach a company to a single contact.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Close conversation
Closes a conversation in intercom, marking it as resolved
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 a collection
You can create a new collection by making a post request to `https://api.intercom.io/help center/collections.`
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 an article
You can create a new article by making a post request to `https://api.intercom.io/articles`.
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 a note
You can add a note to a single contact.
Connect any two apps with Notis in the middle.
Notion and Intercom, 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 Intercom.