Organize new trust-library sections in Conveyor
Add a section to your Notion trust library and prompt Notis to create its home in Conveyor.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Create new folder
Tool to create a new folder in Conveyor Exchange. Use when you need to organize items into folders programmatically after obtaining an API key.
Why this helps
New content areas can lack a predictable place for their related customer-facing documents.
- Give new trust sections a corresponding document home.
- Reduce setup chores when expanding a library.
- Keep content organization aligned across tools.
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 describe the result to Notis.
- 3Write one instruction asking Notis to create a Conveyor folder for each new subpage under the trust-library page.
- 4Choose Notion Page Added to Page for that parent page and select a run-report channel.
- 5Test by adding one example section and confirm the folder exists.
Questions about this workflow
Can this create a folder anywhere in Conveyor?
The prompt can describe the intended organization. Test the folder placement and naming with an example.
What page triggers the workflow?
It triggers when a new subpage is added under the selected Notion parent page.
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.
Delete a Conveyor document
Tool to delete a specific document. Use when you need to remove a document by its ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete folder
Tool to delete a folder by its ID. Use when you need to remove a specific folder after confirming its ID.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
Get Authorization Request
Tool to fetch details of a specific authorization request. Use when you need to retrieve metadata by authorization_request_id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Authorization Requests
Tool to fetch authorization requests. Use when you need to list authorization requests, optionally filtered by status.
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.
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.
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.
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.
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.
Get all Conveyor documents
Tool to retrieve all documents. Use after authenticating with a valid API key.
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.