Skip to content
Notis

Reflect customer offboarding in Engage accounts

Mark an offboarding change in Notion and let Notis remove the customer from the associated Engage account.

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 Customer from Account

Tool to remove a Customer from an Account in Engage. Use when you need to disassociate a customer from a specific account.

Why this helps

Account membership can stay outdated after an offboarding decision if it requires a separate manual update.

  • Keep account membership current.
  • Reduce follow-up steps during offboarding.
  • Make a recorded decision carry through to the account.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Engage to Notis once through the portal.
  • 2Create an automation in the portal or describe the desired outcome to Notis in plain language.
  • 3Ask Notis to remove the customer from the associated Engage account when the Notion offboarding status is updated.
  • 4Choose the Notion Page Properties Updated trigger for the offboarding database and select a channel for run reports.
  • 5Test with one real offboarding record and verify the account membership.

Questions about this workflow

Does removing a customer from an account delete the user?

No. This action disassociates the customer from the specified account.

Can the automation respond only to offboarding?

State the offboarding status change clearly in the plain-language instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Engage. A trigger fires from one place; an action lands in another.

Notion triggers

Engage actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Customer to Accounts

Tool to add a customer to one or more account entities. Use when you need to associate a user with accounts and optionally assign roles.

ActionInstant

Webhook trigger

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

TriggerInstant

Add User to Lists

Tool to add a Customer or Account to one or more Lists in Engage.so. Use when you need to subscribe a user to specific lists for targeted messaging.

ActionInstant

All Page Events

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

TriggerPolling

Archive List

Tool to archive a List in Engage. Use when you want to prevent new subscribers from being added to a list. Existing subscribers will not be affected.

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

Archive User

Tool to archive a user in Engage. Use when you need to deactivate a user account while preserving all historical data. The user will stop being active and all engagement and events for the user will be stopped, but all messages, logs, and related data will be preserved.

ActionInstant

New Comment

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

TriggerPolling

Convert User Type

Tool to convert a user between Customer and Account entity types. Use when you need to change a customer to an account or vice versa.

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 List

Tool to create a new List in Engage for organizing subscribers. Use when you need to set up a new list for managing contacts or subscribers.

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 User

Tool to create a new user (Customer or Account) in Engage. Use when you need to add a user with optional metadata, device tokens, or list subscriptions.

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

Delete Subscriber From List

Tool to remove a subscriber from a List entirely (different from unsubscribing). Use when you need to completely delete a subscriber's association with a specific list.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Engage, 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 Engage.