/concierge-router-builder

--- name: concierge-router-builder description: Guides an admin through building a complete Concierge web-form router from scratch — teams, meeting types, rules, distributions, and the live router — via a discovery interview and confirmation checkpoint. Data fields stay UI-only; third-party webform trigger mapping is now API-writable via thirdPartyForm. version: 0.1.9 references:

• discovery
• segment-presets
• api-reference
• build-procedure
• output-format

inputs:

• name: workspace

type: string description: "Workspace name or ID the router should live in. If omitted, discovered via workspace-list and asked." required: false

• name: requirements

type: string description: "Optional free-text description of the desired router (segments, teams, meeting types) to pre-fill the interview. Missing details are still asked." required: false

• name: dry_run

type: boolean description: "If true, run the interview and present the full build plan without creating anything. The build only runs after explicit confirmation." required: false default: true outputs:

• name: plan

description: The confirmation summary — routing order (rule → team → meeting type → distribution), catch-all/not-scheduled behavior, and every object that will be created

• name: result

description: Everything built with IDs (teams, meeting types, rules, distributions, router) plus the router's booking slug — only after confirmation

• name: next_steps

description: UI-only actions the API can't do (data fields, Chili-managed form mapping, most CRM actions) and the go-live checklist tools_required: [chili-piper-mcp] human_decision_point: "The Phase 2 confirmation. Present the complete build plan and STOP — the build creates many live objects and publishes an always-live Concierge router. Nothing is created until the admin confirms." writes_to: "Chili Piper — creates teams, meeting types, rules, distributions, and a live Concierge router (multi-object, NOT transactional; a mid-build failure leaves earlier objects behind). Data fields are UI-only (or data-field-create). Chili-managed form mapping is also UI-only. Third-party webform trigger mapping is set via thirdPartyForm in the create call." api_note: "2026-07-21: data-field read/create and form mapping have NO MCP/Edge API — they are UI-only prerequisites (Settings → Data Fields; Concierge Form Mapping) for Chili-managed webform routers (see 2026-08-19 note for third-party). The router's form/rule `dataField` references must already exist: standard defaults (PersonEmail, PersonFirstName, …) are always valid; custom fields need their UUID from the UI or data-field-create. An unknown `dataField` fails concierge-router-create with 400. Field truth → references/api-reference.md.; 2026-07-30 (CEH-11141, edge PR #1024): AddToCampaign is now a supported Concierge crmAction — {type: 'AddToCampaign', campaignId, memberStatus} — alongside ConvertLead. Update ownership and create-event remain UI-only. Preflight checklist updated.; 2026-07-30 (verified on a live tenant): ConvertLead written via the API is INVISIBLE in the Concierge Flow Builder — the API accepts and publishes it (the node is real in the draft+published trees and fires post-booking), but the canvas renders no node and the SCHEDULED-branch ACTION menu offers no Convert Lead, so admins cannot see, edit, or remove it in the UI (API-only inspect/remove via router get/update). Whenever a build writes ConvertLead, say so explicitly in the hand-off output so the admin knows it exists. AddToCampaign UI rendering not yet verified. 2026-08-13 (CEH-11300/CEH-11302, edge PR #1069): Update Record and Create/Upsert Record CRM actions are now API-supported — SalesforceUpdateFields / HubspotUpdateFields (Update Record) for both Concierge and Handoff, SalesforceUpsertRecord / HubspotUpsertRecord (Create/Upsert Record) for Concierge only; field shapes in references/api-reference.md. campaign-list / campaign-search are now available to look up Salesforce campaignIds for AddToCampaign actions. 2026-08-13 (CEH-11303, edge PR #1072): SalesforceUpdateOwnership / HubspotUpdateOwnership are now API-supported — always assigns the CRM record owner to the booked host — so 'update ownership' is removed from the UI-only list. create-event remains UI-only. 2026-08-18 (CEH-11358, edge PR #1087): catchAll is now OPTIONAL on concierge-router-create — omitting it produces a router with no fallback path (unmatched requests are not scheduled). Previously required. 2026-08-19 (CEH-11363, edge PR #1088): for third-party webform routers, trigger field mapping is now API-writable via thirdPartyForm: [{formFieldName, dataField, label?}] in concierge-router-create (mutually exclusive with form). The 2026-07-21 'form mapping is UI-only' note applies only to Chili-managed webform routers — third-party form mapping no longer requires a UI step. Data fields still must exist before building (standard defaults always valid; custom fields via data-field-create API or the Settings UI).; 2026-08-25 (CEH-11428, edge PR #1107): teamId is now REQUIRED on CreateOwnershipRuleRequest — omitting it was accepted by the API but produced a rule that could never match (no team to route to). The API now rejects a missing teamId with 400. references/api-reference.md § Rules updated: teamId? → teamId*.; 2026-08-27 (CEH-11450, edge PR #1109): every OwnershipCondition in a rule's conditions block must include the ownership field ({source, object, field} — e.g. {source: 'SF', object: 'Account', field: 'OwnerId'}). Omitting it is now rejected with 400 (OwnershipConditionMissingReference). Previously accepted but unresolvable; now enforced at create/modify time.; 2026-09-03 (CEH-11590, edge PR #1151): SalesforceCreateEvent and HubspotCreateEngagement are now API-supported crmActions on Concierge (Create Event — post-booking calendar event in CRM). relatedTo is optional (full relation set supported on Concierge), meetingCance