Extract webpage details from matching research files
When a new research file matches your Drive query trigger, collect the page details named in its instructions.
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
Scrape webpage content using CSS selectors
A tool to extract structured content from a webpage by specifying css selectors. the tool navigates to the specified url, waits for the page to load (including parsing and executing javascript), and returns the selected elements in a structured json format.
Why this helps
Repeated research requests often mean reopening pages and copying the same kinds of details by hand.
- Collect requested page details in a structured result.
- Start only for new files that meet the existing query trigger.
- Keep research capture tied to its Drive source.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Browserless once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to use the matching file's URL and extract the details it requests.
- 4Pick New File Matching Query as the trigger and choose where run reports go.
- 5Test with one real file that matches the trigger's existing query.
Questions about this workflow
Does this create or configure the Drive query?
No. Choose the existing New File Matching Query trigger and its query configuration in the trigger setup.
What should the matching file contain?
Include a webpage URL and the specific details you want extracted.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Browserless. A trigger fires from one place; an action lands in another.
Google Drive triggers
Browserless actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Download file using Puppeteer script
This tool allows downloading files that chrome has downloaded during the execution of puppeteer code. it sets up a blank page, creates a fresh download directory, injects the provided code, and executes it. once the script finishes, any downloaded files from chromium are returned with the appropriate content-type header.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Custom Function
A tool that allows executing custom puppeteer scripts via http requests. this endpoint enables users to run browser automation tasks without managing their own infrastructure.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Fetch HTML Content
This tool fetches the complete html content of a webpage using browserless's content api. it's designed to retrieve the full html contents of any website, including dynamically generated content.
File Created
Triggers when a new file is created in Google Drive.
Generate PDF from webpage
This tool generates a pdf from a specified webpage using browserless's pdf generation api. it allows specifying the url of the webpage along with parameters such as format, filename, and waituntil options to control the pdf generation process.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Scrape webpage content using CSS selectors
A tool to extract structured content from a webpage by specifying css selectors. the tool navigates to the specified url, waits for the page to load (including parsing and executing javascript), and returns the selected elements in a structured json format.
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.
Take Screenshot
A tool that captures a screenshot of a webpage using browserless's screenshot api. the tool takes a url and returns either a png or jpeg image. it includes options for full page capture, image type, quality, and clipping coordinates.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Unblock Protected Content
This tool provides access to content from websites that implement bot protection mechanisms. it is designed to bypass various types of protection (such as captcha and bot detections) and return the html content of the protected webpage, with optional customization through parameters like waitfor, timeout, and stealth mode.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Browserless, 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 Browserless.