Bring matching Drive research into Attio
Let a saved Drive query surface new research files and ask Notis to create a corresponding Attio record for each useful match.
Trigger
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
Action
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.
Why this helps
Research files can accumulate in Drive without becoming visible in the Attio workflow where you plan relationship follow-up.
- Bring query-matched research into Attio as it appears.
- Keep qualifying material visible in your existing workflow.
- Reduce manual review and re-entry of new research files.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Attio once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for the research you track.
- 3Tell Notis what matching files should become Attio records and which details provide useful context.
- 4Choose the New File Matching Query trigger and where run reports should go.
- 5Test with one real matching file and review the created record.
Questions about this workflow
How does the workflow decide which new files match?
The New File Matching Query trigger uses the query configuration you provide for Drive.
Can I create a record for every matching file?
Yes, if that is the intended outcome. Describe the Attio object type and details to include, and consider how you want to handle duplicates.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Attio. A trigger fires from one place; an action lands in another.
Google Drive 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.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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.
File Created
Triggers when a new file is created in Google Drive.
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.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
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.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
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.
Google Drive 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.