Configure CodeREADr response fields from support requests
Make requested scan payload changes actionable from the originating ticket.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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
Payload changes are easy to misread when requirements move between support and configuration tools.
- Reduce interpretation errors
- Keep payload requests connected to their source
- Get a clear configuration summary
Setup
Build it in a few focused steps.
- 1Connect Zendesk and CodeREADr in Notis once.
- 2Create an automation named Ticket to response fields.
- 3Tell Notis to create or update response fields only after confirming the ticket contains an approved payload request.
- 4Pick New Zendesk Ticket as the trigger and choose a report channel.
- 5Test with one ticket describing the requested scan fields.
Questions about this workflow
Can this remove existing response fields?
Only ask for changes supported by the action and explicitly approved in the ticket.
What if field requirements conflict?
Notis should report the conflict for review rather than guessing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Codereadr. A trigger fires from one place; an action lands in another.
Zendesk 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/
New User Created
Triggered when a new user is created in Zendesk.
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.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
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.
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.
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.
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.
Zendesk 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.