Carry meeting preparation progress into Attio
Mark preparation complete in Notion and let Notis update the related Attio record, making the next meeting easier to track.
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
Update Record
This tool updates an existing record in attio for a specified object type (people, companies, deals, users, workspaces, etc.). it uses patch to partially update only the provided fields, leaving other fields unchanged.
Why this helps
Meeting preparation is easy to repeat or forget when its status is separated from the relationship record.
- See preparation progress alongside the relationship.
- Reduce uncertainty before a meeting.
- Keep a lightweight process in sync across tools.
Setup
Build it in a few focused steps.
- 1Connect Notion and Attio once in the portal.
- 2Create an automation in Automations or ask Notis to create it conversationally.
- 3Use one instruction asking Notis to update the related Attio person or company when meeting preparation properties change in Notion.
- 4Select Page Properties Updated for the meeting data source and choose a report channel.
- 5Change the status on one real meeting page and review the associated Attio record.
Questions about this workflow
Can it update only preparation status?
Describe the status information to carry over, and ask Notis to update the matching record with that information.
How is the relationship identified?
Explain how the meeting page identifies the attendee or organization represented in Attio.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Attio. A trigger fires from one place; an action lands in another.
Notion triggers
Attio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Note
This tool creates a new note on a given record in attio. the note can be attached to any record type (like person, company, or deal) and includes a title and content. it requires parameters such as parent object, parent record id, title, and content, with an optional created at timestamp.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Record
This tool creates a new record in attio for a specified object type (people, companies, deals, users, workspaces, etc.). it requires the object type and a values dictionary containing the attributes for the new record.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Note
This tool allows users to delete a specific note in attio by its id. it is implemented via delete https://api.attio.com/v2/notes/{note id} and handles note deletion by validating the provided note id. it complements attio create note functionality, providing complete note management capabilities within the attio platform.
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.
Delete Record
This tool allows you to delete a record from attio permanently. the deletion is irreversible, and the data will eventually be removed from the system.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Find Record
This tool allows users to find a record in attio by either its unique id or by searching using unique attributes. it provides two methods: one for directly retrieving a record by its id with the get /v2/objects/{object}/records/{record id} endpoint, and another for searching by attributes using the post /v2/objects/{object}/records/query endpoint.
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 Object Details
This tool retrieves detailed information about a specific object type in attio, including all its attributes and their properties. this is useful for understanding what fields are available when creating or updating records of this type.
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 Lists
This tool retrieves all lists available in the attio workspace. the lists are returned sorted as they appear in the sidebar. this tool is essential for managing and navigating lists, and is a prerequisite for many list-related operations. it requires the list configuration:read permission scope.
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 Notes
This tool lists all notes associated with a specific record in attio. notes are returned in reverse chronological order (newest first).
Connect any two apps with Notis in the middle.
Notion and Attio, 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 Attio.