Skip to content
Notis

See the details behind a changing access request

A change to a tracked request can prompt a focused lookup of its Conveyor authorization details.

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

Get Authorization Request

Tool to fetch details of a specific authorization request. Use when you need to retrieve metadata by authorization_request_id.

Why this helps

Request updates create a follow-up task to locate the matching access record and inspect its status.

  • Bring request details into the update workflow.
  • Reduce hunting for an authorization by identifier.
  • Keep follow-up tied to the Notion request record.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Conveyor to Notis once in the portal.
  • 2Create an automation in the portal or tell Notis the intended outcome.
  • 3In one plain-language instruction, ask Notis to fetch details for the Conveyor authorization request related to an updated Notion record.
  • 4Choose Notion Page Properties Updated for the request database and select a channel for run reports.
  • 5Test with one record linked to a known authorization request.

Questions about this workflow

What does Conveyor need for this lookup?

The action fetches a specific authorization request, so the prompt needs enough context to identify its request ID.

Does this make a change to the request?

No. It retrieves the request details.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Conveyor actions

Recurring trigger

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

TriggerScheduled

Delete a Conveyor document

Tool to delete a specific document. Use when you need to remove a document by its ID.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete folder

Tool to delete a folder by its ID. Use when you need to remove a specific folder after confirming its ID.

ActionInstant

All Page Events

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

TriggerPolling

Generate/Validate API Token Guidance

Tool to validate API token and provide guidance. Conveyor does not support API-based token creation; tokens must be created in the Conveyor UI. This action performs a real API call (using the provided metadata) to validate the existing API token and returns structured guidance.

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

Get Authorization Request

Tool to fetch details of a specific authorization request. Use when you need to retrieve metadata by authorization_request_id.

ActionInstant

New Comment

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

TriggerPolling

Get Authorization Requests

Tool to fetch authorization requests. Use when you need to list authorization requests, optionally filtered by status.

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

Get all authorization requests

Tool to retrieve all authorization requests. Use when you need to list all authorizations; optionally filter by status. Use after authenticating with a valid API token.

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

Get all Conveyor connections

Tool to retrieve all connections. Use when you need to fetch the complete list of your Conveyor connections. Use after authenticating with a valid API key.

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

Get all Conveyor documents

Tool to retrieve all documents. Use after authenticating with a valid API key.

ActionInstant

Connect any two apps with Notis in the middle.

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