Automate Feature Rollout Tracking
Rolling out features to different user cohorts is manual, error-prone, and invisible. Notis configures the rollout tracking workflow the moment a feature launches. Every cohort is tracked, adoption is measurable, rollback is instant.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
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.
Why this helps
Rolling out features requires manual coordination across teams, no tracking of who rolled out to which cohort, rollout progress is invisible, adoption metrics are guesses.
- Rollout workflow auto-configured when feature goes live
- Track every cohort rollout with scans and timestamps
- Adoption metrics are real numbers, not guesses
- Rollback decisions are based on real rollout data
Setup
Build it in a few focused steps.
- 1Connect Linear and CodeREADr to Notis
- 2Tell Notis: 'When a feature issue moves to Rollout, configure the CodeREADr picking and delivery workflow.'
- 3Specify which CodeREADr service handles feature rollouts
- 4Set your notification channel for rollout workflow activations
- 5Move a feature issue to 'Rollout' and verify the workflow is configured
Questions about this workflow
How do I define cohorts?
Define cohorts in CodeREADr using custom questions or response fields. Notis uses your existing rollout service configuration.
Can I roll back to a previous version?
Yes. Close the Rollout issue or change its status in Linear. You control rollback; Notis doesn't auto-trigger it.
Who tracks the rollout scans?
Your team members with CodeREADr access scan rollout events. You configure who can access what in CodeREADr.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Codereadr. A trigger fires from one place; an action lands in another.
Linear 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 Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
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.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Linear 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.