Keep opportunity records aligned with working briefs
Notis can carry a revised Notion opportunity brief into the matching Dynamics 365 opportunity, so CRM context stays useful.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Update Opportunity
Updates an existing opportunity entity record in dynamics crm using the web api.
Why this helps
Founders often refine a deal plan in a working document but forget to update the sales record that others rely on.
- Refresh an existing opportunity after its Notion brief changes.
- Keep deal context closer to the team's working notes.
- Reduce the follow-up task of repeating an update across systems.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dynamics 365 to Notis through the portal once.
- 2Create an automation in the portal or ask Notis for the desired workflow in plain language.
- 3Use one instruction to update the matching Dynamics 365 opportunity when its Notion brief content changes.
- 4Choose Page Content Updated and scope it to the opportunity brief page or database, then select a report channel.
- 5Test by changing one real brief and reviewing its Dynamics 365 opportunity.
Questions about this workflow
Can the trigger be limited to one brief?
Yes. Page Content Updated can be scoped to a specific Notion page or to rows from a data source.
What should the instruction say?
State that Notis should find the corresponding Dynamics 365 opportunity and update it using the changed Notion brief.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dynamics365. A trigger fires from one place; an action lands in another.
Notion triggers
Dynamics365 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get all invoices action
Get all invoices action
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Account
Creates a new account entity record in dynamics crm using the web api.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Case
Creates a new case (incident) entity record in dynamics crm using the web api.
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.
Create Contact
Creates a new contact entity record in dynamics crm using the web api.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Invoice
Creates a new invoice entity record in dynamics crm using the web api.
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.
Create Lead
Creates a new lead entity record in dynamics crm using the web api.
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.
Create Opportunity
Creates a new opportunity entity record in dynamics crm using the web api.
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.
Create Sales Order
Creates a new sales order entity record in dynamics crm using the web api.
Connect any two apps with Notis in the middle.
Notion and Dynamics365, 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 Dynamics365.