Shape CodeREADr scan responses from a matching Drive specification
Let a matching specification guide which response fields CodeREADr returns with scan data.
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
Manage CodeREADr Response Fields
Tool to create or update response fields returned with scan data. Use when customizing which fields to include in scan payloads.
Why this helps
Teams can collect scans successfully and still miss the context they need because response fields were never aligned with the work.
- Align scan response data with requirements in the source specification.
- Avoid repeated manual review of field requirements.
- Catch ambiguous or unsupported field requests in the run report.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and CodeREADr once in the Notis portal.
- 2Create an automation for response fields from matching Drive specifications.
- 3Tell Notis to read each matching file, identify requested scan response fields, and create or update those fields for the specified CodeREADr service; ask about missing service details.
- 4Pick New File Matching Query as the trigger and choose where run reports go.
- 5Test with one real matching specification and inspect the response fields.
Questions about this workflow
What query does this trigger use?
Choose the New File Matching Query trigger and use its available Drive query configuration. The workflow prompt handles what Notis does with a matching file.
Can the action add fields that are not supported?
Ask Notis to report requested fields that cannot be represented by the CodeREADr response field action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Codereadr. A trigger fires from one place; an action lands in another.
Google Drive triggers
Codereadr actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Collect Data With Questions
Tool to configure data collection forms by adding custom questions. Use after creating a service to collect survey questions after each scan.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Configure CodeREADr Connector
Helper to guide configuring the CodeREADr Connector for Google Sheets. There is no public API to programmatically create connector configurations. This tool validates your API connectivity (optional) and returns clear steps to proceed via the Google Sheets Add-on UI: https://www.codereadr.com/knowledgebase/codereadr-connector-add-on/
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Configure Direct Scan URL (DSU)
Tool to configure a Direct Scan URL (DSU). Use after obtaining a valid service ID to set up scan callbacks. Use when you need to enable or update the DSU postback settings for a CodeREADr service.
File Created
Triggers when a new file is created in Google Drive.
Configure CodeREADr Kiosk Mode
Tool to enable and configure Kiosk Mode for unattended scanning. Use when setting up a dedicated scanning kiosk after service setup.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Configure Picking, Delivery & Receiving App
Tool to configure the complete picking, delivery, and receiving workflow. Use when setting up scan workflow endpoints for an existing CodeREADr service.
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.
Configure CodeREADr Postback URL
Tool to configure a real-time postback URL for a CodeREADr service. Use when you need to set up or modify scan forwarding for an existing service.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Create CodeREADr Service
Tool to create a new workflow configuration (service) for scanning tasks. Use after obtaining a valid API key when registering a new Service.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Delete CodeREADr Database
Tool to delete an existing CodeREADr database. Use when you need to remove a database by its ID after confirming you no longer need its data. Example prompt: "Delete database with ID 123e4567-e89b-12d3-a456-426614174000".
Connect any two apps with Notis in the middle.
Google Drive and Codereadr, 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 Codereadr.