Cal: Let routing forms end in a URL or message, log submissions and pass answers on
Calendly routing forms can send respondents to an event type, a custom message or an external URL, and emit routing_form_submission.created webhooks (https://community.calendly.com/featured-tips-tricks-32/12-days-of-calendly-day-10-routing-for-teams-527, https://learn.microsoft.com/en-us/connectors/calendlyv2). Our evaluateRouting in lib/calendar-routing.ts can only return an event type slug, rules have a single condition, submissions are not stored, and only name and email reach the booking (components/calendar/PublicRoutingForm.tsx). Disqualified leads hit a dead end and the host never sees the qualification answers. First scope: destination types (event, url, message), a submissions table visible in the form editor, carry all answers into booking answers, and a routing.submitted event for webhooks and Flow. Priority: medium. Effort: M. Compared with Calendly.
Comentários 0
Ainda sem comentários.
Entre para comentar