Skip to main content

Trigger System Overhaul: Smarter Starts for Every Workflow

Trigger System Overhaul: Smarter Starts for Every Workflow​

How a workflow starts matters just as much as what it does. We've replaced the old start node with a dedicated trigger system that supports multiple trigger types, sensible defaults, and reliable execution — so your automations fire exactly when and how you expect.

What's New​

  • Dedicated Trigger Node: The generic start node has been replaced with a purpose-built trigger node. Choose from App Events, Scheduled, or Webhook trigger types — each with its own configuration panel and validation.

  • Default Status & Direction Preselection: Each trigger type now comes with sensible defaults pre-selected. App event triggers default to relevant statuses and directions, reducing setup time and configuration errors.

  • Inbound Email Trigger: Email triggers now fire for all matched flows — not just the first match. If an inbound email matches criteria for three different workflows, all three run.

  • New Chat Begins Trigger: Enabled for all channels. When a new chat conversation starts — whether from the widget, SMS, or any other channel — your workflow fires automatically.

  • Disabled Trigger Safety: Disabled triggers and disabled global nodes no longer fire unexpectedly. When you disable something, it stays disabled — period. No more ghost triggers executing flows you thought were turned off.

  • Auto-Save Node Config: Node configurations now save automatically when you switch between nodes. No more lost changes because you forgot to click "Apply."

Why This Matters​

Reliable Triggers: The overhauled trigger system gives you precise control over when workflows fire, with clear type distinctions and sensible defaults. No more ghost triggers or unexpected executions.

Multi-Flow Email Handling: Inbound email triggers firing for all matches means you can have separate workflows for support routing, lead nurturing, and notification — all triggered by the same email without conflicts.

Faster Setup: Default preselection means less manual configuration. Create a trigger, and it's already configured for the most common use case — just customize from there.