Back to the changelog

• Feature

  Delete items created by mistake

  An item can now be **deleted** from its detail page, but only under safe conditions: it must still be in the **initial status** and have **no completed tasks**. A regular user can delete only items they created manually themselves; an **Admin** can also delete items created by automations/API — handy for cleaning up example items left over from tests. Deletion asks for confirmation and is recorded in the audit log.

• Improvement

  Flow folders: same actions in the list view

  The **list view** of flows now has the same actions as the card view: **move to folder, edit, archive, delete** (plus design / monitor / analytics). Two related annoyances are fixed too: moving a flow to a folder now updates the folder counter immediately, and the "move" menu is no longer clipped inside the card.

• Integration

  Optional strict validation of the external trigger

  For ERP/CRM integrations: in the designer (**Trigger API** tab) two new options make the trigger call stricter — **"Require entityRefId"** (rejects calls without an identifier instead of auto-generating one) and **"Validate the data payload"** (checks the received data against the flow's data structure and rejects incomplete or wrong-typed payloads with a clear error). Both **off by default**: if you don't enable them, the flexible behaviour is unchanged.

• Improvement

  More robust during updates (deploy)

  The **worker** now finishes in-flight jobs before shutting down during an update and **automatically retries** interrupted ones (with an idempotency key on webhooks to avoid duplicates). Less risk of lost work during a deploy.

• Improvement

  Corrected documentation and in-app guide

  The **/docs** page now opens via a direct link / bookmark too (direct access previously returned 404). The **Trigger API** guide was rewritten on the real endpoint (`POST /api/v1/trigger/{flowCode}` with the `X-Api-Key` header) — the old version showed an endpoint and parameters (e.g. `action: transition`) that don't exist in the backend. The **Authentication** section now correctly describes the **HttpOnly cookie** login (not a token in the JSON body) and points to **API keys** for external integrations.

• Design

  UX refinements and assorted fixes

  The **automation gauges** are fixed — the arc was drawn the wrong way and overlapped the value and label. In the **"New flow"** modal the name field now clearly signals it is required (red asterisk, helper text, tooltip on the disabled button) and is properly marked for accessibility and password managers. On the API side, **action endpoints** (publish, archive, restore…) now accept a call with no body without returning an error.