Keep a monthly view of configured scan services
Let a recurring Notis automation retrieve Codereadr services before your monthly operations review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Retrieve CodeREADr Services
Tool to list all services. Use when you need to fetch configured services in your CodeREADr account after authentication.
Why this helps
Service inventories become stale when nobody has a recurring reminder to check them.
- Creates a regular service inventory checkpoint.
- Reduces manual preparation for operations review.
- Helps teams notice service changes sooner.
Setup
Build it in a few focused steps.
- 1Connect Codereadr to Notis once; connect Notion too if the review should reference planning pages.
- 2Ask Notis to retrieve Codereadr services once a month and report the result.
- 3Select a monthly recurring schedule and choose a channel for run reports.
- 4Test one retrieval and confirm the monthly timing.
Questions about this workflow
Does this change service settings?
No. It retrieves the configured services for review.
Can the schedule be changed later?
Yes. Update the automation's recurring schedule in the portal.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Codereadr. A trigger fires from one place; an action lands in another.
Notion 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/
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.
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.
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.
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.
Notion 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.