Routing rules
Create Qubeforms Business routing rules using form field values. Apply tags and priorities, send notifications to verified recipients, and test matching rule order.
1. Create a Business routing rule
Business owners can create rules under Settings → API & routing → Routing rules. A rule matches submitted fields and selects verified notification recipients and tags. Enter a Rule name, Priority, Condition field, Operator, and Condition value, then optionally enter Route to recipients and Tags. Select Create rule. The field must match the submitted name exactly; use ordinary scalar values rather than nested objects.
2. Start with a concrete example
If your form submits department=sales, use the example below to route those submissions to your sales address. First add and verify that address under Recipients for this same form. Recipient addresses and tags can be comma-separated in the dashboard inputs. The rule’s field names are literal keys: a dot in a name is not a nested-property lookup.
Rule name: Sales enquiries
Priority: 100
Condition field: department
Operator: Equals
Condition value: sales
Route to recipients: sales@example.com
Tags: sales, follow-up3. Understand the visible operators
Equals and Not equal compare string values exactly, including case. Contains checks for a case-insensitive substring. For example, Equals sales does not match Sales, while Contains sales does. A missing field behaves like an empty value, so Not equal can match submissions that omit the field. The customer dashboard exposes these three operators; it does not provide a multi-condition builder or numeric-comparison control.
4. Understand order and combined matches
Rules are evaluated in ascending Priority order; use values from 1–1,000, with 100 as the default. Priority controls rule evaluation order, not an email delivery deadline. In the dashboard-created flow, every matching rule can contribute recipients and tags; results are combined and duplicates removed. Do not assume the first match excludes later matches. Business deliveries already use the priority queue through the plan.
5. Route only to verified addresses
When matching rules supply recipient addresses, Qubeforms sends notification mail only to the intersection of those addresses and the form’s currently eligible verified recipients. It does not add unverified addresses automatically. If the matched recipient list contains no eligible address, notification mail can have no destination. If no rule supplies recipients, normal verified recipients are used. A tag-only rule therefore keeps normal notification routing. Rules do not change the webhook URL or the autoresponder destination.
6. Find the resulting tags
Matching tags are added to the submission data under _qubeforms_tags; duplicate tags are removed and each tag is limited to 50 characters. Inspect the submission detail or read API to confirm the result. Routing evaluates the submission at receipt; creating a rule does not reprocess older records. Spam classification still controls delivery, and routing does not bypass origin checks, CAPTCHA, or plan limits.
7. Test and manage rules
Test a matching value, a nonmatching value, a different case, and an omitted field. Check tags and each notification destination before using the rule for important traffic. The current customer interface lists and creates rules but has no edit, disable, or delete control. Contact the operator to correct or remove an existing rule rather than creating conflicting replacements. If the form drops below Business, new submissions no longer use its routing rules.
Public form keys can appear in browser code. Read keys, management credentials, and webhook signing secrets must stay on the server.