Skip to content
Notis

Keep customer messaging preferences in sync

Carry a recorded customer consent change from Notion into the corresponding Intercom subscription.

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

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.

Why this helps

Messaging preferences can be recorded during customer work and then forgotten when subscription settings need updating.

  • Reduce manual preference updates.
  • Keep recorded consent connected to messaging settings.
  • Make follow-up more consistent with customer preferences.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Intercom to Notis once.
  • 2Create the automation in the portal or ask Notis in plain language.
  • 3In one instruction, tell Notis how to interpret the recorded preference and update the matching Intercom subscription type.
  • 4Select Page Properties Updated and choose a channel for run reports.
  • 5Test with a real preference change and confirm the subscription state in Intercom.

Questions about this workflow

Can this handle opt-in and opt-out preferences?

The Intercom action supports adding a contact to an opt-in or opt-out subscription type; describe the intended meaning clearly.

Does the workflow send a message?

No. It changes a contact's subscription association.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Assign conversation

Assigns a conversation to a specific admin or team in intercom

ActionInstant

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.

TriggerInstant

Attach a contact to a company

You can attach a company to a single contact.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Close conversation

Closes a conversation in intercom, marking it as resolved

ActionInstant

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.

TriggerInstant

Create a collection

You can create a new collection by making a post request to `https://api.intercom.io/help center/collections.`

ActionInstant

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.

TriggerInstant

Create an article

You can create a new article by making a post request to `https://api.intercom.io/articles`.

ActionInstant

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.

TriggerInstant

Create a note

You can add a note to a single contact.

ActionInstant

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.