Routing Rules

Routing for a booking form: if company size is over 50 and the region is Europe, send it to Sales EU. Drag routes into order, see what share of last month each one caught, test a response to watch it land, and export the lot as one CASE WHEN.

akarouting form·lead routing·routing rules

Explore Qnot

Install

Run this in any project set up for the shadcn CLI. It copies the Routing Rules source into your components folder, so the code is yours to change.

npx shadcn@latest add https://devl.dev/r/routing-rules.json

Use it

Import it and render it. Every prop has a typed default, so it works straight away, and you pass your own data when you’re ready.

import { RoutingRules } from "@/components/routing-rules";

export default function Page() {
  return <RoutingRules />;
}

Built with

A free React component in the Filters collection, written in TypeScript with Tailwind CSS on coss ui. MIT licensed.

coss ui: button, input, menu, select
npm: @qnot/core, @qnot/react, lucide-react, motion

Props

Read from the Routing Rules source. Everything is optional unless it says required.

Prop	Type	Default
title	string	"Request routing"
description	string	"Checked top to bottom. The first route that matches wins."
fieldsrequired	Fields	—
destinationsrequired	RouteDestination[]	—
routesrequired	Route[]	—
fallbackrequired	string	—
history	readonly Record<string, unknown>[]	[]
sampleResponserequired	Record<string, unknown>	—
onChange	(routes: Route[], fallback: string) => void	—
className	string	—

More in Filters

on Qnot

058

Alert Rules

An alert you write as a sentence: when error rate is above 2% for at least 5 minutes, only for checkout in production, page the on-call. A 30-day timeline shows which past incidents it would have caught, and warns you before it gets noisy.

on Qnot

059

Filter Bar

Linear-style filter chips you build from one menu: Status is not Done, Labels include Bug, Assignee is me. Click any part of a chip to change it, press F to add one, Backspace to drop it, and the issue list re-sorts itself as you go.

on Qnot

060

Flag Playground

Paste a user as JSON and watch every flag decide, rule by rule: each condition ticks or crosses, the winning rule lights up, later ones grey out, and the served variant swaps in. Broken JSON and wrong types get called out instead of quietly failing.

on Qnot

061

Flag Targeting

Targeting rules for a feature flag, per environment: if beta and in Europe serve the new checkout, roll out to 10% of everyone else, fall back when it's off, and see who gets what across 2,000 simulated users while you edit.

Prop

Type

Default

title

string

"Request routing"

description

string

"Checked top to bottom. The first route that matches wins."

fieldsrequired

Fields

—

destinationsrequired

RouteDestination[]

—

routesrequired

Route[]

—

fallbackrequired

string

—

history

readonly Record<string, unknown>[]

[]

sampleResponserequired

Record<string, unknown>

—

onChange

(routes: Route[], fallback: string) => void

—

className

string

—