Carry vendor findings into the maintenance queue
Give post-visit repairs a clear next step by converting new Notion vendor notes into MaintainX work orders.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Create Work Order
This tool creates a new work order in maintainx. it uses the post /api/v1/workorders endpoint. the tool requires a 'title' for the work order and offers several optional parameters including description, priority, duedate, startdate, userids, teamids, proceduretemplateid, locationid, assetid, and categories.
Why this helps
Vendor recommendations can be noted during a visit but forgotten once the immediate conversation ends.
- Creates a work record while vendor findings are fresh.
- Keeps follow-up from depending on someone to revisit meeting notes.
- Makes actionable recommendations easier to track.
Setup
Build it in a few focused steps.
- 1Connect Notion and MaintainX to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Give Notis one instruction to create a work order for an actionable maintenance finding in a new vendor visit page.
- 4Select Page Created and scope it to the vendor visit parent page or data source when appropriate.
- 5Test by adding one real vendor visit note with a follow-up item.
Questions about this workflow
Can this watch only vendor visit pages?
Page Created can be scoped to the vendor visit data source or a parent page.
Can it distinguish recommendations from general notes?
Describe what counts as actionable maintenance in your plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Maintainx. A trigger fires from one place; an action lands in another.
Notion triggers
Maintainx actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Work Order
This tool creates a new work order in maintainx. it uses the post /api/v1/workorders endpoint. the tool requires a 'title' for the work order and offers several optional parameters including description, priority, duedate, startdate, userids, teamids, proceduretemplateid, locationid, assetid, and categories.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Work Order Comment
This tool creates a new comment on an existing work order in maintainx. it allows users to add comments for documentation, updates, or communication purposes within a specific work order. it requires a workorderid and the text content of the comment to create a new comment on the work order, providing capabilities to update maintenance work order records.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Work Request Portal
Creates a new work request portal in maintainx. a work request portal allows users to submit work requests through a dedicated url. the portal can be customized with a title, welcome text, and description placeholder. it can be associated with a specific location and asset, and can be configured to require email contact information.
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.
Find Entity
A tool to search and find specific entities within maintainx by specified fields. this tool allows users to search for different types of entities including work orders, users, and locations.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Assets
This tool allows users to retrieve a list of all assets in their organization.
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.
List Categories
This tool retrieves a list of all categories in your maintainx organization. categories are used to organize and classify work orders, assets, and other items in the system. it supports listing the categories with pagination and provides details such as category id, name, description, and timestamps for creation and update.
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.
List Locations
This tool retrieves a list of all available locations in the organization's maintainx account. the locations can be physical places where assets are located, work is performed, or maintenance is needed.
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.
List Teams
This tool retrieves a list of all teams in your maintainx organization.
Connect any two apps with Notis in the middle.
Notion and Maintainx, 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 Maintainx.