Check related Magnetic tasks when a Notion status changes
A status change can affect more than one task. Get related Magnetic work surfaced for a quick consistency check.
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
Search Magnetic Tasks
Tool to search tasks by a specified field and value. use when you need to filter and page tasks after authentication.
Why this helps
Status changes can be recorded in Notion while connected work in Magnetic remains unnoticed.
- Spot related tasks that may deserve a status check.
- Keep updates visible across both workspaces.
- Avoid relying on memory to revisit connected tasks.
Setup
Build it in a few focused steps.
- 1Connect Notion and Magnetic to Notis once through the portal.
- 2Create an automation with a prompt asking Notis to search Magnetic tasks related to a Notion page after its status changes.
- 3Select the Notion Page Properties Updated trigger for the relevant data source and choose a run-report channel.
- 4Test with one status change that has known related Magnetic work.
Questions about this workflow
Will this change Magnetic task statuses?
No. It searches tasks and reports related results for your review.
Can it respond only to certain properties?
The trigger includes updated property details; describe the relevant status change in the prompt so Notis can assess the event context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Magnetic. A trigger fires from one place; an action lands in another.
Notion triggers
Magnetic actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Follow-ups
Tool to retrieve upcoming follow-ups assigned to the authenticated user. use after authentication to view scheduled tasks.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search Client Contacts
Tool to search contacts by field or client id. use when you need to retrieve client contacts matching given criteria after authentication.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Contact Tags
Tool to get all tags associated with a contact. use after confirming the contactid to list contact tags.
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 Magnetic Groupings
Tool to retrieve a list of groupings. use after authentication when you need to select a grouping to comment on.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Grouping Statuses
Tool to retrieve the list of statuses for signed groupings. use after authentication when you need available grouping status options for tasks or jobs.
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 Grouping Tags
Tool to retrieve tags associated with any groupings owned by the company. use after authentication when grouping tags are needed.
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 Magnetic Opportunity Statuses
Tool to retrieve opportunity statuses. use when you need current status options for unsigned groupings (opportunities).
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 Magnetic Task
Tool to retrieve a task by its id. use after confirming you have the taskid.
Connect any two apps with Notis in the middle.
Notion and Magnetic, 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 Magnetic.