Set up a CodeREADr Direct Scan URL callback on demand
Trigger a callback configuration run when your operations process is ready for a service update.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Callback setup can interrupt work when the service ID and requested postback change need to be found and handled manually.
- Start configuration from an existing HTTP-based process.
- Use the service details included with the request.
- Get a run report to confirm the configuration outcome.
Setup
Build it in a few focused steps.
- 1Connect CodeREADr once in the Notis portal.
- 2Create an automation for configuring CodeREADr Direct Scan URL settings.
- 3Tell Notis to use the service ID and requested postback settings in the incoming request, and ask for any required details that are missing.
- 4Pick an HTTP webhook as the trigger and choose where run reports go.
- 5Test with one real request for a service whose callback settings you can verify.
Questions about this workflow
What starts this workflow?
An HTTP request to the automation's webhook starts it. Include the service ID and requested Direct Scan URL settings in the request or prompt context.
Can this create a service too?
This workflow configures the Direct Scan URL for an existing service. Create or identify a valid service before triggering it.
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.