Skip to content
Notis

Prepare scan responses for a new Notion workflow

When a new data source defines a scanning workflow, let Notis configure the response fields Codereadr returns.

Trigger

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.

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

A new tracking workflow can start collecting scans before its response details are considered.

  • Prompts response-field setup as a workflow is created.
  • Reduces the gap between tracking plans and scan output.
  • Keeps requested response details grounded in the Notion context.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Codereadr to Notis once in the portal.
  • 2Ask Notis to configure Codereadr response fields when a new Notion data source documents a scan workflow that needs them.
  • 3Select the Notion Data Source Created trigger and choose a run-report channel.
  • 4Test with one real data source and inspect the configured response fields.

Questions about this workflow

Does creating a data source always mean scan fields are needed?

No. State in the instruction which data sources describe scan workflows requiring response fields.

Can fields be updated later?

This action creates or updates response fields, according to the Codereadr tool description.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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/

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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".

ActionInstant

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.