Skip to main content
Routing forms collect visitor data through single-page or multi-step funnels, then route the visitor to a meeting type, external URL, custom page, or contact form based on configurable rules.

Key Concepts

Structure Types

Create a Routing Form

Create a form with inline data fields, funnel steps, and routing rules in a single request:

Cascade Creation

When creating or updating a routing form, data fields can be referenced by ID or created inline:
This works in both fields (form fields) and funnelSteps[].dataFields (funnel step fields).

Data Fields

Data fields are reusable inputs scoped to your company.

Input Fields

Selection Fields

Composite Fields

File & Document Fields

Display-Only Fields

These fields do not collect input. They are used for layout and content within forms.

Create Data Field

Routing Rules (Qualifiers)

Qualifiers determine where a visitor goes after submitting the form. They are evaluated in order; the first match wins.

Routing Actions

Condition Expressions

Conditions use a nested AND/OR tree:
Operators: equals, notEqual, contains, notContains, startsWith, blank, notBlank, lessThan, greaterThan, lessThanOrEqual, moreThanOrEqual, containsAny, containsNone Targets: attendeeEmail, attendeeFullname, attendeeFirstname, attendeeLastname, attendeePhone, attendeePolicyAccepted, attendeeReceiveReminders, attendeeLanguage, attendeeTimezone, attendeeOther (use customTarget for custom field name)

Fallback Qualifier

If no qualifier has isFallback: true, a default “Thanks for submitting” custom page is auto-created.

Updating with Declarative Sync

When updating via PATCH, nested arrays use different strategies:
  • Qualifiers: Declarative sync — items with id are updated, without id are created, missing items are removed
  • Funnel Steps & Fields: Full replace — the array you send replaces the current set

Sending Forms

Send a routing form to a recipient via email, SMS, or generate a one-time link.

Delivery Methods

Send via Email

The response always includes publicUrl regardless of delivery method. For unlimited-access forms, set a slug:

One-Time Fill

When sent to a recipient, each link can only be submitted once:
  1. SendPOST /v4/routing-form/:id/send creates a recipient with a unique token
  2. Open — Recipient opens the link, openedAt is recorded
  3. Submit — Recipient submits, completedAt is recorded
  4. Blocked — Re-submission returns 409 Conflict

Track Recipients

API Reference

Next Steps

Routing & Round-Robin

Distribute bookings across team members

Meeting Types

Configure meeting templates