Keep the Magnetic team roster easy to reference
When a work page changes, surface the Magnetic user list for a quick ownership and handoff review.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Get Users
Tool to retrieve the list of all users in the authenticated user's company. use after authentication to audit or manage user accounts.
Why this helps
It can be easy to forget who is available to own the next step, especially when project context is shifting.
- See the company user roster during a handoff review.
- Reduce the effort of finding team ownership context.
- Keep people lookup connected to active work changes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Magnetic to Notis once through the portal.
- 2Create an automation with one prompt asking Notis to retrieve Magnetic users as a reference when a relevant Notion page changes.
- 3Select the Notion All Page Events trigger and choose a channel for run reports.
- 4Test on a relevant page update and review the roster output.
Questions about this workflow
Does this assign an owner?
No. It retrieves the Magnetic user list for reference; it does not assign work.
How can I avoid irrelevant page changes?
Describe the kinds of pages that matter in the prompt and review whether the workspace-wide trigger suits your use case.
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.