What is your goal?
Get a trigger module (Custom Webhook or Twilio Watch Messages) to become a genuine, working first module for a scenario whose canvas currently has no real trigger.
What is the problem & what have you tried?
Any trigger-type module I add (tried Custom Webhook and Twilio “Watch Messages”) shows a cosmetic dotted connector line when dragged near the first module, but never actually connects. Confirmed via two independent signals: (1) the save validator reports downstream fields as “references inaccessible module,” and (2) clicking Auto-align strands the trigger module away from the rest of the flow every time, which Auto-align only does to modules with zero real incoming/outgoing edges.
Six tests run so far, all with the identical result:
- Custom Webhook trigger - fails.
- Twilio Watch Messages trigger (different module type entirely) - fails identically.
- Exported the scenario as a blueprint, rebuilt it as a brand-new scenario, added a fresh Twilio trigger there - fails identically on a clean canvas with a module that’s never touched the original scenario.
- Tried near-drag, full-overlap drag (dropped directly on the target module’s center), and reverse-direction drag (dragging the existing chain onto the trigger instead of the other way around) - all fail identically.
- Tried dropping the orphaned trigger onto a mid-chain module instead of the first module, to rule out “first module” being a special case - still fails.
- Tried in a brand-new browser tab that had never touched the scenario before, on the real persisted (not draft) scenario - fails identically, ruling out browser/tab-level staleness.
Right-clicking the canvas near the first module also produces no context menu (was hoping for an “insert module before” option).
Has anyone seen this, or know of an actual supported mechanism for wiring a new trigger onto an existing flow that already has a first module in place? Drag-to-connect appears completely non-functional for this specific operation in my case.
