Back to the changelog

• Feature

  Scheduled item start

  You can now create an item with a future start time: pass scheduledAt (API or MCP) and the item stays pending, starting automatically at the given time instead of immediately. Before, the value was ignored and the item started right away. Useful for scheduled follow-ups, deferred sends and time-sensitive activities.

• Improvement

  State timeouts now actually work

  When a state has a timeout and it expires, the flow now advances: in the designer you can set a timeout target state; if unset, the system uses evaluation rules or, lacking those, the single allowed transition. Before, without an explicit rule the item could stay stuck past the deadline.

• Security

  API-key security & import/export fidelity

  Managing API keys (create/list/revoke) is now Admin-only (the FlowDesigner role could do it before) — least privilege. Flow import now preserves fields that were lost before (flow/state code, trigger constraints, effort requirement, manual-task-add). Saving the design now also persists the flow-level constraints (activation mode, required entity ref, trigger-data validation). Raising a start-event via MCP now correctly starts flows.

• Design

  Chrome extension

  The popup shows a selector when multiple flows match the page (before it showed only one). The "Open" button opens exactly the clicked item. Starting a flow from the side panel now shows errors instead of failing silently. New flows on a new domain now prompt for permission after sync; the side panel no longer hides flows that fail to load (shows a retry); linking a second tenant switches to it; and in-app (SPA) navigation in modern CRMs now recomputes badge/context on the new record.