Keep handoffs moving as their details change
When a handoff changes, make the account's people easy to look up again.
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 Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
Why this helps
Updated ownership or timing details can leave a handoff waiting for someone to rediscover the right contacts.
- Refresh contact context when handoff details change.
- Reduce repeated searching for collaborators.
- Make updates easier to follow through on.
Setup
Build it in a few focused steps.
- 1Connect Notion and Appveyor to Notis once in the portal.
- 2Create an automation in the portal, or tell Notis to retrieve Appveyor users when a handoff page's properties are updated.
- 3Pick the Notion Page Properties Updated trigger for your handoff data source.
- 4Choose a channel for run reports and test with one changed handoff.
Questions about this workflow
Does this assign a new owner?
No. It retrieves users to support the handoff decision.
What changes can trigger it?
The trigger fires on page property updates. The prompt should describe the handoff context to report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Appveyor. A trigger fires from one place; an action lands in another.
Notion triggers
Appveyor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Environments
Tool to get a list of all deployment environments. use when you need to enumerate available environments before creating deployments.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
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 Role
Tool to retrieve details of a specific role. use when you need to inspect permissions and metadata of a role by id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Roles
Tool to retrieve all roles in the account. use when you need to enumerate available roles before assigning permissions.
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 Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Appveyor, 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 Appveyor.