Skip to content
Notis

Keep Facebook Page task access aligned with Notion

Update the access record in Notion and prompt Notis to remove the corresponding Facebook Page task.

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 Page Task

Removes a user's tasks/access from a specific facebook page.

Why this helps

Page responsibilities can remain assigned after an ownership change if the access follow-up is missed.

  • Carry documented offboarding into Page task management.
  • Reduce reliance on memory for access follow-up.
  • Keep the Notion access record connected to the Page change.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Facebook to Notis once in the portal.
  • 2Create an automation with a prompt to remove the named user's Facebook Page task when the Notion access record explicitly requests removal.
  • 3Select Page Properties Updated, choose a run-report channel, and create it.
  • 4Test with one real access-change request and confirm the intended task is removed.

Questions about this workflow

Does this remove every Page role?

The action removes a specified task or access assignment. Describe the intended user and task clearly in the prompt.

How can I avoid acting on an unfinished request?

Use a clear approved removal status in Notion and tell Notis to act only when that request is present.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Facebook actions

Recurring trigger

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

TriggerScheduled

Add Photos to Album

Adds photos to an existing facebook album. note: currently adds one photo at a time. for true batch upload, use facebook's batch api endpoint directly.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Reaction

Adds a specific reaction (like, love, wow, etc.) to a facebook post or comment.

ActionInstant

All Page Events

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

TriggerPolling

Assign Page Task

Assigns tasks/roles to a user for a specific facebook page.

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

Create Comment

Creates a comment on a facebook post or replies to an existing comment.

ActionInstant

New Comment

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

TriggerPolling

Create Photo Album

Creates a new photo album on a facebook page.

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 Photo Post

Creates a photo post on a facebook page.

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 Post

Creates a new post on a facebook page.

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 Video Post

Creates a video post on a facebook page.

ActionInstant

Connect any two apps with Notis in the middle.

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