Carry PO change review requests into Coupa
Record who should review a PO change in Notion and have Notis add them to the pending Coupa change approval chain.
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
Add Approver to PO Change
Tool to add an approver to a purchase order change after the current approver. Use when you need to manually add an approver to a pending PO change request in the approval chain.
Why this helps
Change requests wait when the reviewer is known but the approval chain is never updated.
- Move a clear reviewer handoff into the relevant approval chain.
- Keep change-request context close to its review record.
- Reduce reminders to route a pending change.
Setup
Build it in a few focused steps.
- 1Connect Notion and Coupa to Notis once through the portal.
- 2Create an automation in the portal or tell Notis how to route documented PO change reviews.
- 3Describe how to match the PO change and add only the explicitly named approver.
- 4Select the Notion Page Properties Updated trigger for the change tracker and choose a run-report channel.
- 5Test with one pending change request that needs a reviewer.
Questions about this workflow
Does this alter the PO change itself?
No. It adds an approver to the pending change approval chain.
Can it add a reviewer from vague notes?
The prompt should require a clearly named person and a matching pending PO change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Coupa. A trigger fires from one place; an action lands in another.
Notion triggers
Coupa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Abandon Invoice
Tool to abandon an invoice. Use when an invoice is invalid and needs to be abandoned. Invoice once abandoned cannot be reversed.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Account
Tool to create a Coupa account. Use when you need to provision a new general ledger account with a specific chart-of-accounts type and code segments.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Accounts
Tool to list accounts from Coupa. Use when you need to retrieve account IDs and codes with optional filters and pagination.
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 Recent Accounts
Tool to retrieve recently accessed accounts from Coupa. Use when you need to view accounts that the user has recently interacted with.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Account
Tool to retrieve a specific account by ID. Use when you need detailed account information including segments, type, and 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.
Update Account
Tool to update an existing Coupa account. Use when you need to modify account information including account type, activation status, code segments, and display name.
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 Account Types
Tool to list account types in Coupa. Use when you need account type IDs and names for account creation.
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 Account Type
Tool to retrieve a specific account type by ID. Use when you need detailed information about a chart of accounts.
Connect any two apps with Notis in the middle.
Notion and Coupa, 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 Coupa.