Teams running outbound in Nooks want Chili Piper outcomes to drive the next steps in Nooks. There's no connection in that direction today, so the handoff from a Chili Piper event to a Nooks cadence is manual, or stitched together with CRM fields and workarounds.
Requested behavior: enroll a prospect in a Nooks sequence or cadence based on a Chili Piper action or a CRM field update. The cases customers have described:
  • Someone fills out a form but doesn't book a meeting, enroll them in a follow-up sequence
  • A meeting is marked no-show, enroll them in a re-engagement sequence
  • A meeting outcome or CRM field change moves someone into the right cadence
  • An agreement reached on a Nooks call triggers a Chili Piper scheduling link, sent immediately
Adjacent asks pointing the same direction: exposing Chili Piper events to Nooks through webhooks, and Orchestrator nodes for Nooks actions so this can be built into a flow instead of hard-coded.
Why it matters: Nooks is displacing Outreach and Salesloft as the sequencing layer for a growing number of teams. Booking from the dialer begins when a rep is on the phone with someone. This covers everyone who never gets that far.